Clinical Product Manager

We need to output HTML fragment with sections: About the role? The posting includes Position Overview, Key Responsibilities, Required Qualifications, Preferred Qualifications, What we offer, About Doctronic, Compensation Range. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not include Job ID etc. We must include sections only when posting has real specific content. Avoid filler like "commensurate with experience" - but we have Salary commensurate with experience; that is filler? The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. So we cannot create a Pay section if the content is just "Salary commensurate with experience" which is placeholder? Actually they gave a compensation range: $200K - $300K. That's specific. So we can include Pay section with that range. Also they have parental leave detail, which is a benefit. So Benefits section can include parental leave and maybe other benefits? They mention "Competitive equity package". That's a benefit. So we can include Benefits section with bullet points: Competitive equity package, 12 weeks fully paid parental leave. We also have "What we offer" includes direct impact, opportunity, work with world-class AI tech, shape partnerships, competitive equity package, salary commensurate with experience, parental leave. So we can split: Benefits (equity, parental leave), Pay (salary range), maybe also "Impact" etc could be under About the role? But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have content. We have Position Overview (could be About the role). Key Responsibilities -> Responsibilities. Required Qualifications -> Requirements (or Qualifications). Preferred Qualifications could be Skills? Or we could combine Required and Preferred under Qualifications? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide. We have medical background, product management experience, technical aptitude, leadership & communication. That's qualifications. Preferred qualifications could be Skills? Or we could have Qualifications (required) and Skills (preferred). Let's map: - About the role: Position Overview paragraph. - Responsibilities: Key Responsibilities (with sub-bullets). - Requirements: Required Qualifications (maybe as list). - Skills: Preferred Qualifications (maybe as list). - Benefits: What we offer (excluding salary and parental leave? Actually parental leave is benefit, equity package is benefit). We'll list those. - Pay: Compensation Range. - Schedule: Not mentioned, so omit. We must not include sections with filler. Ensure we preserve all substantive info. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include boilerplate like EEO etc. Not present. We must not repeat job title as heading. We must not include navigation etc. Let's craft. First, About the role: The Position Overview paragraph: "We seek a physician-product leader to drive the development of clinical pathways and workflows that power AI-native care delivery. This role sits at the intersection of clinical medicine, product management, and partner success—requiring deep medical expertise, proven product leadership, and the ability to translate complex clinical needs into scalable AI-enabled solutions for both our internal clinic and growing network of clinical partners." We'll put that in

  . Responsibilities: Key Responsibilities with three bullet areas each with subpoints. We'll create a

  with
  • for each main area, and inside each
  • we can have

    or further

    ? The instruction: Use
    • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
      with each responsibility as
      • . Inside each
      • we can have

        for the description and maybe a nested

        for subpoints. That seems okay. Requirements: Required Qualifications: list items: Medical Background (MD/DO, residency preferred, etc), Product Management Experience (3+ years, etc), Technical Aptitude (AI/ML understanding, etc), Leadership & Communication (stakeholder management, etc). We'll make
        • each. Skills: Preferred Qualifications: list items: Previous experience at healthcare tech companies, digital health startups, health systems innovation teams; Background in clinical informatics or health IT implementation; Understanding of HIPAA, healthcare data privacy, FDA regulations; Experience with prompt engineering, LLMs, or AI system development; MBA or other business/product training a plus. Benefits: What we offer: bullet points: Direct impact on healthcare accessibility for millions of patients; Opportunity to define how AI transforms clinical care delivery at a pioneering company; Work with world-class AI technology unique in the industry; Shape partnerships that will scale AI-native care across the healthcare ecosystem; Competitive equity package; 12 weeks fully paid parental leave for all parents, regardless of gender or path to parenthood — no distinction between birthing and non-birthing parents. We'll put those as
          • . Pay: Compensation Range: $200K - $300K. We'll put in

            . We must not include Schedule. Make sure not to include filler like "commensurate with experience". We have salary range specific, so fine. Now produce HTML fragment. Check for any repeated content: Ensure we didn't miss any substantive info: The "About Doctronic" paragraph: "Doctronic is the #1 AI Doctor, revolutionizing direct-to-patient healthcare through our proprietary AI system. Doctronic is the first AI legally authorized to practice medicine. We're processing millions of consultations monthly with 99%+ treatment plan accuracy validated by board-certified clinicians. Our platform (doctronic.ai) provides free, anonymous, HIPAA-compliant AI consultations alongside affordable human physician visits ($40) available 24/7 across all 50 states via instant video, scheduled video, or async text." This is substantive; we need to include it somewhere. Where? Could be under About the role? Or maybe a separate section like "About the Company". But headings list does not include About the Company. However we could incorporate it into About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; but we could also add other headings if needed? The instruction: "Use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings. It doesn't explicitly forbid others, but to be safe we should stick to those. Where to put About Doctronic? Could be part of About the role? Might be okay to append after the overview as another paragraph. The About the role section could contain both the position overview and company description. That seems acceptable. Thus About the role will have two paragraphs: first the position overview, second the About Doctronic description. Now ensure we didn't miss any other substantive info: The "Competitive equity package" already in benefits. Parental leave in benefits. Salary range in pay. Now produce HTML. We'll need to escape any HTML special characters? Not needed. Let's craft:

            About the role

            We seek a physician-product leader to drive the development of clinical pathways and workflows that power AI-native care delivery. This role sits at the intersection of clinical medicine, product management, and partner success—requiring deep medical expertise, proven product leadership, and the ability to translate complex clinical needs into scalable AI-enabled solutions for both our internal clinic and growing network of clinical partners.

            Doctronic is the #1 AI Doctor, revolutionizing direct-to-patient healthcare through our proprietary AI system. Doctronic is the first AI legally authorized to practice medicine. We're processing millions of consultations monthly with 99%+ treatment plan accuracy validated by board-certified clinicians. Our platform (doctronic.ai) provides free, anonymous, HIPAA-compliant AI consultations alongside affordable human physician visits ($40) available 24/7 across all 50 states via instant video, scheduled video, or async text.

            Responsibilities

            • Clinical Product Development (50%)

              • Own the product roadmap for clinical pathways, defining and prioritizing features that enable safe, effective AI-native care delivery
              • Design and iterate on clinical workflows for urgent care, primary care, chronic disease management, and medication management use cases
              • Translate clinical requirements into detailed product specifications for our AI engineering and context engineering teams
              • Drive product decisions grounded in clinical evidence, regulatory requirements, and real-world physician workflows

            • Partner Integration & Customization (35%)

              • Serve as the primary liaison for new clinical partners, leading discovery to understand their unique workflow requirements and use cases
              • Develop customized pathway configurations that adapt our AI platform to partner-specific clinical environments
              • Build scalable frameworks for partner onboarding that balance customization with product consistency
              • Gather and synthesize partner feedback to inform product roadmap priorities
              • Ensure successful deployment and adoption of clinical workflows across diverse partner settings

            • Cross-Functional Leadership (15%)

              • Collaborate daily with AI engineering, context engineering, and clinical operations to bring clinical products from concept to deployment
              • Partner with clinical leadership to ensure pathways meet quality standards and align with evidence-based medicine
              • Work with engineering on EHR integrations and interoperability requirements for partner implementations
              • Define success metrics and evaluation frameworks for clinical pathway performance
              • Coordinate with compliance and legal teams to ensure all products meet regulatory requirements

            Requirements

            • Medical Background: MD, DO, or equivalent medical degree (minimum requirement); Completed residency strongly preferred; post-residency clinical practice experience ideal; Deep understanding of clinical decision-making, care delivery workflows, and physician needs; Experience in urgent care, primary care, emergency medicine, or internal medicine preferred
            • Product Management Experience: 3+ years of product management experience, ideally in healthcare technology or digital health; Demonstrated ability to own product roadmaps from strategy through execution; Experience writing product requirements, user stories, and detailed specifications; Track record of shipping products that required cross-functional coordination
            • Technical Aptitude: Strong understanding of AI/ML systems and their application in healthcare settings; Experience deploying or implementing AI-enabled products in production environments preferred; Familiarity with EHR systems, clinical data standards (HL7, FHIR), and healthcare interoperability; Comfort with technical discussions and ability to collaborate effectively with engineering teams
            • Leadership & Communication: Exceptional stakeholder management skills with ability to navigate complex partner relationships; Strong written and verbal communication skills for both clinical and technical audiences; Experience working with or managing multidisciplinary teams; Ability to thrive in ambiguity and drive clarity in fast-moving environments

            Skills

            • Previous experience at healthcare technology companies, digital health startups, or health systems innovation teams