TECHNICAL ARCHITECT

Azure Healthcare Platform & Integration | Hands-on builder-architect | US Based Healthcare Platform

EXPERIENCE

8–10 years total

LOCATION

Hyderabad | Primarily WFO

ROLE TYPE

Full-time | Hands-on technical lead

The Architecture You Will Unify

Operational & Clinical: Healthie for care workflows; Azure Health Data Services / FHIR as the canonical clinical backbone; Redox for hospital interoperability.

Backend & Integration: Azure API Management, Service Bus/eventing, Functions, Logic Apps, backend services, APIs, webhooks, integration contracts, retries, reconciliation and observability.

Data & Intelligence: ADLS Gen2, Azure Databricks, Delta Lake, Bronze/Silver/Gold Medallion Architecture, Unity Catalog, governed analytics and AI consumption.

Engagement & Enterprise: HubSpot, Intercom, patient communications, downstream reporting, identity/EMPI, consent, governance and security controls.

What You Will Own and Lead

· Own the end-to-end technical architecture of the modernized backend and continuously evolve it as it scales.

· Define clear system boundaries and source-of-truth rules so FHIR, Healthie, Databricks, engagement systems and hospital integrations do not become competing data silos.

· Architect integration patterns across APIs, webhooks, Service Bus/events, batch, CDC and FHIR transactions; make practical sync-versus-async decisions.

· Define reusable patterns for idempotency, retries, dead-letter handling, replay, reconciliation, schema evolution, versioning, correlation IDs and observability.

· Lead technical design across backend services, Redox/hospital flows, Healthie integration, FHIR mappings, identity crosswalks, CRM/communication integrations and any other new vendors (In future)

· Provide architecture leadership for Databricks, Delta Lake and Medallion design while allowing the Data Engineer to own day-to-day pipeline implementation.

· Drive identity and master-data architecture across FHIR Patient IDs, Healthie IDs, Redox/hospital MRNs, provider/facility identifiers and future EMPI/MDM capabilities.

· Embed HIPAA-aligned security, PHI minimization, RBAC, Managed Identity, Key Vault, auditability, environment separation and least privilege into delivery.

· Establish pragmatic architecture discipline: Architecture Decision Records, reference patterns, technical standards, design reviews and code-review expectations.

· Mentor engineers, unblock difficult problems, challenge vendor designs, and step into implementation whenever a problem crosses team or system boundaries.

What Hands-On Means Here

YOU WILL BE EXPECTED TO DO THIS

· Open and understand backend code.

· Review pull requests and API implementations.

· Read Python, SQL and PySpark logic.

· Inspect FHIR resources, REST requests and webhook payloads

· Trace events across queues, services, logs and data layers.

· Troubleshoot production failures with engineers & optimise for throughput

· Test vendor APIs and authentication flows.

· Build PoCs or small reference implementations when needed.

THIS ROLE IS NOT THIS

· Creating diagrams and handing them to delivery teams.

· Attending architecture councils without implementation accountability.

· Advisory consulting with limited day-to-day ownership.

· Pure program or vendor management.

· Choosing technology only by feature comparison or certification knowledge.

· Becoming a bottleneck for every engineering decision.

· Acting as the primary feature developer for all teams.

· Treating architecture as something finished once documented.

Non-Negotiable Capabilities

ARCHITECTURE, INTEGRATION & AZURE

· Distributed systems and cloud-native architecture.

· API-led and event-driven integration.

· REST, JSON, OAuth, webhooks and versioned contracts.

· Idempotency, retries, DLQ, replay and reconciliation.

· Strong Azure architecture across APIM, Functions, Service Bus/Event Hub, Logic Apps, ADLS, Key Vault, Entra ID/RBAC and observability.

· Ability to make practical service-selection trade-offs.

· Technical Architect – What the Resume Should Demonstrate

·

· For the Azure Healthcare Technical Architect role, the resume should clearly demonstrate the following capabilities:

·

· CRITICAL

·

· 1️⃣ Azure Architecture

· APIM, Azure Functions, Service Bus, Logic Apps, ADLS, Key Vault, Entra ID/RBAC

·

· 2️⃣ Backend Engineering

· Python/backend APIs, REST, JSON, OAuth, Webhooks

·

· 3️⃣ Integration Architecture

· API-led & event-driven integration, Async processing, Retries, DLQ, Idempotency, Replay & Reconciliation

·

· 4️⃣ Healthcare Technology

· FHIR, Azure Health Data Services, Healthie, Redox, HIPAA/PHI, Patient Identity

·

· 5️⃣ Architecture & Design

· HLD/LLD, Architecture Decision Records (ADRs), Design Reviews, System Boundaries & Source-of-Truth

·

· 6️⃣ Production Troubleshooting

· Logs, Queues, APIs, Distributed Tracing, Production Failures, Performance & Throughput Optimization

·

· 7️⃣ Hands-on Coding

· Ability to read/write and troubleshoot Python, SQL and PySpark

·

· HIGH IMPORTANCE

·

· 8️⃣ Databricks Architecture

· Databricks, Delta Lake, Medallion Architecture (Bronze/Silver/Gold), Unity Catalog

·

· 9️⃣ Data Engineering

· SQL, PySpark, CDC, Streaming/Batch, Schema Evolution & Data Lineage

·

· Technical Leadership

· Mentoring engineers, technical decision-making, Code Reviews, PoCs and Architecture Governance

·

Key point: This role is looking for a hands-on Technical Architect, not just someone who creates architecture diagrams. The resume should show actual production implementation, troubleshooting, design ownership and technical leadership.