Azure Technical Architect

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 role in one sentence

PERSONALLY LEAD the technical evolution of the client’s modernized backend and ensure that backend services, integrations, FHIR, Databricks, identity, security, and external platforms evolve as one coherent architecture.

This is not an ivory-tower architecture position.

About the RoleThe client is building a modern, Azure-first healthcare platform. We are looking for a hands-on Technical Architect with 8–10 years of total technology experience who can architect, build, integrate, troubleshoot, and continuously evolve this ecosystem.

The Architecture You Will UnifyOperational & 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.

Experience Profile We Prefer8–10 years of total professional technology experience. The strongest candidates will have started with a solid software, backend, integration or platform engineering foundation and grown into progressively larger architecture responsibilities while remaining hands-on.

• Typically 3–5 years of increasingly significant design/architecture responsibility within the 8–10 year career span.
• Evidence of personally owning architecture for substantial production systems—not only proposals or RFPs.
• Recent code/design reviews, troubleshooting, PoCs, deployment or production involvement.
• Experience working directly with small engineering teams and making progress in ambiguous, evolving environments.