Azure Databricks Architect (US Healthcare Payer Domain)

Job Title

Azure Databricks Architect (US Healthcare Payer Domain)

Location

Newtown Square, PA

Work Mode

Hybrid (3 days onsite must)

Role Summary

Seeking a Data Lake/Lakehouse Data Modeler with deep hands-on experience building governed, secure, and high-performance data models on Azure for banking use cases. The role will design logical and physical schemas across landing, curated, and serving layers to support Payer domain Analytics and governance reporting.

Experience & Education

• 10 + years of experience in data modeling or data engineering with US Healthcare and Payer domain is a must have experience.
• 5 years of experience with different modeling tools like Erwin/ Embarcadero or ER Studio
• 5 plus years of experience in modeling various data domain in Payer domain.
• Azure or Databricks certifications is a value add.
• Deliverables: Model artifacts and data dictionaries, source-to-target mappings, lineage for audits, and measurable performance and quality improvements.

Key Responsibilities

• Design logical and physical models across raw, curated, and consumption layers optimized for lakehouse patterns.
• Define canonical models and source-to-target mappings for member, provider, claims, prior auth etc
• Define retention, archival, encryption (CMK), and access controls using Azure Key Vault and Azure AD.
• Work with data engineers and platform teams to implement models in Databricks and Synapse with CI/CD and tests.
• Perform data profiling, validation, and iterative tuning to meet performance and SLAs for BI and ML consumers.

Required Qualifications

• Proven experience modeling Lakehouse or data lake solutions for US Healthcare Payers.
• Deep knowledge of US Payer domain with modeling member, provider and all types of claims.
• Hands-on experience with ADLS Gen2, Azure Databricks (Delta Lake).
• Practical experience with CDC, streaming, low-latency analytics, and schema evolution strategies.
• Familiarity with Unity Catalog, Azure AD, Key Vault, network isolation, and regulatory