Senior Technical Product Manager (AI Data Platform), Remote

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to parse the posting. Key sections: - About the role: description of team, mission. Could be first paragraph: "Aledade is dedicated to transforming value-based care through innovative technology. Our AI Platform team is at the forefront, building the foundational tools, services, and infrastructure that empower internal product teams to seamlessly integrate cutting-edge AI capabilities into Aledade’s products and develop powerful internal AI solutions. As a Senior Technical Product Manager on the AI Data Platform team, you will be instrumental in defining and delivering the roadmap to drive the execution and scale of our AI Data Platform that supports internal stakeholders and external AI products. You’ll work at the intersection of machine learning systems, data engineering, and applied healthcare AI, partnering closely with AI engineers, data scientists, and clinical leadership to deliver production-grade agentic retrieval and context graph solutions that enable LLM-powered tools to find and use relevant data to support value-based care workflows. Your contributions will help improve quality and cost of care for over 2 million patients who are treated by Aledade providers." That's about the role. - Responsibilities: "Primary Duties:" list bullet points. We need to extract each bullet. List: - Partner with business owners to cultivate a shared vision for the problem space, constraints, priorities and ideal end state, and be able to articulate and advocate for this perspective. - Lead the full lifecycle of ML and LLM platform workstreams; from data ingestion, training, and deployment to the ongoing optimization of live user workflows based on performance metrics and feedback - Work with internal teams and end users to develop a deep understanding of requirements, perform thoughtful solution design, use data to test hypotheses, and support teams throughout execution. - Write detailed user stories for new features, capturing detailed descriptions of business rationale, requirements, and success criteria that are defined by measurable outcomes. - Develop short- and long-term roadmaps that deliver maximum value with minimum risk and assume ongoing iteration. - Partner with AI Researchers to mature proofs-of-concept into production-ready capabilities. - Perform hands-on exploration of user feedback, healthcare records and validation data to validate model performance. - Requirements: Minimum Qualifications list. List: - 8+ years of product management experience in technology, technology-enabled services industry, or a SaaS product. - Robust understanding of artificial intelligence and/or machine learning, and related technologies. - Experience using data and primary research to inform solution design and build internal business understanding. - Experience with Agile teams, Jira, and understanding of the software development lifecycle - Strong understanding of APIs, DevOps, enterprise software development, cloud infrastructure (databricks/AWS/GCP/Azure), and data engineering principles. - Exceptional ability to communicate technical trade-offs to non-technical stakeholders. - Comfortable with translating ambiguous product requirements into a technical roadmap - Qualifications: Preferred Knowledge, Skills and/or Abilities list. List: - Experience working on or leading products for an AI/ML platform team and building a platform to scale vertically and horizontally. - Proven track record of building and launching AI/ML platforms, tools, or internal services that enable other product teams. - Deep understanding of the AI/ML product lifecycle, MLOps, and scalable AI infrastructure (e.g., model training, deployment, monitoring, observability, reliability). - Experience with large language models (LLMs) and generative AI technologies, including prompt engineering strategies and VLMs. - Experience working as a data scientist or backend engineer. - Strong ability to translate technical concepts and platform capabilities into value propositions and storytelling skills to communicate to diverse internal stakeholders. - Clinical Data Literacy: Familiarity with EHR data, Claims, or population health datasets. - Experience in a healthcare technology environment, including physician-facing products or working with clinical datasets (EHR data, Claims, Population Health datasets, etc). - Skills: maybe combine with Preferred? But we can have a Skills section if there is content. The posting includes "Physical Requirements" but that's not a skill. Could treat "Physical Requirements" as not needed. The "Skills" could be derived from Preferred list? But we already have Qualifications (Preferred). The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred), Skills (maybe we can extract from Preferred list? But we already used Qualifications for preferred. Could treat Qualifications as minimum, Skills as preferred? But they said "Qualifications" and "Skills" separate. Usually Qualifications = minimum qualifications, Skills = preferred skills. However they gave both Minimum Qualifications and Preferred Knowledge, Skills and/or Abilities. So we can map Minimum Qualifications -> Requirements, Preferred -> Skills. But they also have a separate "Qualifications" heading. Hmm. The list of possible headings includes both Requirements and Qualifications and Skills. We need to decide which to use. The posting has Minimum Qualifications and Preferred Knowledge, Skills and/or Abilities. So we could use Requirements for Minimum Qualifications, and Skills for Preferred Knowledge, Skills and/or Abilities. Then we might not need a separate Qualifications section. Or we could use Qualifications for Minimum Qualifications and Skills for Preferred. But they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose any of those that have content. We need to avoid empty sections. Thus we could have: - About the role - Responsibilities - Requirements (minimum qualifications) - Skills (preferred knowledge/skills) - Benefits (benefits package) Maybe also Pay and Schedule if present. The posting does not mention pay or schedule specifics. It mentions flexible work schedules and ability to work remotely are available for many roles. That's schedule info? It says "Flexible work schedules and the ability to work remotely are available for many roles". That's schedule info. So we could include Schedule section with that statement. Pay: not mentioned. So we omit Pay. Benefits: they list many benefits. So we include Benefits. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Check if any other sections like Qualifications needed? We'll skip. Now we need to format. Use

for each heading. Then content: for prose use

. For lists use

• . We must not repeat job title. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight punctuation). Ensure we don't drop any. Let's extract exact text. About the role paragraph: We'll combine the first few sentences up to "over 2 million patients who are treated by Aledade providers." That's one paragraph. Responsibilities bullets: need to keep each bullet exactly as in posting. Let's copy them: - Partner with business owners to cultivate a shared vision for the problem space, constraints, priorities and ideal end state, and be able to articulate and advocate for this perspective. - Lead the full lifecycle of ML and LLM platform workstreams; from data ingestion, training, and deployment to the ongoing optimization of live user workflows based on performance metrics and feedback - Work with internal teams and end users to develop a deep understanding of requirements, perform thoughtful solution design, use data to test hypotheses, and support teams throughout execution. - Write detailed user stories for new features, capturing detailed descriptions of business rationale, requirements, and success criteria that are defined by measurable outcomes. - Develop short- and long-term roadmaps that deliver maximum value with minimum risk and assume ongoing iteration. - Partner with AI Researchers to mature proofs-of-concept into production-ready capabilities. - Perform hands-on exploration of user feedback, healthcare records and validation data to validate model performance. Check punctuation: some have trailing period, some not. We'll keep as is. Requirements (minimum qualifications) bullets: - 8+ years of product management experience in technology, technology-enabled services industry, or a SaaS product. - Robust understanding of artificial intelligence and/or machine learning, and related technologies. - Experience using data and primary research to inform solution design and build internal business understanding. - Experience with Agile teams, Jira, and understanding of the software development lifecycle - Strong understanding of APIs, DevOps, enterprise software development, cloud infrastructure (databricks/AWS/GCP/Azure), and data engineering principles. - Exceptional ability to communicate technical trade-offs to non-technical stakeholders. - Comfortable with translating ambiguous product requirements into a technical roadmap Note: some missing period at end; we keep. Skills (preferred knowledge, skills and/or abilities) bullets: - Experience working on or leading products for an AI/ML platform team and building a platform to scale vertically and horizontally. - Proven track record of building and launching AI/ML platforms, tools, or internal services that enable other product teams. - Deep understanding of the AI/ML product lifecycle, MLOps, and scalable AI infrastructure (e.g., model training, deployment, monitoring, observability, reliability). - Experience with large language models (LLMs) and generative AI technologies, including prompt engineering strategies and VLMs. - Experience working as a data scientist or backend engineer. - Strong ability to translate technical concepts and platform capabilities into value propositions and storytelling skills to communicate to diverse internal stakeholders. - Clinical Data Literacy: Familiarity with EHR data, Claims, or population health datasets. - Experience in a healthcare technology environment, including physician-facing products or working with clinical datasets (EHR data, Claims, Population Health datasets, etc). Benefits: list from posting: - Flexible work schedules and the ability to work remotely are available for many roles - Health, dental and vision insurance paid up to 80% for employees, dependents and domestic partners - Robust time-off plan (21 days of PTO in your first year) - Two paid volunteer days and 11 paid holidays - 12 weeks paid parental leave for all new parents - Six weeks paid sabbatical after six years of service - Educational Assistant Program and Clinical Employee Reimbursement Program - 401(k) with up to 4% match - Stock options - And much more! We should keep each as bullet. Schedule: we have "Flexible work schedules and the ability to work remotely are available for many roles". That's already in Benefits list as first bullet. But we might want to separate schedule. However the instruction: include a section ONLY when posting has real, specific content for it. The schedule info is present; we could put it in Schedule section. But we already used it in Benefits. Could duplicate? Better to keep schedule separate and remove from Benefits? But we must preserve ALL substantive information; we cannot remove it. If we move it to Schedule, we still need to keep it somewhere. We could keep it in Benefits as well, but that would duplicate. Duplication is discouraged? They said remove duplicated lines. So we should not duplicate. So we need to decide where to place it. The schedule info is about flexible work schedules and remote work. That's more about schedule than benefits. So we can put it in Schedule section, and not include it in Benefits. Then Benefits section will have the rest. Thus Benefits bullets exclude the first item. Schedule section: one bullet: "Flexible work schedules and the ability to work remotely are available for many roles". Now Benefits bullets list remaining items. Check if any other schedule info: none. Now ensure we don't include Pay section. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Skills

  ...

  Benefits

  ...

  Schedule