Product Manager, Risk

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - Who We Are: description of company. Could be "About the role"? Actually "Who We Are" is about company, not role. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. Likely "About the role" corresponds to description of what we're looking for (the role). "Responsibilities" corresponds to bullet list of duties. "Requirements" maybe qualifications. "Qualifications" maybe preferred? "Skills" maybe specific skills. "Benefits" from "We will offer you…". "Pay" maybe mention of competitive compensation. "Schedule" maybe not present. We must only include sections if posting has real specific content. Let's identify content: Company description: "Who We Are Zus is a shared health data platform designed to accelerate healthcare data interoperability by providing easy-to-use patient data via API, embedded components, and direct EHR integrations. Founded in 2021 by Jonathan Bush, co-founder and former CEO of athenahealth, Zus partners with HIEs and other data networks to aggregate patient clinical history and then translates that history into user-friendly information at the point of care. Zus's mission is to catalyze healthcare's greatest inventors by maximizing the value of patient insights - so that they can build up, not around." That's about company, not role. Could be placed under "About the role"? Might be better as a brief intro but not required. The instruction says use those headings; we can include "About the role" with description of role and maybe company context. Next: "What we're looking for We are seeking a Product Manager to own a portion of our value-based care portfolio. This is a great opportunity to own Risk Adjustment, Quality / Care Gaps, and Transitions of Care, with the exact scope shaped by your strengths and where the business needs you most. These products take aggregated clinical and claims data and turn it into the signals VBC organizations act on: suspected conditions their coders can validate, care gaps their teams can close, transitions their care teams can intervene on, and evidence they can defend to a payer. We are looking for someone who understands the people on the other end of our products: the providers, coders, auditors, and care teams who have to act on what we send them. Each of them needs something different, and building for that is what separates a useful product from another source of output. We are also looking for deep strategic and analytical judgment. Much of the work is reading results, testing what they actually show, and deciding what that means for the roadmap. You should be able to take a care gap close rate or a suspecting precision score, understand how it was built and what it means for a customer's performance, and turn that into a clear, well-maintained set of priorities for the team. You will work closely with engineering, design, clinical informatics, our medical advisors, and customers, and you will own your roadmap end to end. As part of the team, you will Articulate a differentiated positioning for Zus for value-based care organizations, and ensure organization evolutionOwn the roadmap and backlog for your products within the VBC portfolio, with the discipline to keep them prioritized, written down, and defensible to engineering and to customers.Turn vague customer problems into testable questions and drive them to an answer.Interpret analytical results and convert them into next steps, risks, and decision points that someone else can act on without translation.Run customer conversations directly, from discovery through validation of what we shipped, across ACO enablement, Medicaid complex care, specialty, and virtual-first organizations.Define and track the success metrics that prove the product is delivering measurable financial and clinical value.Track the regulatory and methodology changes that move our roadmap, including CMS-HCC model updates, HEDIS and Stars measure specifications, and program rules across MSSP, ACO REACH, and MA." That's a big paragraph with responsibilities. Then: "You're a good fit because you have 3–5 years of product management experience, including exposure to data or analytics products where the output is an insight rather than a workflow.Demonstrated analytical judgment. You read a result and know what it does and does not say. You ask about the denominator before you repeat the number. You are comfortable pushing back on an analysis that does not hold up.A methodical approach to ambiguity. You frame the question before you frame the solution, and you write both down clearly enough that engineering, sales, and customers can all work from the same document.Experience working with healthcare data, specifically claims, clinical records, EHR and FHIR-based sources, and an understanding of how data quality and provenance affect what a product can honestly claim.Excellent written communication. Much of the value you create here is in the clarity of the decisions you record.An interest in how value-based care organizations succeed under their contracts, and a habit of starting from those terms rather than from what is easiest to measure. Strongly preferred Domain depth in risk and quality, usually built inside an ACO, MA plan, provider enablement company, or a risk or quality vendor.Risk adjustment mechanics: CMS-HCC models, prospective and retrospective programs, and suspecting-to-capture workflows through coder or CDI review." That's qualifications/requirements/skills. Then: "We will offer you… Competitive compensation that reflects the value you bring to the team a combination of cash and equityRobust benefits that include health insurance, wellness benefits, 401k with a match, unlimited PTOOpportunity to work alongside a passionate team that is determined to help change the world (and have fun doing it)" That's benefits and pay. Then there is a note about underrepresented backgrounds etc. That's boilerplate EEO? It's a note encouraging underrepresented backgrounds; might be considered EEO/equal-opportunity boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove that note. Also "Please Note: Research shows that candidates from underrepresented backgrounds often don’t apply unless they meet 100% of the job criteria..." That's EEO-ish; remove. Also "We do not conduct interviews by text nor will we send you a job offer unless you've interviewed with multiple people, including the Director of People & Talent, over video interviews." That's application instructions? Might be considered boilerplate; remove. Also "Job scams do exist so please be careful with your personal information." Remove. Thus we keep substantive content: company description, role description, responsibilities, qualifications/requirements/skills, benefits, pay. We need to decide sections. Potential sections: - About the role: could include company description + role overview. - Responsibilities: list of duties (the bullet list from "As part of the team, you will ..."). - Requirements: maybe the mandatory qualifications (3-5 years PM experience, analytical judgment, methodical approach, healthcare data experience, written communication, interest in VBC). Could be separate. - Qualifications: maybe preferred qualifications (domain depth in risk and quality, risk adjustment mechanics). Could be separate. - Skills: maybe specific skills like analytical judgment, etc. But we might combine. Given instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But they ask to use headings like Requirements, Qualifications, Skills. We could include only those that have real content. We have content for Requirements (mandatory) and Qualifications (preferred). Also Skills maybe overlapping. We could make:

