ConvergeHEALTH Life Sciences - Product Management & Strategy Manager - Innovation_Delivery_Transformation

We need to output HTML fragment with sections: About the role? Actually the posting includes "The Team", "Position Summary", "Work you'll do" with subsections: Product Strategy & Roadmap Ownership, Market & Client Insight, Go-to-Market & Commercial Enablement, "The successful candidate would possess these skills:" (skills), "Qualifications Required:", "Preferred:", wage range, incentive program. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to these headings appropriately. We need to include sections only when posting has real specific content. We should not repeat job title. No Job ID. Remove boilerplate. We need to decide which sections to include: About the role (maybe from "The Team" and "Position Summary"?). Responsibilities (maybe from "Work you'll do" subsections). Requirements (Qualifications Required). Skills (maybe "The successful candidate would possess these skills:" and "Preferred:"). Benefits (maybe wage range and incentive program). Pay (maybe wage range). Schedule (maybe travel requirement). However we must not create sections with placeholder text. We have actual content for Pay (wage range) and Schedule (travel 20-25%). Benefits maybe incentive program. We need to use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details. We need to avoid duplication. Let's parse content: - The Team paragraph: description of team. - Position Summary: description of role. - Work you'll do: three bullet-like sections (Product Strategy & Roadmap Ownership, Market & Client Insight, Go-to-Market & Commercial Enablement). Each contains multiple sentences, some bullet-like but not explicit list. We can treat each as a

  or we could break into

  • for each duty? The instruction: Use
    • for any list of duties/requirements/benefits. The content is not explicitly a list but we could still format as paragraphs. Safer to use

      for prose. Only use

      • when there is a list. There's no explicit bullet list; but we could treat each duty as a list item? Might be okay but risk of adding structure not present. Safer to use

        for each subsection. - The successful candidate would possess these skills: list of skills (Cross-Functional Leadership etc). This is a list; we can use

        • . - Qualifications Required: list of qualifications (Bachelor's degree..., 4-5 years..., 3-5 years..., Experience..., Demonstrated ability..., Deep familiarity..., Proficiency..., Proven track record..., Ability to travel..., Must be legally authorized...). This is a list; use
          • . - Preferred: list of preferred qualifications (Familiarity with AI/ML..., Familiarity with Agentic AI..., Comfort with modern data...). Use
            • . - Pay: wage range paragraph: "The wage range for this role takes into account... A reasonable estimate of the current range is $134,500 to $265100." Also mention discretionary annual incentive program. This is Pay and Benefits. - Schedule: travel 20-25% mention. We need to avoid creating sections with placeholder text. All sections have content. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should not duplicate similar headings. The instruction says use

              for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems we can choose which to include. We should not create both Qualifications and Requirements if they overlap; but we have both Qualifications Required and Preferred. Could map Qualifications Required to Requirements section, and Preferred to Skills? Or Skills section for the skills list. About the role could combine The Team and Position Summary. Responsibilities could be Work you'll do. Benefits could be incentive program. Pay could be wage range. Schedule could be travel. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft:

              About the role

              The Team ... Position Summary ...

              combine.

              Responsibilities

              Product Strategy & Roadmap Ownership: ...

              Market & Client Insight: ...

              Go-to-Market & Commercial Enablement: ...

              Skills

              • Cross-Functional Leadership: Act as a strategic thought partner ...
              ... etc. But we need to keep the content exactly as in posting, not summarizing. So we need to copy the sentences. Let's extract each bullet: From "The successful candidate would possess these skills:": - Cross-Functional Leadership: Act as a strategic thought partner to Product Management, Engineering, UX, and Delivery leaders, ensuring strategic intent is preserved through execution. Facilitate strategic planning sessions, roadmap reviews, and prioritization forums with senior stakeholders across Deloitte and ConvergeHEALTH. Contribute to practice-building efforts, including points of view, whitepapers, and conference presentations, to establish Deloitte as a thought leader in AI-driven market access transformation. Leverage rapid prototyping and AI tools (e.g., Cursor, Lovable, N8N) to bring strategic concepts to life as demonstrable ideas that accelerate alignment and feedback. That's one long sentence; we keep as is. Next maybe there are more? Actually after that, the posting goes to "Qualifications Required:" So only that one skill bullet? It says "The successful candidate would possess these skills:" then only one item described. So we will have a single
              • .

                Requirements

                (or Qualifications). We'll use Requirements for Qualifications Required. List each qualification: - Bachelor's degree (Master's degree preferred) in life sciences, health economics, business strategy, computational biology, or related field. - 4-5 years of experience working as an employee of a life sciences company (pharmaceutical, biotech, or medical products). - 3-5 years of combined experience in Life Science market access environments and product management, management consulting, or technology product roles. - Experience in a SaaS or enterprise software product organization in the life sciences, health tech, or pharmaceutical commercial operations space. - Demonstrated ability to develop and communicate product strategy - including market sizing, competitive positioning, and roadmap rationale - to senior audiences. - Deep familiarity with pharmaceutical market access workflows - including pre-deal modeling, deal strategy, contract development, contract execution, post-deal pull-through, and rebate adjudication. - Proficiency with the key data assets that power market access decisions, including formulary and PDL data, covered lives, rebate and chargeback transaction data, GTN waterfall components (WAC, rebates, Medicaid best price, 340B, copay), script-level claims (e.g., IQVIA LAAD, Symphony Health), copay voucher data, hub and patient enrollment data, and syndicated benchmarks (e.g., SSR Health, CMS MDRP). - Proven track record of synthesizing complex inputs (market data, user research, business context) into clear, actionable strategic recommendations. - Ability to travel 20-25%, on average, based on the work you do and the clients and industries/sectors you serve. - Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future. Note: travel appears also in Schedule; but we can keep it in Requirements as it's a qualification. However we might also create Schedule section for travel. But we should not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put travel in both Requirements and Schedule, that's duplication. Better to keep travel only in Schedule section, and remove from Requirements? But the requirement list includes travel as a qualification. If we remove it, we lose that detail. We could keep it in Requirements and not create Schedule section, or we could keep it in Schedule and also keep it in Requirements but that duplicates. The instruction says do not duplicate lines. So we need to avoid duplication. We could decide to put travel in Schedule section and not include it in Requirements list. But then we would be omitting that qualification from Requirements, which is not allowed (must preserve ALL substantive information). So we need to keep it somewhere; we could keep it in Requirements and not have a separate Schedule section. However the instruction says we should include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having a Schedule section if we have content; but we must not duplicate. So we could include Schedule section with travel content, and remove travel from Requirements list (but then we lose that qualification). However the qualification list includes travel as a qualification; maybe we can keep it there and not have Schedule. The instruction about Schedule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state travel 20-25% (under Qualifications Required). So we could create a Schedule section with that content, and also keep it in Qualifications? That would be duplication. To avoid duplication, we could move the travel bullet to Schedule section and not include it in Qualifications. But then we are missing that qualification from the Qualifications section. However the Qualifications section is meant to capture qualifications; travel is a qualification (ability to travel). If we omit it, we lose that qualification. But maybe we can keep it in both places but rephrase? That would be duplication of same sentence, which is disallowed. So we need to decide. Perhaps we can treat travel as part of Schedule, and still keep it in Qualifications but rephrase? That would still be duplication of meaning. The instruction says "do NOT put duplicated lines". It might refer to exact duplicated lines, not necessarily same meaning. But safer to avoid duplication. We could keep travel in Qualifications and not create a Schedule section. The posting does mention travel, but we could argue that Schedule section is optional; we can omit it if we prefer not to create thin section. The instruction: "Prefer a few substantive sections over many thin ones." So we could omit Schedule and keep travel in Qualifications. That seems acceptable. Similarly, Benefits: we have discretionary annual incentive program. We could create Benefits section with that content. Pay: wage range. Thus sections: About the role, Responsibilities, Skills, Requirements, Pay, Benefits. We need to use

                for each. Now we need to ensure we preserve all substantive information: The Team, Position Summary, Work you'll do (three subsections), The successful candidate would possess these skills (one bullet), Qualifications Required (list), wage range, incentive program. We must not include boilerplate like "Recruiting for this role ends on 10/31/26." That's a date; is that substantive? It's recruiting end date. Might be considered metadata but not boilerplate. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

                or drop it." The recruiting end date is minor metadata; we could fold into a short

                or drop it. Probably drop it as it's not essential. But we need to preserve ALL substantive information; is end date substantive? Might be considered minor metadata; we could drop it. Safer to drop it. Also "At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case." That's commentary about pay; maybe we keep as part of Pay section. We also have "The disclosed range estimate has not been adjusted for the applicable geographic differential associated with the location at which