Technical Program Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes description, responsibilities, qualifications, benefits, compensation range. We need headings for sections that have real content. Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include. The posting includes: - Intro about Assured mission (maybe "About the role"? Actually it's about the company and role description). Could be "About the role" or "Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists. We have: - Some of the Problems You'll Solve: list of bullet points (with emojis). Those are responsibilities/duties. - How You'll Make an Impact: another list. - You'll Probably Thrive Here If You: list of qualifications/requirements. - Benefits: list. - Compensation Range: $165K - $185K (Pay section). - No explicit schedule. Thus we can have sections: About the role (intro paragraph), Responsibilities (combining Problems You'll Solve and How You'll Make an Impact maybe), Requirements/Qualifications (You'll Probably Thrive Here If You), Benefits, Pay. We must not repeat job title as heading. No Job ID. We must remove boilerplate: the warning about false recruiters, EEO statement, etc. Also remove application instructions (none). Remove duplicated lines. We must preserve all substantive information. We need to use

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

  for prose. We must not include sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine the introductory paragraphs up to "Some of the Problems You'll Solve:" maybe. Intro: "Assured is on a mission to modernize insurance. Claims processing (i.e. should we pay this claim?), while often overlooked, is the foundation of the entire industry. It’s currently highly manual, involving phone calls, faxes, and gut instinct, costing tens of billions of dollars a year. We can do better. At Assured, we provide large insurers with the software solutions they need to win in a modern, technology-driven world. From self-service claim-filing software to backend fraud detection, we’re the engine that powers claims processing for some of the largest insurers in the world. The challenges we face are deep and diverse, from creating digital experiences that provide comfort and clarity to claimants at their most stressed and vulnerable to orchestrating large-scale ML-driven decision-making on billions of dollars of claims payments, life at Assured is dynamic, collaborative, and rewarding." That's prose. Then Responsibilities: combine the bullet lists under "Some of the Problems You'll Solve:" and "How You'll Make an Impact:". We need to strip emojis? Probably keep them? The instruction didn't say to remove emojis, but they are part of content. We can keep them inside

• . Might be okay. We'll produce
  • for each bullet. Bullet list from "Some of the Problems You'll Solve:": - Bridge the gap between what Sales promised and what Eng can build. Sit between Client Engagement and Engineering to translate carrier requirements into scoped, sequenced work — surfacing conflicts early instead of letting them surface in a status meeting three weeks before launch. - Drive new carrier launches from kickoff to go-live. Own the cross-functional plan for onboarding a new carrier — dependencies, timelines, risk, and the dozens of small decisions that determine whether launch day is calm or chaotic. - Build the product ops muscle that doesn't exist yet. Design the intake process, prioritization framework, and status cadence that let carrier projects move through Product and Eng predictably, instead of every project reinventing how it gets tracked. - Make tradeoffs visible before they become fires. When a carrier asks for something new mid-project, figure out what it actually costs in eng time and timeline, and make sure the right people decide — instead of the request quietly absorbing into someone's backlog. - Be the translator, not just the tracker. Turn carrier-speak into engineering requirements and engineering constraints into carrier-facing answers, so neither side is negotiating in the dark. - Find the pattern across carrier projects. Notice when three carriers are hitting the same wall, and turn that into a platform fix instead of three one-off workarounds — this is the seed of the long-term platform PM role. - Keep multiple concurrent projects honest on timeline. Run the actual TPM mechanics — RAID logs, dependency mapping, critical path — for the highest-stakes carrier initiatives, without slowing engineering down with process for its own sake. Then "How You'll Make an Impact:" bullets: - Own carrier projects start to finish. Take a project from "the carrier wants X" through scoping, execution, launch, and the retro that makes the next one smoother. - Solve for ambiguity, not just execute a plan. Most carrier asks don't arrive scoped. You'll figure out what's actually being asked, what it takes to deliver it, and who needs to be in the room. - Keep things visible. Build the reporting and status rhythm that lets leadership, Client Engagement, and Eng all know where things stand without a meeting to find out. - Work as the connective tissue across teams. Client Engagement needs to trust your timelines. Eng needs to trust your scoping. You earn both by being precise about what you know and honest about what you don't. - Use AI to move faster. Use tools like Claude and similar platforms to help scope work, draft requirements, track dependencies, and keep documentation current without it eating your week. - Grow into platform product ownership. As you find the recurring patterns across carrier projects, take ownership of the platform capability that resolves them — this role is the on-ramp to a long-term PM seat, not a permanent ops function. We can combine both lists into one Responsibilities section, or split into two subsections? The instruction says prefer a few substantive sections over many thin ones. So combine into one Responsibilities
    . Now Requirements/Qualifications: "You'll Probably Thrive Here If You:" bullets: - Have real product ops or TPM experience. You've run cross-functional projects with real timeline and stakeholder pressure — ideally in a B2B SaaS or platform environment with external clients in the mix. - Are comfortable being the least technical person in an eng conversation and the most technical person in a client conversation. You don't need to write the code, but you need to understand enough about how systems work to scope honestly and push back on both sides. - Have appetite for ownership beyond your job title. You see product ops and TPM work as a way into the room, not the ceiling — you want to end up owning product decisions, not just orchestrating other people's. - Balance speed with rigor. You can get a launch plan moving on day one, but you don't skip the RAID log because it felt slow. - Lead through influence, not authority. You don't own the Eng roadmap or the Client Engagement relationship — you get both to move together by being the most trusted, most organized person in the project. - Learn the domain fast. You don't need insurance experience walking in, but you need to be the kind of person who can explain coverage validation to a new hire within a month of learning it yourself. We'll put these under a

    Requirements

    or

    Qualifications

    . The instruction list includes both Requirements and Qualifications as possible headings. We can choose Qualifications. Use

    Qualifications

    . Now Benefits: list from "Benefits:" section. We need to extract each benefit item: - Competitive Compensation: Competitive salary and equity packages for all employees - Healthcare Plan: Platinum medical, dental, and vision - Free life insurance: Including long-term disability & short-term disability - Unlimited PTO: Uncapped vacation days & paid holidays - Family Leave: Maternity & paternity - 401(k) Contribution: Assured contributes 3% of your income, even if you don't contribute - WFH Benefits: Lunch on us 2x/week, monthly phone stipend & other home office perks - Health FSAs & HSAs: Pre-tax accounts for out-of-pocket medical expenses - Team events & Offsites: We're remote, but we regularly get together We'll put each as
    • . Now Pay: compensation range: $165K - $185K. We'll put under

      Pay

      with

      $165K - $185K

      . Schedule: not present, so omit. Now ensure we removed boilerplate: the warning about false recruiters, EEO statement, etc. Also remove "Our Commitment: We are an equal opportunity employer..." etc. Also remove any duplicated lines (none). Now produce HTML fragment:

      About the role

      ... intro paragraph ...

      Responsibilities

      • ... each bullet ...
      ...

      Qualifications

      • ... each bullet ...
      ...

      Benefits

      • ... each benefit ...
      ...

      Pay

      $165K - $185K

      Make sure no extra whitespace issues. Now craft the intro paragraph exactly as given, but ensure we don't include any trailing spaces. Let's copy the intro: "Assured is on a mission to modernize insurance. Claims processing (i.e. should we pay this claim?), while often overlooked, is the foundation of the entire industry. It’s currently highly manual, involving phone calls, faxes, and gut instinct, costing tens of billions of dollars a year. We can do better. At Assured, we provide large insurers with the software solutions they need to win in a modern, technology-driven world. From self-service claim-filing software to backend fraud detection, we’re the engine that powers claims processing for some of the largest insurers in the world. The challenges we face are deep and diverse, from creating digital experiences that provide comfort and clarity to claimants at their most stressed and vulnerable to orchestrating large-scale ML-driven decision-making on billions of dollars of claims payments, life at Assured is dynamic, collaborative, and rewarding." Check for any stray characters: The original includes an em dash? It's fine. Now responsibilities bullets: need to ensure we keep the em dashes and punctuation. Let's list them exactly. I'll copy each bullet: 1. Bridge the gap between what Sales promised and what Eng can build. Sit between Client Engagement and Engineering to translate carrier requirements into scoped, sequenced work — surfacing conflicts early instead of letting them surface in a status meeting three weeks before launch. 2. Drive new carrier launches from kickoff to go-live. Own the cross-functional plan for onboarding a new carrier — dependencies, timelines, risk, and the dozens of small decisions that determine whether launch day is calm or chaotic. 3. Build the product ops muscle that doesn't exist yet. Design the intake process, prioritization framework, and status cadence that let carrier projects move through Product and Eng predictably, instead of every project reinventing how it gets tracked. 4. Make tradeoffs visible before they become fires. When a carrier asks for something new mid-project, figure out what it actually costs in eng time and timeline, and make sure the right people decide — instead of the request quietly absorbing into someone's backlog. 5. Be the translator, not just the tracker. Turn carrier-speak into engineering requirements and engineering constraints into carrier-facing answers, so neither side is negotiating in the dark. 6. Find the pattern across carrier projects. Notice when three carriers are hitting the same wall, and turn that