About the role

with company description and role overview.

Responsibilities

with bullet list.

Requirements

with mandatory qualifications.

Qualifications

with preferred qualifications.

Benefits

with benefits.

Pay

with compensation. We might omit Skills if not distinct. Check if Pay section has specific content: "Competitive compensation that reflects the value you bring to the team a combination of cash and equity". That's specific enough. Benefits: "Robust benefits that include health insurance, wellness benefits, 401k with a match, unlimited PTO". Also "Opportunity to work alongside a passionate team that is determined to help change the world (and have fun doing it)" maybe part of benefits or culture; we can include. Now we need to format as HTML fragment: use

for headings,

• for lists,

  for prose. We must not repeat job title. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as in posting, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can rephrase? It says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the information, but we can rewrite in our own words as long as we don't lose detail. Safer to keep close to original phrasing. We need to convert bullet points into

  • . The responsibilities paragraph includes many items separated by periods. We need to extract each duty as a list item. Let's list responsibilities from the text: From "As part of the team, you will": - Articulate a differentiated positioning for Zus for value-based care organizations, and ensure organization evolution - Own the roadmap and backlog for your products within the VBC portfolio, with the discipline to keep them prioritized, written down, and defensible to engineering and to customers. - Turn vague customer problems into testable questions and drive them to an answer. - Interpret analytical results and convert them into next steps, risks, and decision points that someone else can act on without translation. - Run customer conversations directly, from discovery through validation of what we shipped, across ACO enablement, Medicaid complex care, specialty, and virtual-first organizations. - Define and track the success metrics that prove the product is delivering measurable financial and clinical value. - Track the regulatory and methodology changes that move our roadmap, including CMS-HCC model updates, HEDIS and Stars measure specifications, and program rules across MSSP, ACO REACH, and MA. Also earlier: "You will work closely with engineering, design, clinical informatics, our medical advisors, and customers, and you will own your roadmap end to end." That's also a responsibility. Also earlier: "You should be able to take a care gap close rate or a suspecting precision score, understand how it was built and what it means for a customer's performance, and turn that into a clear, well-maintained set of priorities for the team." That's also a responsibility. Also earlier: "Much of the work is reading results, testing what they actually show, and deciding what that means for the roadmap." That's also. We need to capture all substantive info. Might be many items; we can group similar. But we must not invent or summarize away detail. If we combine multiple sentences into one bullet, we might lose nuance. Better to keep each distinct sentence as separate bullet. Let's parse the "What we're looking for" paragraph for responsibilities. Paragraph: "We are seeking a Product Manager to own a portion of our value-based care portfolio. This is a great opportunity to own Risk Adjustment, Quality / Care Gaps, and Transitions of Care, with the exact scope shaped by your strengths and where the business needs you most. These products take aggregated clinical and claims data and turn it into the signals VBC organizations act on: suspected conditions their coders can validate, care gaps their teams can close, transitions their care teams can intervene on, and evidence they can defend to a payer. We are looking