Technical Program Manager - Pharmacy Care

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow specific rules: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID/requisition numbers as headings 5. Preserve ALL substantive information 6. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) 7. Include a section ONLY when the posting has real, specific content for it 8. Never emit a heading followed by filler/placeholder text 9. Never create Pay/Schedule/Benefits sections unless the posting actually states them 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting: The posting has: - An introductory paragraph about the role (Technical Program Manager, Pharmacy Care) - "What you'll do" section with multiple subsections: - Own the program end to end - Drive the technical integration - Run governance and quality - Carry the regulated-delivery load - Build the operating model - "What we're looking for" with Required and Preferred qualifications - "Who we are" section about Transcarent - "Total Rewards" section with compensation and benefits info I need to structure this into appropriate sections. The user mentioned using

  for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". Looking at the content: - The intro paragraph is "About the role" - "What you'll do" maps to "Responsibilities" - "What we're looking for" maps to "Requirements" and "Qualifications" (Required and Preferred) - "Total Rewards" maps to "Benefits" and "Pay" (since it mentions salary, bonus, stock options, and benefits) I should not include "Who we are" as it's company boilerplate, but the user said to remove boilerplate. However, "Who we are" might be considered company description. The instructions say to remove "cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "Who we are" section is company marketing, not exactly boilerplate but could be considered non-essential. However, the user said "Preserve ALL substantive information". I think I should include it as "About the company" or similar, but the user didn't list that as a heading. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Who we are" doesn't fit neatly. Maybe I can fold it into a short

  or drop it. The user said "fold minor metadata into a short

  or drop it." This is more than minor metadata. But it's not a core job requirement. I'll include it as a brief paragraph under "About the role" or as a separate section? The user said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So only those headings. I should not create new headings. So I'll incorporate "Who we are" into "About the role" as a paragraph. Similarly, "Total Rewards" contains both Pay and Benefits info. I'll split into Pay and Benefits sections. Now, let's structure: 1.

  About the role

  - includes the intro paragraph and maybe the "Who we are" paragraph. 2.

  Responsibilities

  - the "What you'll do" section with its subsections as lists. 3.

  Requirements

  - the Required qualifications. 4.

  Qualifications

  - the Preferred qualifications (or maybe combine with Requirements? The user listed both Requirements and Qualifications as separate headings. Usually Requirements are required, Qualifications are preferred. I'll use Requirements for required, Qualifications for preferred.) 5.

  Benefits

  - the benefits list. 6.

  Pay

  - the compensation info (salary, bonus, stock options). The posting doesn't mention Schedule, so no Schedule section. Now, I need to convert each bullet point into
  • . The "What you'll do" has subsections with prose and bullet-like items. I'll create a list for each major responsibility area, but the user said "Use
    • for any list of duties/requirements/benefits, and

      for prose." So for each duty, I can make a list item. However, the "What you'll do" has five major areas, each with multiple sentences. I could make each area a list item with sub-bullets? But the instruction says

      • for any list. I think I'll create a list for each major area, with each bullet being a key responsibility. But the content is prose. I'll break down each paragraph into separate list items where appropriate. Let's parse "What you'll do": - Own the program end to end: multiple sentences. I'll make each sentence a list item? Or group related sentences. Better to keep each distinct responsibility as a list item. I'll create a
        for Responsibilities, with each
        • being a distinct duty. But there are many. I'll follow the structure: maybe use nested lists? The user didn't forbid nested lists. But they said "Use
          • for any list of duties/requirements/benefits". So I can have a top-level list for each major area, with sub-lists for details. However, the example headings are flat. I'll keep it simple: one list for all responsibilities, each item a major duty. But the posting has five major areas. I'll make each area a list item with a bold lead? But HTML doesn't have bold in spec. I can use inside
          • . That's acceptable. Alternatively, I can use

            for subsections? The user only allowed

            for section headings. Not

            . So I'll stick to

            for main sections and use

            • for lists. I'll structure Responsibilities as a single
              with each major area as a
              • containing a for the area title and then a
                for sub-items? That would be nested lists. That's okay. But the user said "Output ONLY the HTML fragment". I'll produce clean HTML. Let's start writing. First, About the role: combine the intro paragraph and the "Who we are" paragraph. Intro paragraph: "The Technical Program Manager, Pharmacy Care owns the delivery of our largest and most complex pharmacy platform programs. This is a hands-on technical delivery role for someone who can hold a multi-party, multi-phase implementation together: integration dependencies across organizations, contractual milestones with defined acceptance criteria, regulated launch requirements, and a phased rollout that moves from a controlled pilot all the way through government-program populations. You will be the connective tissue between Product, Engineering, Design, Solutions, Data, Security, Compliance, Client Services, Service Delivery, and external partners. The work is equal parts technical fluency and program discipline. You need to be able to read an API specification, run the integration conversation on your own, and then convert what you heard into a plan, a dependency, or an escalation. If a date is going to move, you know first and you say so early. This program delivers a pharmacy-first digital member experience: medicine cabinet, claims and prior-authorization visibility, real-time price transparency, benefit and accumulator presentment, digital ID cards, document access, member notifications, an AI care assistant, and the partner integrations that power all of it." Who we are: "Transcarent is the One Place for Health and Careᵀᴹ, bringing medical, pharmacy, and point solutions together with the WayFinding ᵀᴹ experience, the first and only generative AI-powered health and care platform for health consumers. Our WayFinding experience, paired with transparent and consumer-driven pharmacy care, 2nd.MD expert medical opinions, and virtual primary care, works seamlessly with comprehensive Care Experiences — Cancer Care, Surgery Care, and Weight Health — to support people with all of their health needs, simple or serious. More than 1,700 employers and health plans rely on us to provide information, guidance, and care, empowering health consumers with more choice, an experience they love, access to higher-quality care, and lower costs for 21 million Members. Our Values Guide Everything We Do People First: We prioritize our Members, clients, and each other in every decision Care: Every decision starts with improving health and care for our Members Resilience: We push boundaries and take the uncharted path to change an industry Results: We take ownership, solve with speed, and deliver for our people and each other Humble and Human: We lead with humility, bring fun to tough moments, and go further together" I'll include both as paragraphs under About the role. Responsibilities: I'll create a list with five main items, each with sub-items. Let's break down each area: 1. Own the program end to end - Own delivery of a multi-phase, enterprise-scale platform implementation from mobilization and discovery through pilot, staged client rollout, and transition to ongoing operations. - Structure the program into workstreams with clear owners, milestones, and exit criteria. - Build and maintain the integrated program plan: scope, milestones, critical path, dependencies, acceptance criteria, and readiness gates across every workstream. - Sequence phased rollout waves: internal pilot, shared pilot clients, standard commercial rollout, strategic accounts, and regulated and government-program populations. - Drive milestone attainment where milestones carry contractual acceptance criteria and commercial consequence. Know exactly what must be true for each gate to close. 2. Drive the technical integration - Coordinate delivery across the full integration surface: eligibility, identity and authentication, claims history, accumulators, formulary and medication data, real-time pricing, prior-authorization status and intake, document retrieval, event and webhook interfaces, notifications, and federated SSO connections. - Work with Engineering and Architecture on integration design, data mapping, identifier reconciliation across systems, environment strategy, and interface specifications covering authentication, schemas, idempotency, error handling, monitoring, and reconciliation. - Hold the line on data quality and interface readiness, real-time versus batch trade-offs, validation rigor, and what happens when bad data moves downstream fast. - Manage partner-side technical dependencies rigorously: API documentation and sandbox access, file specifications and cadence, test data and credentials, environment provisioning, technical SMEs, and approvals. Track them, age them, and escalate with evidence before they become schedule impacts. 3. Run governance and quality - Establish and run program governance: meeting cadence, status reporting, RAID log, decision records, RASCI ownership across organizations, and executive-level reporting that tells the truth concisely. - Own scope discipline. Distinguish clarification from expansion, route genuine change through a documented change-control process and protect the committed timeline. - Partner with QA and Engineering to maintain a live quality and release-readiness view: test coverage and execution, defect counts by severity and trend, automation and regression status, environment and test-data blockers, and an honest Green/Yellow/Red call. - Produce release readiness summaries ahead of each major milestone: included and deferred scope, test and UAT completion, open defects and mitigations, security, privacy, performance and accessibility results, residual risk, and a clear Go / Go-with-conditions / No-Go recommendation. - Run post-production validation after each go-live —