Director, Product
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO etc. Remove duplicated lines, application instructions. Also remove cookie/navigation/legal etc. The posting includes some EEO at end; we should drop that.
We need to preserve all substantive information.
We need to decide what content goes where.
Let's parse:
- "Who You Are": description of candidate traits. Could be part of About the role? Might be "About You" later. But we have sections: About the role (maybe combine Who You Are and Who We Are?). However instructions: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- About the role: description of role, mission, maybe "Who You Are" and "Who We Are"? Actually "Who You Are" describes candidate traits, could be part of Requirements or Qualifications. "Who We Are" describes company, could be About the role? Usually About the role includes company description and role summary. We'll put company description and role summary under About the role.
- Responsibilities: Key Responsibilities list.
- Requirements / Qualifications: Qualifications list.
- Skills: maybe not separate; we could embed skills in Qualifications.
- Benefits: Investment In Our Team includes benefits description.
- Pay: Salary Range.
- Schedule: not present, so omit.
We also have "In The First 12 Months, You Will ...": could be part of Responsibilities or maybe a separate section like "First 12 Months" but not in allowed headings. Could be included under Responsibilities as additional duties. Or we could create a section "About the role" includes that. But instructions: only use allowed headings. So we should incorporate that content into Responsibilities or maybe under About the role as prose.
We also have "About You" earlier: candidate traits. That could go under Requirements or Qualifications as prose.
We must not invent sections like "About You". So we need to fold that content into Qualifications or Requirements.
Let's extract substantive content:
Who You Are (traits):
- builder excited to join fast-moving company focused on helping independent primary care providers succeed in value-based care.
- delivered real software and real data products.
- comfortable owning something end to end.
- happy in technical design conversation as in front of market team or executive.
- likes ambiguity, moves fast, prefers delivering usable and learning rather than six months on spec.
- ready to make meaningful impact.
Who We Are (company):
- Oasis Health Partners building healthier communities by advancing primary care.
- partner with patients, providers and plans to provide personalized, local care for seniors.
- belief patient needs come first, primary care foundation.
- patients receive better access and care.
- providers receive data, resources, expertise to be successful in value-based care.
- payors get benefit of solution improving performance, driving growth, reducing total cost of care in hard-to-engage markets.
- excited for you to join.
- invite to be part of Oasis, where we do the right thing, build things together and go all in - while having fun.
About You (candidate experience):
- built homegrown software, not just managed vendors.
- know what it takes to stand something up, keep it running, keep making it better: scoping, sequencing, release management, enhancement backlogs, performance, fixing what breaks.
- worked closely with engineering and data teams and can hold your own on architecture, data models, tradeoffs without being engineer.
- seeking Director of Product to own internal platform/software for prioritizing and routing work across internal teams.
- tool leverages internal data + AI to decide highest value work, gets it in front of right person at right time, learns from what happens next.
- hands-on role with real ownership.
- This is an illustrative and not an exhaustive list of responsibilities. As ideal candidate, looking for someone who will jump in where Oasis needs support!
Key Responsibilities (list):
- Own VBCOS end to end: prioritization and next best action logic, data model underneath it, experience end user sees.
- Define data model behind tool: objects exist, how they relate, where each field comes from, what has to be true about data for logic to hold.
- Work with data and analytics to identify and vet source systems that feed tool, make call on what we can use today vs what needs to be built or cleaned up first.
- Build and socialize prototypes. Get something clickable in front of market teams, clinical, leadership early, use it to force real decisions, iterate before engineering builds it.
- Work side by side with engineering and data to design what gets built, then stay involved through delivery, testing, release, post-launch performance.
- Act as quarterback across risk adjustment, quality, clinical, growth, market operations, patient engagement center, turning competing asks into sequenced plan people agree to.
- Translate messy operational problems into product requirements, and translate product decisions back into plain language for market leaders and executive team.
- Own feedback loop as real product surface, not byproduct of usage. What users accept, dismiss, ignore should make logic better over time.
- Decide where AI belongs in workflow and where it does not, own those features through evaluation, guardrails, measurement.
- Own adoption alongside market and clinical teams, including super user groups, training, change management.
- Provide executive-level updates, risk assessments, recommendations.
In The First 12 Months, You Will:
- Launch MVP of platform and get it in real use with first user group.
- Build roadmap for what comes next: enhancements to core product plus expansion into additional personas and channels, with clear sequence and rationale.
- Stand up performance tracking so we can tell whether platform is working, including adoption, action completion, downstream performance impact.
- Wire platform data back into models that generate priorities, so what happens in tool improves what tool recommends.
- Establish working rhythm around user feedback: how it gets collected, triaged, prioritized, closed out with people who raised it.
Investment In Our Team (benefits):
- We take care of our people and offer robust benefits including medical, dental, vision and generous time off plans.
- Committed to supporting your growth with a development program that starts with onboarding and continues throughout your career.
- As inclusive, passionate and diverse team, you will partner with professionals who understand importance of high-value, high-impact patient care.
- Invite to be part of Oasis Health, where you’ll discover we listen first, build things together, always do the right thing, have fun and most importantly, are all in!
Qualifications:
- 8+ years in product management, with experience across both software products and data or analytics products.
- Track record of building and maintaining internally developed software, including release process, enhancement cycles, performance monitoring, and technical debt tradeoffs.
- Experience with Medicare Advantage and value-based care is strongly preferred, particularly risk adjustment, quality, or care management workflows.
- Comfortable working directly in data. Hands-on experience with a modern data stack such as Snowflake, dbt, and a BI layer like Sigma, Looker, or Tableau.
- Experience prototyping with tools like Claude Design, Figma, Replit, Lovable.
- Experience with AI or LLM-enabled features in a production product, including prompt and retrieval design, evaluation and testing approaches, human in the loop patterns, etc.
- Fluent with modern product and engineering tooling: Jira or Linear, Figma, Git, API and integration work, and agile or iterative delivery.
- Experience with healthcare data and systems such as claims, EMR integrations, CRM/patient engagement platforms.
- Strong problem solver who is resourceful with incomplete information and does not wait to be handed a plan.
- Excellent written and verbal communication, with ability to adapt to audience from individual contributor to senior leadership, and to distill complex information into clear, compelling messages.
- Ability to thrive in a fast-paced startup environment, including comfort with shifting priorities and doing work that is below your title when it needs doing.
- Experience leading through influence across functions.
Salary Range: $160,000 USD - $190,000 USD
- The salary range listed reflects the full compensation range for this role level at Oasis and is designed to support growth over time. Actual offers may vary based on a candidate’s skills, experience, and alignment with the scope of the role. Offers near the top of the range are uncommon and generally reflect exceptionally deep, directly relevant experience.
- At this time, we are unable to sponsor employment visas. Candidates must be authorized to work in the United States without a current or future visa sponsorship.
- This role is open to applicants currently residing in the United States.
- All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, gender identity, sexual orientation, national origin, protected veteran status, or disability status. (EEO boilerplate - should be removed.)
We need to remove EEO/equal-opportunity boilerplate. So drop that last paragraph.
Also remove visa sponsorship line? It's not EEO but it's about visa sponsorship; it's substantive? It's a requirement: "Unable to sponsor employment visas. Candidates must be authorized to work in the United States without a current or future visa sponsorship." That's substantive info about eligibility. Should we keep? It's not boilerplate; it's a requirement. Likely keep. Similarly "This role is open to applicants currently residing in the United States." Keep.
We need to format sections.
We'll produce:
About the role
... combine Who We Are and maybe a brief role summary? We'll include company description and role summary from About You? Actually About You includes role description. We'll put role summary there.
Better: About the role includes company description and what the role entails (maybe high-level). Then Responsibilities list detailed duties. Qualifications list requirements. Benefits section. Pay section.
Let's craft.
About the role paragraph: combine Who We Are and a brief description of the role: Director of Product owning internal platform/software for prioritizing and routing work across internal teams, leveraging internal data + AI.
We'll write:
Oasis Health Partners (Oasis) is building healthier communities by advancing primary care. We partner with patients, providers and plans to provide personalized, local care for seniors. We believe that patient needs come first, and that primary care is the foundation of patient‑centric healthcare. With Oasis, patients receive better access and care. Providers receive the data, resources, and expertise to be successful in value‑based care arrangements. Payors get the benefit of a solution that improves performance, drives growth, and reduces the total cost of care in hard‑to‑engage markets.
As a Director of Product you will own our internal platform/software for prioritizing and routing work across our internal teams. This tool leverages internal data + AI to decide what the highest value work is, gets it in front of the right person at the right time, and learns from what happens next. This is a hands‑on role with real ownership.
That covers Who We Are and About You role description.
Responsibilities: list from Key Responsibilities plus In The First 12 Months items (they are also responsibilities). We'll combine into one .
We need to ensure we don't duplicate. We'll list all items.
Let's enumerate:
- Own VBCOS end to end: the prioritization and next best action logic, the data model underneath it, and the experience the end user sees
- Define the data model behind the tool: what objects exist, how they relate, where each field comes from, and what
for prose. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO etc. Remove duplicated lines, application instructions. Also remove cookie/navigation/legal etc. The posting includes some EEO at end; we should drop that. We need to preserve all substantive information. We need to decide what content goes where. Let's parse: - "Who You Are": description of candidate traits. Could be part of About the role? Might be "About You" later. But we have sections: About the role (maybe combine Who You Are and Who We Are?). However instructions: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - About the role: description of role, mission, maybe "Who You Are" and "Who We Are"? Actually "Who You Are" describes candidate traits, could be part of Requirements or Qualifications. "Who We Are" describes company, could be About the role? Usually About the role includes company description and role summary. We'll put company description and role summary under About the role. - Responsibilities: Key Responsibilities list. - Requirements / Qualifications: Qualifications list. - Skills: maybe not separate; we could embed skills in Qualifications. - Benefits: Investment In Our Team includes benefits description. - Pay: Salary Range. - Schedule: not present, so omit. We also have "In The First 12 Months, You Will ...": could be part of Responsibilities or maybe a separate section like "First 12 Months" but not in allowed headings. Could be included under Responsibilities as additional duties. Or we could create a section "About the role" includes that. But instructions: only use allowed headings. So we should incorporate that content into Responsibilities or maybe under About the role as prose. We also have "About You" earlier: candidate traits. That could go under Requirements or Qualifications as prose. We must not invent sections like "About You". So we need to fold that content into Qualifications or Requirements. Let's extract substantive content: Who You Are (traits): - builder excited to join fast-moving company focused on helping independent primary care providers succeed in value-based care. - delivered real software and real data products. - comfortable owning something end to end. - happy in technical design conversation as in front of market team or executive. - likes ambiguity, moves fast, prefers delivering usable and learning rather than six months on spec. - ready to make meaningful impact. Who We Are (company): - Oasis Health Partners building healthier communities by advancing primary care. - partner with patients, providers and plans to provide personalized, local care for seniors. - belief patient needs come first, primary care foundation. - patients receive better access and care. - providers receive data, resources, expertise to be successful in value-based care. - payors get benefit of solution improving performance, driving growth, reducing total cost of care in hard-to-engage markets. - excited for you to join. - invite to be part of Oasis, where we do the right thing, build things together and go all in - while having fun. About You (candidate experience): - built homegrown software, not just managed vendors. - know what it takes to stand something up, keep it running, keep making it better: scoping, sequencing, release management, enhancement backlogs, performance, fixing what breaks. - worked closely with engineering and data teams and can hold your own on architecture, data models, tradeoffs without being engineer. - seeking Director of Product to own internal platform/software for prioritizing and routing work across internal teams. - tool leverages internal data + AI to decide highest value work, gets it in front of right person at right time, learns from what happens next. - hands-on role with real ownership. - This is an illustrative and not an exhaustive list of responsibilities. As ideal candidate, looking for someone who will jump in where Oasis needs support! Key Responsibilities (list): - Own VBCOS end to end: prioritization and next best action logic, data model underneath it, experience end user sees. - Define data model behind tool: objects exist, how they relate, where each field comes from, what has to be true about data for logic to hold. - Work with data and analytics to identify and vet source systems that feed tool, make call on what we can use today vs what needs to be built or cleaned up first. - Build and socialize prototypes. Get something clickable in front of market teams, clinical, leadership early, use it to force real decisions, iterate before engineering builds it. - Work side by side with engineering and data to design what gets built, then stay involved through delivery, testing, release, post-launch performance. - Act as quarterback across risk adjustment, quality, clinical, growth, market operations, patient engagement center, turning competing asks into sequenced plan people agree to. - Translate messy operational problems into product requirements, and translate product decisions back into plain language for market leaders and executive team. - Own feedback loop as real product surface, not byproduct of usage. What users accept, dismiss, ignore should make logic better over time. - Decide where AI belongs in workflow and where it does not, own those features through evaluation, guardrails, measurement. - Own adoption alongside market and clinical teams, including super user groups, training, change management. - Provide executive-level updates, risk assessments, recommendations. In The First 12 Months, You Will: - Launch MVP of platform and get it in real use with first user group. - Build roadmap for what comes next: enhancements to core product plus expansion into additional personas and channels, with clear sequence and rationale. - Stand up performance tracking so we can tell whether platform is working, including adoption, action completion, downstream performance impact. - Wire platform data back into models that generate priorities, so what happens in tool improves what tool recommends. - Establish working rhythm around user feedback: how it gets collected, triaged, prioritized, closed out with people who raised it. Investment In Our Team (benefits): - We take care of our people and offer robust benefits including medical, dental, vision and generous time off plans. - Committed to supporting your growth with a development program that starts with onboarding and continues throughout your career. - As inclusive, passionate and diverse team, you will partner with professionals who understand importance of high-value, high-impact patient care. - Invite to be part of Oasis Health, where you’ll discover we listen first, build things together, always do the right thing, have fun and most importantly, are all in! Qualifications: - 8+ years in product management, with experience across both software products and data or analytics products. - Track record of building and maintaining internally developed software, including release process, enhancement cycles, performance monitoring, and technical debt tradeoffs. - Experience with Medicare Advantage and value-based care is strongly preferred, particularly risk adjustment, quality, or care management workflows. - Comfortable working directly in data. Hands-on experience with a modern data stack such as Snowflake, dbt, and a BI layer like Sigma, Looker, or Tableau. - Experience prototyping with tools like Claude Design, Figma, Replit, Lovable. - Experience with AI or LLM-enabled features in a production product, including prompt and retrieval design, evaluation and testing approaches, human in the loop patterns, etc. - Fluent with modern product and engineering tooling: Jira or Linear, Figma, Git, API and integration work, and agile or iterative delivery. - Experience with healthcare data and systems such as claims, EMR integrations, CRM/patient engagement platforms. - Strong problem solver who is resourceful with incomplete information and does not wait to be handed a plan. - Excellent written and verbal communication, with ability to adapt to audience from individual contributor to senior leadership, and to distill complex information into clear, compelling messages. - Ability to thrive in a fast-paced startup environment, including comfort with shifting priorities and doing work that is below your title when it needs doing. - Experience leading through influence across functions. Salary Range: $160,000 USD - $190,000 USD - The salary range listed reflects the full compensation range for this role level at Oasis and is designed to support growth over time. Actual offers may vary based on a candidate’s skills, experience, and alignment with the scope of the role. Offers near the top of the range are uncommon and generally reflect exceptionally deep, directly relevant experience. - At this time, we are unable to sponsor employment visas. Candidates must be authorized to work in the United States without a current or future visa sponsorship. - This role is open to applicants currently residing in the United States. - All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, gender identity, sexual orientation, national origin, protected veteran status, or disability status. (EEO boilerplate - should be removed.) We need to remove EEO/equal-opportunity boilerplate. So drop that last paragraph. Also remove visa sponsorship line? It's not EEO but it's about visa sponsorship; it's substantive? It's a requirement: "Unable to sponsor employment visas. Candidates must be authorized to work in the United States without a current or future visa sponsorship." That's substantive info about eligibility. Should we keep? It's not boilerplate; it's a requirement. Likely keep. Similarly "This role is open to applicants currently residing in the United States." Keep. We need to format sections. We'll produce:
About the role
... combine Who We Are and maybe a brief role summary? We'll include company description and role summary from About You? Actually About You includes role description. We'll put role summary there. Better: About the role includes company description and what the role entails (maybe high-level). Then Responsibilities list detailed duties. Qualifications list requirements. Benefits section. Pay section. Let's craft. About the role paragraph: combine Who We Are and a brief description of the role: Director of Product owning internal platform/software for prioritizing and routing work across internal teams, leveraging internal data + AI. We'll write:
Oasis Health Partners (Oasis) is building healthier communities by advancing primary care. We partner with patients, providers and plans to provide personalized, local care for seniors. We believe that patient needs come first, and that primary care is the foundation of patient‑centric healthcare. With Oasis, patients receive better access and care. Providers receive the data, resources, and expertise to be successful in value‑based care arrangements. Payors get the benefit of a solution that improves performance, drives growth, and reduces the total cost of care in hard‑to‑engage markets.
As a Director of Product you will own our internal platform/software for prioritizing and routing work across our internal teams. This tool leverages internal data + AI to decide what the highest value work is, gets it in front of the right person at the right time, and learns from what happens next. This is a hands‑on role with real ownership.
That covers Who We Are and About You role description. Responsibilities: list from Key Responsibilities plus In The First 12 Months items (they are also responsibilities). We'll combine into one- .
We need to ensure we don't duplicate. We'll list all items.
Let's enumerate:
- Own VBCOS end to end: the prioritization and next best action logic, the data model underneath it, and the experience the end user sees
- Define the data model behind the tool: what objects exist, how they relate, where each field comes from, and what