Senior Product Manager, New Clinic Launches

We need to output HTML fragment with sections: About the role, Responsibilities (maybe "What You'll Do"), Requirements (maybe "What You Bring"), Benefits, Pay, Schedule. Must only include sections with real specific content. The posting includes: - About Duet (company description) - not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections that have content: About the role (maybe "About The Role" heading), Responsibilities (maybe "What You'll Do"), Requirements (maybe "What You Bring"), Benefits (maybe none explicit? There's mention of equity, salary range, hybrid schedule). Pay: salary range $175-200k base + equity. Schedule: hybrid 3x/week in office, out of NYC. Benefits: maybe equity, but not explicit benefits like health etc. Could include "Benefits" if there is mention of equity? Might be considered compensation. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range and equity, and hybrid schedule. So we can include Pay and Schedule sections. Benefits: not explicitly listed besides equity (which is part of compensation). Could treat equity as part of Pay. Benefits maybe not present; we can omit Benefits section. Also include "Qualifications" maybe not needed; we have "What You Bring" which is requirements. Could map to Requirements or Qualifications. Use

for Requirements. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

... content from About The Role ...

Responsibilities

• ... each bullet from What You'll Do ...

Requirements

• ... each bullet from What You Bring ...

Pay

The salary range for this role is $175-200k base salary + equity.

Schedule

This role is hybrid 3x/week in office, out of NYC.

We must ensure we preserve all substantive information: also include KPIs You'll Own? That could be part of Responsibilities? Might be separate section but not in allowed headings list. Could include under Responsibilities as bullet. The instruction: Use headings only from list; we can add other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. We can incorporate KPIs into Responsibilities or maybe a separate "Qualifications"? Not appropriate. Could add a "Qualifications" heading for KPIs? Not ideal. Better to include KPIs as part of Responsibilities bullet list. Also include "Live inside the launch process." etc. That's part of What You'll Do. We need to preserve all substantive information: include details about shadowing, building roadmap, solving patient acquisition, building practice-facing experience, test community cohort models, work with engineers, hand off, KPIs. We need to ensure not to invent or summarize away detail: we must keep specifics like "days from signed agreement to first patient seen", "Milestone cycle time: days spent in each launch stage, and the variance across practices", etc. Thus in Responsibilities bullet list we can include each bullet as a sentence. Let's extract responsibilities from "What You'll Do": - Live inside the launch process. Shadow the practice advisors, join practice calls, sit with credentialing, billing, and EHR onboarding. Build a first-hand map of where a launch can stall, what gets repeated, and which pain is loudest for the NP versus most expensive for us. - Own the launch product roadmap. Turn what you learn into a prioritized set of bets across internal tooling, practice-facing product, and automation. Write the specs, make the tradeoffs, and defend the sequencing. - Solve patient acquisition as a product problem. Design and run experiments on how launching practices fill a schedule — paid channels, directory and marketplace presence, referral mechanics, local demand generation. Start scrappy and manual, measure honestly, and productize the channels that work into something we can run across a cohort rather than one practice at a time. - Build the practice-facing experience. Shape what a launching practice sees, does, and gets nudged toward in our product during their first ninety days, so the product carries more of the relationship over time. - Test community and cohort models. Explore whether launching NPs get more from each other than from us — cohort programming, peer content, shared playbooks — and build the ones that show signal. - Work directly with engineers. Partner with a small team to scope, ship, and iterate. Prototype yourself where it's faster. Be technical enough to be useful in a design discussion and honest about tradeoffs. - Hand off cleanly. Get each piece of the Launcher experience to the point where it's documented, instrumented, and stable enough to transition to our core product team, then go find the next bottleneck. - KPIs You'll Own: Time to launch: days from signed agreement to first patient seen; Milestone cycle time: days spent in each launch stage, and the variance across practices; Patient acquisition cost and payback by channel; Share of launch steps that are automated or self-serve rather than human-mediated; NP-reported experience of the launch process. We need to keep each as bullet. Now "What You Bring": - 5+ years in product management, ideally including 0-to-1 work where the problem space was undefined and you were the one who defined it. Founding PM, new-product, or internal-platform experience is all relevant. - Experience in an operationally complex domain — healthcare, fintech, logistics, marketplaces, or another environment where software has to accommodate messy real-world processes and regulated constraints. - A track record of turning manual operations into product. You've watched a team do something by hand, understood why, and shipped the thing that stopped them from having to. You can point to specific examples and the before-and-after numbers. - Real experimentation discipline. You think in hypotheses, know how to design a test that can actually fail, and can tell a real signal from a flattering one in a small sample. - Technical depth to work with engineers as a peer. You can reason about integrations, data models, and APIs, evaluate a build-versus-buy call, and prototype when prototyping is faster than speccing. - Growth instincts. You've been close enough to acquisition — paid channels, funnels, CAC, conversion — to run a channel test yourself rather than hand it to someone else. - Nice to Have: Experience with EHR, practice management, revenue cycle, or credentialing systems; Background in provider enablement, practice management, or small-business enablement platforms; Experience with local or multi-location patient or customer acquisition; Time spent in an operations role before moving into product. - Who Will Thrive Here: You want to build the system, not run it. You'll be tempted to just fix the launch yourself; the job is to make the fix unnecessary next time. You prefer to be measured on business outcomes rather than shipped features. You’d rather run three scrappy experiments this month than write one perfect PRD. We could include these as bullet list under Requirements. Might be long but okay. Now "About The Role" paragraph: we need to include that section content. Extract "About The Role": Today NPs come to Duet to launch their clinics for its community of owners, special vendor deals, enhanced payor contracts, and advisor guidance. Your job is to productize this experience. You'll sit close enough to the work to understand it in detail: sitting in on practice onboarding, watching how practice advisors actually spend a Tuesday, working with credentialing and billing. From there you’ll lead building the systems, workflows, and products that make the next launch faster and more delightful. This is a 0-to-1 role in the real sense: how does a new practice acquire its first hundred patients, and which of those channels can be managed at scale? What does a launching practice actually need to see and do each week, and how much of that can our product guide them vs an advisor? You'll form opinions on these, design experiments to test them, and work with engineers to build what survives contact with reality. The measure of your success is that the Launcher experience becomes a repeatable system that takes driven NPs and helps them fill up their practices. We'll put that in

. Now Pay: salary range $175-200k base + equity. Schedule: hybrid 3x/week in office, out of NYC. We might also include location: NYC. Now ensure we don't include any boilerplate like "About Duet", "Why Duet, Why Now", etc. Those are not required headings; we can omit them. Now produce HTML. We must not include markdown fences. Let's craft:

About the role

Today NPs come to Duet to launch their clinics for its community of owners, special vendor deals, enhanced payor contracts, and advisor guidance. Your job is to productize this experience. You'll sit close enough to the work to understand it in detail: sitting in on practice onboarding, watching how practice advisors actually spend a Tuesday, working with credentialing and billing. From there you’ll lead building the systems, workflows, and products that make the next launch faster and more delightful. This is a 0-to-1 role in the real sense: how does a new practice acquire its first hundred patients, and which of those channels can be managed at scale? What does a launching practice actually need to see and do each week, and how much of that can our product guide them vs an advisor? You'll form opinions on these, design experiments to test them, and work with engineers to build what survives contact with reality. The measure of your success is that the Launcher experience becomes a repeatable system that takes driven NPs and helps them fill up their practices.

Responsibilities

• Live inside the launch process. Shadow the practice advisors, join practice calls, sit with credentialing, billing, and EHR onboarding. Build a first-hand map of where a launch can stall, what gets repeated, and which pain is loudest for the NP versus most expensive for us.
• Own the launch product roadmap. Turn what you learn into a prioritized set of bets across internal tooling, practice-facing product, and automation. Write the specs, make the tradeoffs, and defend the sequencing.
• Solve patient acquisition as a product problem. Design and run experiments on how launching practices fill a schedule — paid channels, directory and marketplace presence, referral mechanics, local demand generation. Start scrappy and manual, measure honestly, and productize the channels that work into something we can run across a cohort rather than one practice at a time.
• Build the practice-facing experience. Shape what a launching practice sees, does, and gets nudged toward in our product during their first ninety days, so the product carries more of the relationship over time.
• Test community and cohort models. Explore whether launching NPs get more from each other than from us — cohort programming, peer content, shared playbooks — and build the ones that show signal.
• Work directly with engineers. Partner with a small team to scope, ship, and iterate. Prototype yourself where it's faster. Be technical enough to be useful in a design discussion and honest about tradeoffs.
• Hand off cleanly. Get each piece of the Launcher experience to the point where it's documented, instrumented, and stable enough to transition to our core product team, then go find the next bottleneck.