Architect

Healthcare

Architect-Data

₹60–90L ~AI est. Mumbai, Maharashtra, India; Bangalore, Karnataka, India; Trivandrum, Kerala, India FULL TIME
Market Sentiment
HIGH DEMAND

Neural analysis suggests this role is
optimal for Senior candidates.

The Brief

“Architect - Data at Architect. Skills: Data Architecture, Google Cloud Platform, Apache Iceberg, FHIR. Define architectural blueprint. Define canonical data model”

What You'll Achieve.

RPO under 5 minutes; RTO under 4 hours

Industry & Context.

Healthcare
Problems you'll solve

Root cause analysis; Troubleshooting; Critical thinking

Eligibility Requirements

PHI handling discipline

What They're Looking For.

Must Have

Bachelor's or Master's degree, 8+ years of data engineering experience, 3-5 years in Data Architect or Lead Data Engineer role, Deep expertise architecting and operating large-scale data platforms on Google Cloud Platform, Hands-on experience with Apache Iceberg in production, Production experience with Starburst or Trino, Experience with streaming architectures using Apache Flink and Apache Kafka, Expert SQL and Python skills, Deep experience with dbt, Comprehensive understanding of healthcare data standards, Hands-on experience with FHIR runtime platforms, Experience with master data management for patient identity resolution, Experience designing for HIPAA-regulated environments, Demonstrated ability to lead complex technical initiatives, Make critical architectural decisions under uncertainty, Influence diverse stakeholders, Excellent written and verbal communication

Nice to Have

GCP Professional Data Engineer or Cloud Architect certification, Experience with Atlan or comparable governance platforms, Experience with multi-region deployments on GCP, Production experience operating Confluent Cloud, Familiarity with spec-driven development workflows, Experience replacing or sunsetting legacy healthcare data platforms

What You'll Do.

Define architectural blueprint

Define canonical data model

Define ingestion framework

Define transformation patterns

Define FHIR serialization layer

Define bidirectional flow with FHIR-Repository

Define governance frameworks

Define observability frameworks

Set standards for implementation

Partner with customer's Health Data Engine technical owners

Make architectural decisions

Defend architectural choices

Adapt architectural choices

Own end-to-end architecture

Maintain architecture specification document

Lead design of Common Data Model

Lead evolution of Common Data Model

Define bidirectional FHIR flow

Specify FHIR repository egress interceptor contract

Specify loopback Flink consumer pipeline

Specify boundary semantics

Define patient identity resolution architecture

Set standards for naming conventions

Set standards for hash algorithms

Set standards for Iceberg table properties

Set standards for DLQ taxonomy

Set standards for observability

Set standards for security

Own spec-driven development framework

Approve changes to platform-wide rules

Drive high-volume capacity design

Lead capacity planning

Lead capacity validation

Lead parallel-run cutover

Evaluate technology choices

Recommend technology choices

Build trade-off matrices

Defend technology recommendations

Provide architectural review for engineering work

Review component specs

Mentor data engineers

Lead architectural review meetings

Translate complex trade-offs

Establish disaster recovery strategy

Evolve disaster recovery strategy

Establish backup strategy

Evolve backup strategy

Establish reprocessing strategy

Evolve reprocessing strategy

How You'll Work.

Team & Collaboration

Customer technical stakeholders; Health Data Engine team; Governance team; Security team; Clinical informatics team

Communication Scope

Verbal communication; Written communication; Translate complex trade-offs

Process & Methodology

Spec-driven development

Full Job Description

While technology is the heart of our business, a global and diverse culture is the heart of our success. We love our people and we take pride in catering them to a culture built on transparency, diversity, integrity, learning and growth. If working in an environment that encourages you to innovate and excel, not just in professional but personal life, interests you- you would enjoy your career with Quantiphi! # # _**Data Architect**_ **Exp Range :** 8 - 13 Years **Job location :** Mumbai , Bangalore, Trivandrum ## Role Overview The Data Architect is the senior technical owner of the platform's design. You will define and evolve the architectural blueprint — the canonical data model, the ingestion framework, the transformation patterns, the FHIR serialization layer, the bidirectional flow with FHIR-Repository, and the governance and observability frameworks that hold them together. You will set the standards every other role implements against. This role works in close partnership with the customer's existing Health Data Engine technical owners, who carry deep operational knowledge of healthcare data at scale. Architectural decisions are made in dialogue with them, anchored on real volume requirements and known operational pain points. You will be expected to defend choices with technical depth and adapt them when warranted. ## Key Responsibilities * Own the end-to-end architecture across ingestion (Flink + PySpark), storage (Iceberg on GCS with BigLake Metastore), transformation (dbt over Starburst), FHIR serialization (flat FHIR Iceberg → bundles → FHIR-Repository), and consumption (Starburst, FHIR API, data products). Maintain the architecture specification document and its companion design docs. * Lead the design and evolution of the Common Data Model (CDM): the dimensional, fact, bridge, and reference table classes; SCD2 semantics; hash key conventions; the write-authority matrix that governs cross-source field precedence. CDM is the project's central design art

Free ATS check

Applying for this Architect - Data role?

Most applicants get filtered before a human reads their resume. See if yours makes the cut.

How to Apply on Workday

  • Workday has a multi-step form — save your progress after every section.
  • "Apply With LinkedIn" can fail or lose data; manual entry is more reliable.
  • Watch for the "Submit for Review" final step — hitting "Save" alone does not submit.
  • Job requisition numbers are useful when following up with HR by email.

ANONYMOUS · UNFILTERED

What do employees actually say about Architect?

Real rants from real employees. Read before you apply.

Read Company Rants →