Enterprise Data Architect

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs at start: "Alignment Health is breaking the mold..." That's about the company and role? Could be "About the role" or "About the company". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content for Responsibilities (Job Duties/Responsibilities). We have Requirements (Experience, Education, Training). We have Skills & Competencies. We have Pay Range. We have maybe Benefits? Not mentioned. Schedule? Not mentioned. Supervisory Responsibilities is a note but could be part of Responsibilities? It says "Supervisory Responsibilities This role does not carry direct supervisory responsibility." That's a detail; we could include under Responsibilities or a separate note but not a heading unless we have content. Probably include under Responsibilities as a bullet. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, disclaimer, scam warning, etc. Also remove "Essential Physical Functions" maybe? It's not required but could be considered boilerplate? It's not EEO but still maybe not needed? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Essential Physical Functions is not EEO but could be considered legal? Might be considered boilerplate but it's about job demands. Might keep? Safer to keep if it's substantive. However it's generic; but it's not duplicated. Might keep as a paragraph under a section like "Physical Requirements"? Not in allowed headings. Could fold into Responsibilities or a separate

without heading. Probably better to omit as it's not explicitly requested and could be considered boilerplate. The instruction says remove legal/EEO etc. Physical demands maybe not legal but could be considered boilerplate. I'd omit. We need to preserve all substantive information. So we need to include the introductory paragraphs about Alignment Health mission etc. That could be under "About the role" or maybe a general description. We'll create an

About the role

with paragraphs describing the company and role. Then Responsibilities: list bullet points from Job Duties/Responsibilities. Then Requirements: include Experience, Education, Training (maybe combine). Could have subheadings? Not allowed; only those specific headings. We could put all under Requirements as a

