Principal Product Owner / Architect

We need to output HTML fragment with sections only if real content. Must include headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate etc. We need to extract substantive content. Let's parse the posting: First paragraph: "Become a part of our caring community The Principal Product Owner / Architect is a dual-mandate leadership role that unifies product strategy and solution architecture across CenterWell's four core business segments: Pharmacy, Primary Care Organization (PCO), Home Solutions, and Humana Military. This senior individual contributor serves as the connective tissue between business vision and technical execution—owning cross-segment product roadmaps while simultaneously authoring and governing the architectural blueprints that underpin them. You will operate within CenterWell IT – Cross-CenterWell Architecture, partnering with segment product leaders, engineering teams, EA Activation, security, data, and compliance to deliver integrated, interoperable health solutions that serve members, providers, and partners across the full care continuum. Your decisions shape what gets built, how it gets built, and the standard by which all four segments measure delivery readiness." That's prose about role. Could be "About the role". We'll put that in

  About the role

  then

  ...

  . Next: "DAY-TO-DAY Key Activities" then list of bullet-like sentences separated by periods? Actually it's a paragraph with sentences separated by periods but no explicit bullet list. The instruction: Use
  • for any list of duties/requirements/benefits. The DAY-TO-DAY Key Activities appears to be a list of duties. We can treat each sentence as a list item. Let's extract sentences: - Define and own a unified cross-segment product roadmap that balances segment-specific priorities against shared platform investments, and communicates trade-offs clearly to leadership. - Establish and maintain reference architectures, design patterns, and integration standards applicable across all four CenterWell segments. - Conduct cross-segment discovery sessions, design workshops, and architecture reviews to surface shared needs, resolve competing priorities, and prevent duplicative build. - Own and prioritize top-level product backlogs for shared platforms, partnering with segment product owners to decompose initiatives into delivery-ready user stories with clear acceptance criteria and non-functional requirements (NFRs). - Define integration contracts, API standards, and domain boundaries for cross-segment data flows spanning pharmacy, clinical, home health, and military health domains. - Lead architecture checkpoints and risk reviews for cross-segment initiatives; represent the combined product and architecture perspective in governance forums (ARB, TRB, MOR). - Translate product vision into architectural runways and delivery-ready specifications that engineering teams across segments can act on immediately. - Identify and steward opportunities for component and pattern reuse across segments; build the case for platform consolidation where segment convergence creates lasting efficiency. - Serve as the primary liaison between segment business leaders, engineering leads, EA Activation, security, and the enterprise CIO organization. We'll put under

    Responsibilities

    with
    • each. Next: "Required Qualifications" heading then paragraphs. We'll treat as Requirements or Qualifications? The instruction includes sections: Requirements, Qualifications, Skills. We need to decide which to use. The posting has "Required Qualifications" then bullet list of qualifications. Also later "Preferred Qualifications". Also "What You Own Core Responsibilities" which seems like more responsibilities but maybe we can merge. We need to avoid duplicate sections. We'll produce sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications), Preferred Qualifications (maybe as Qualifications?), Skills (maybe from Generative & Agentic AI etc). Benefits, Pay, Schedule. We need to include only sections with real content. Let's extract Required Qualifications bullet list: - Bachelor's Degree in Computer Science, Information Systems, or a related field. - 10+ years of progressive IT experience spanning product management, solution architecture, or a meaningful combination of both disciplines. - 5+ years of solution architecture or senior product ownership experience within healthcare IT; demonstrated delivery in regulated environments (HIPAA/PHI, HITECH); experience across payer, provider, pharmacy, or government health domains preferred. - Proven track record owning and prioritizing cross-functional product backlogs and roadmaps across multiple business lines or segments simultaneously, including managing competing stakeholder demands at the executive level. - Hands-on architecture experience with Azure services (Azure API Management, Event Hub, Service Bus, Azure Data Factory, AKS, Azure AD/Entra ID); working knowledge of Snowflake or Databricks data platform patterns. - Deep competency in API design and governance, event-driven architecture, and microservices patterns; experience with FHIR R4 and HL7 interoperability standards in healthcare contexts. - Demonstrated ability to produce reference architectures, architectural decision records (ADRs), and solution blueprints consumed by multiple engineering delivery teams. - Experience participating in and translating output from enterprise governance forums (ARB, TRB, MOR or equivalent) into actionable product and architecture direction. - Proficiency in agile and SAFe delivery models: backlog management, PI planning, iteration ceremonies, and dependency management across agile release trains. - Executive-level communication skills; able to synthesize complex architectural and product trade-offs into clear, concise recommendations for senior and C-suite audiences. That's a list. Preferred Qualifications: multiple sub-sections: CROSS-SEGMENT DOMAIN DEPTH, Agentic Ai & Platform Skills, ENTERPRISE ARCHITECTURE & GOVERNANCE. We'll need to extract bullet points. Let's extract each bullet. Under CROSS-SEGMENT DOMAIN DEPTH: - Experience supporting or architecting solutions for pharmacy benefit management (PBM), medication therapy management, specialty pharmacy, or retail pharmacy platforms, including integration with pharmacy dispensing systems and PBM claims engines. - Familiarity with TRICARE and military health benefit administration; experience with DoD/VA interoperability requirements, electronic health record systems used in military contexts, or government health benefit program integrations. - Experience with primary care clinical workflows, EMR integrations (Epic, Cerner, or equivalent), value-based care program architecture, or risk-stratified care management platforms. - Knowledge of Home Health operational workflows—clinical document management, authorization/eligibility automation, visit scheduling, and Home Health OASIS/PDGM reimbursement data requirements. - Demonstrated product or architecture leadership managing strategy across multiple business lines with distinct regulatory, operational, and technical profiles simultaneously. Under Agentic Ai & Platform Skills (looks like a list): - Agent orchestration: planning loops, tool/function calling, role assignment, and multi-agent collaboration patterns for production healthcare workflows. - Long- and short-term memory management, context window optimization, and retrieval strategies for AI assistants operating across complex, multi-domain knowledge bases. - Human-in-the-loop design: override workflows, confidence thresholds, escalation paths, and audit trails for AI outputs in clinically sensitive or compliance-gated contexts. - Telemetry and evaluation: distributed tracing, evaluation frameworks (LLM-as-judge, human eval pipelines), A/B testing for AI-assisted features, and latency/cost SLO definition. - Reliability patterns for agentic systems: structured retries, graceful fallbacks, circuit breakers, and deterministic handoffs between human and automated decision nodes. - FHIR R4 / SMART on FHIR integration patterns; familiarity with ONC interoperability and information-blocking rules as they apply to AI-enabled clinical data access. - Tool ecosystem integration: REST/GraphQL API orchestration, MCP server configuration, vector database design (Pinecone, Azure AI Search, pgvector), and feature store patterns for ML-adjacent workloads. Under ENTERPRISE ARCHITECTURE & GOVERNANCE: - Experience with enterprise identity and access management flows, Azure Active Directory / Entra ID group governance, and privileged access management within large multi-tenant healthcare environments. - Familiarity with portfolio governance and activation forums (ARB, TRB, MOR) and the ability to translate governance decisions into architecture-informed delivery runways across multiple agile release trains. - Knowledge of data mesh and data product patterns for distributed healthcare data ownership at segment scale, including federated governance and interoperability contracts. Now "What You Own Core Responsibilities" seems like more responsibilities but we already have Responsibilities section; we could merge or create another section like "Core Responsibilities". However instruction: Prefer a few substantive sections over many thin ones. We could incorporate those bullet points into Responsibilities as well. But we already have a Responsibilities list from DAY-TO-DAY. The "What You Own Core Responsibilities" includes items like: - Cross-Segment Product Strategy: Own and continuously evolve a shared platform product roadmap spanning Pharmacy, PCO, Home Solutions, and Humana Military. Balance segment-specific priorities against enterprise platform investments; facilitate structured prioritization across competing segment demands, and communicate decisions and rationale clearly to executives and delivery teams alike. - Solution Architecture Authority: Serve as the architectural decision-maker for cross-segment initiatives. Produce and maintain reference architectures, integration patterns, and design standards that guide delivery teams across all four segments. Author architectural decision records (ADRs) that capture context, alternatives considered, and governing rationale for reuse by future teams. - Backlog & Delivery Enablement: Own top-level product backlog items for shared platforms and cross-segment capabilities. Partner with segment-level product owners to decompose epics into executable user stories with well-defined acceptance criteria, architectural constraints, and measurable NFRs. Serve as the final arbiter on cross-segment feature scope and dependency sequencing. - Governance & Compliance Leadership: Lead architecture and product checkpoints for cross-segment solutions. Ensure all designs conform to enterprise security, privacy, and regulatory requirements including HIPAA/PHI, ONC interoperability rules, and DoD/TRICARE data standards where applicable. Represent the combined product and architecture voice in governance forums (ARB, TRB, MOR). - Data & Integration Strategy: Define integration contracts, API standards, and domain data boundaries for cross-segment data flows. Ensure observability, data lineage, and end-to-end data protection for shared assets spanning pharmacy benefit, clinical EMR, home health operational, and military health domains on Snowflake, Databricks, and Azure data platforms. - Platform Reuse & Pattern Stewardship: Proactively identify opportunities to reuse components, services, and architectural patterns across segments. Evangelize shared capabilities over duplicated build; build quantitative business cases for platform consolidation where segment convergence creates measurable efficiency and reduces long-term technical debt. - Stakeholder Alignment: Act as the primary connector between segment business leaders, product owners, engineering leads, EA Activation, security, data, and enterprise CIO teams. Translate complex architectural and product decisions into narratives that resonate at every level—from PI planning rooms to executive briefings—and maintain alignment across four distinct segment operating rhythms. These are also responsibilities. We could merge them with the DAY-TO-DAY list, but to avoid too thin sections, we could have a single Responsibilities section that includes all these bullet points. That would be substantive. Thus we will have one Responsibilities
      combining both sets. Now "Generative & Agentic AI" section earlier under Required Qualifications? Actually after Required Qualifications there is a heading "GENERATIVE & AGENTIC AI". That contains bullet-like paragraphs describing experience with AI/ML. This could be considered Skills or maybe part of Preferred Qualifications. We'll treat as Skills section. Extract bullet points from GENERATIVE & AGENTIC AI: - Demonstrated experience incorporating AI/ML capabilities into product strategy and architectural design, including Generative AI use cases such as clinical document NLP, prior authorization automation, member-facing conversational AI, or care gap identification. - Working knowledge of LLM integration patterns including RAG, prompt engineering, knowledge management, and fine-tuning; ability to evaluate platform options (Azure OpenAI, Amazon Bedrock, Vertex AI) and make informed build/buy/integr