with items. But we need to preserve details like "Required: 10+ years..." etc. We'll list each requirement as
• . Then Skills & Competencies: list bullet points. Then Pay: include Pay Range. We must not include Benefits or Schedule if not present. We must not include filler like "commensurate with experience". Not present. Now craft HTML. We need to ensure no markdown fences, just raw HTML. Let's draft:

  About the role

  Alignment Health is breaking the mold in conventional health care, committed to serving seniors and those who need it most: the chronically ill and frail. It takes an entire team of passionate and caring people, united in our mission to put the senior first. We have built a team of talented and experienced people who are passionate about transforming the lives of the seniors we serve. In this fast-growing company, you will find ample room for growth and innovation alongside the Alignment Health community. Working at Alignment Health provides an opportunity to do work that really matters, not only changing lives but saving them. Together.

  The Enterprise Data Architect sets the technical foundation for how data is structured, integrated, stored and governed across our Medicare Advantage health plan — translating business strategy into scalable, compliant, and future-ready data solutions/services. This role partners directly with clinical operations, actuarial, compliance, IT, and business intelligence teams to ensure data assets support accurate risk adjustment, Star ratings performance, regulatory reporting, and member outcomes. The position drives measurable impact on the organization's ability to use data as a strategic asset — enabling analytics, AI/ML capabilities, and CMS-compliant reporting at scale.

  Responsibilities

  • Design and govern the data architecture that spans operational systems, cloud platforms, and analytics environments to support clinical and business workflows across our Medicare Advantage lines of business.
  • Build and maintain data models (conceptual, logical, and physical) that enable accurate risk adjustment, HEDIS reporting, Star ratings optimization, and encounter data submissions to CMS.
  • Establish and enforce data governance frameworks — in coordination with the Data Governance, compliance, and privacy teams — covering data quality, lineage, PHI/PII classification, and audit readiness.
  • Integrate structured and unstructured data from claims systems, EHRs, pharmacy platforms, and third-party sources into unified, reliable data pipelines that serve analytics and operational decision‑making.
  • Define and uphold security architecture that meets HIPAA, CMS, and SOC 2 requirements while enabling appropriate, governed access for analytics teams and business consumers.
  • Evaluate and recommend data platforms, cloud technologies, and vendors — including tools for data virtualization, orchestration, consumption, analytics and AI/ML infrastructure — that align with organizational strategy and roadmap priorities.
  • Serve as the primary technical data partner to cross‑functional leaders across clinical operations, population health, finance, product, and compliance — translating complex architecture decisions into clear business context.
  • Advance data‑enabled innovation by scoping and piloting emerging capabilities — including generative AI, FHIR‑based interoperability, and real‑time streaming — that support care management and member engagement initiatives.
  • Supervisory Responsibilities: This role does not carry direct supervisory responsibility. The Enterprise Data Architect leads through technical authority and cross‑functional influence across engineering, analytics, governance, and business teams.

  Requirements

  • Required: 10+ years of progressive experience in data architecture, enterprise data integration, and database design.
  • Minimum 2 years of experience working in a health plan, payer, or healthcare delivery system with direct familiarity with claims data, EHRs, HEDIS, and CMS reporting environments.
  • Demonstrated experience designing data platforms in regulated, audit‑sensitive environments with PHI and PII datasets (including canonical models for Enterprise Data Platforms).
  • Proven experience with cloud data platforms (AWS, Azure, or GCP) and modern architecture patterns including data lakes, lakehouses, and real‑time streaming.
  • Experience leading cross‑functional architecture initiatives and influencing senior stakeholders without direct authority.
  • Experience working in an agile delivery model.
  • Preferred: Experience designing data solutions for Medicare Advantage‑specific programs including risk adjustment, Star ratings, RADV audits, and value‑based care models.
  • Preferred: Experience enabling AI/ML and generative AI capabilities within a healthcare data platform context.
  • Preferred: Background in DataOps, Agile delivery methodologies, and healthcare interoperability standards (FHIR, HL7).
  • Education Required: Bachelor's degree in Computer Science, Information Systems, Data Science, Engineering, or a related technical field; equivalent combination of education and demonstrated experience will be considered.
  • Education Preferred: Master's degree in a related technical or data discipline.
  • Training Required: Demonstrated working proficiency with cloud data platforms (Azure Databricks, Snowflake, BigQuery, Redshift, or equivalent) acquired through direct hands‑on project experience.
  • Training Preferred: Cloud platform certification (AWS Certified Data Analytics, Azure Data Engineer Associate, or Google Professional Data Engineer).
  • Training Preferred: Data governance or architecture certification (TOGAF, DAMA‑CDMP).

  Skills & Competencies

  • Technical / Role‑Specific Skills
  • Data Architecture & Modeling — Expert‑level proficiency in conceptual, logical, and physical data modeling using industry methodologies (Kimball, Inmon, Data Vault).
  • Cloud Data Platforms — Hands‑on experience with Snowflake, Databricks, BigQuery, or Redshift; familiarity with data lake and lakehouse architectures.
  • Data Integration & Orchestration — Working knowledge of ETL/ELT tools and orchestration platforms (Informatica, Talend, dbt, Airflow).
  • Healthcare Data Standards & Regulatory Knowledge — Applied knowledge of Medicare Advantage data constructs including HIPAA, CMS encounter data, HEDIS, STAR ratings, risk adjustment (HCC coding), and ICD‑10/CPT codes.
  • Data Governance & Security — Demonstrated ability to design and enforce governance frameworks, data classification, lineage tracking, and PHI/PII protection across regulated environments.
  • SQL & Programming — Advanced SQL proficiency; working knowledge of Python or Scala for data engineering and pipeline use cases.
  • AI/ML‑Enabling Infrastructure — Familiarity with MLflow, Feature Store, vector databases, LangChain, and generative AI APIs in the context of healthcare data environments.
  • Licensure Required: None required for this role.
  • Preferred: TOGAF (The Open Group Architecture Framework)
  • Preferred: DAMA Certified Data Management Professional (CDMP)
  • Preferred: AWS Certified Data Analytics, Azure Solutions Architect, or Google Professional Cloud Architect
  • Preferred: CPHIMS (Certified Professional in Health Informatics and Information Management) or equivalent healthcare IT credential

  Pay

  Pay Range: $130,332.00 - $195,498.00. Pay range may be based on a number of factors including market location, education, responsibilities, experience, etc.

  We need to ensure no duplicate headings. The Skills & Competencies section includes a nested list for technical skills; we used
  • Technical / Role‑Specific Skills
  ... That's okay but we need proper HTML: can't have
  directly inside
  • without closing? Actually you can:
  • Technical / Role‑Specific Skills
    ...
  . We'll adjust. Let's rewrite Skills & Competencies properly:

  Skills & Competencies

  • Technical / Role‑Specific Skills
    • Data Architecture & Modeling — Expert‑level proficiency in conceptual, logical, and physical data modeling using industry methodologies (Kimball, Inmon, Data Vault).
    • Cloud Data Platforms — Hands‑on experience with Snowflake, Databricks, BigQuery, or Redshift; familiarity with data lake and lakehouse architectures.
    • Data Integration & Orchestration — Working knowledge of ETL/ELT tools and orchestration platforms (Informatica, Talend, dbt, Airflow).
    • Healthcare Data Standards & Regulatory Knowledge — Applied knowledge of Medicare Advantage data constructs including HIPAA, CMS encounter data, HEDIS, STAR ratings, risk adjustment (HCC coding), and ICD‑10/CPT codes.
    • Data Governance & Security — Demonstrated ability to design and enforce governance frameworks, data classification, lineage tracking, and PHI/PII protection across regulated environments.
    • SQL & Programming — Advanced SQL proficiency; working knowledge of Python or Scala for data engineering and pipeline use cases.
    • AI/ML‑Enabling Infrastructure — Familiarity with MLflow, Feature Store, vector databases, LangChain, and generative AI APIs in the context of healthcare data environments.
  • Licensure Required: None required for this role.
  • Preferred: TOGAF (The