Product Manager
Staritas · United States · 4 wk ago
RemoteRemoteMarketing$175k–$185k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the Role: paragraph after "About the Role". It includes bullet-like sentences: "Define and execute the product roadmap for analytics and decision-support solutions. Partner with customers to understand challenges, gather feedback, and identify opportunities for innovation. Collaborate with Engineering, Analytics, and Data Science teams to deliver data-driven and AI-powered capabilities. Lead customer discovery, Voice of Customer programs, and usability testing. Develop dashboards, alerts, benchmarks, recommendations, and workflow solutions that drive action and measurable value. Manage product backlogs, requirements, and Agile delivery processes. Support product launches, customer presentations, and go-to-market initiatives."
That's responsibilities. Could be under "Responsibilities". The "About the Role" heading is allowed as a section heading. The content can be placed under
About the Role
then... maybe we could split into
- for list of duties. The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can treat the bullet sentences as list items. Thus under About the Role we can have
- each sentence.
- Required Qualifications: list of qualifications. Could be under Requirements or Qualifications. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have separate sections: Requirements (maybe required qualifications) and Qualifications (preferred). Or we could combine. But we need to include sections only when posting has real specific content. It does have Required Qualifications and Preferred Qualifications. So we can have Requirements (for required) and Qualifications (for preferred). Or we could have Requirements for required, Qualifications for preferred. Let's do that.
- Technical Skills: list of tools. Could be under Skills.
- What We Offer: includes Competitive salary..., Fully remote..., Comprehensive benefits..., 19 days PTO..., 10 holidays..., Opportunity..., Travel..., Work Environment..., Benefits Statement etc. We need to extract Benefits, Pay, Schedule. Pay: they gave base compensation range $175,000 - $185,000 annually, plus benefits. Also mention compensation offered will depend on factors. So we have Pay section with that info.
Schedule: They mention "Fully remote work environment" and "Travel Up to 10% travel, based on business needs. While our roles are 100% remote, we do get together a few times a year for up to one week." Also maybe schedule not explicit but we can infer remote and travel. However schedule section should only be included if posting actually states them. They mention remote work environment and travel expectations. That's about work arrangement, not schedule like hours. Could be considered Schedule? Might be better to put under Benefits? But we have a Benefits section for benefits package. The "What We Offer" includes many items: Competitive salary and performance bonus program (Pay), Fully remote work environment (maybe Schedule?), Comprehensive benefits package including 401k match (Benefits), 19 days of PTO per year; 10 holidays per year (Benefits), Opportunity to work in a mission-driven organization (maybe not needed), Travel Up to 10% travel... (Schedule?), Work Environment (maybe not needed). The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide if we have enough specific content for Benefits, Pay, Schedule.
Benefits: they list comprehensive benefits package including 401k match, 19 days PTO, 10 holidays, medical/dental/vision, retirement savings plans with company contributions, paid parental/family leave, employee assistance, wellness resources, life and disability insurance, professional development, flexible work arrangements. That's specific. So Benefits section yes.
Pay: they give base compensation range $175k-$185k annually, plus performance bonus program. That's specific. So Pay section yes.
Schedule: they mention Fully remote work environment, Travel up to 10% travel, a few times a year for up to one week. That's about work arrangement and travel, not exactly schedule like hours. Could be considered Schedule? Might be okay to include Schedule section with remote and travel details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state remote work environment and travel expectations. So we can include Schedule.
We also have Work Environment details (stationary position, ability to operate equipment). That could be part of Schedule or maybe separate but we don't have a heading for Work Environment. Could fold into Schedule or maybe under Benefits? Probably Schedule.
Now we need to remove boilerplate: Equal Opportunity / Affirmative Action Statement, Accommodation Statement, Pay Transparency Statement, Benefits Statement (some of that is duplicated with Benefits we already captured). Also "Learn more about us by visiting www.staritas.com." That's boilerplate? It's not navigation but maybe okay to keep? It's not substantive about the role; it's a call to action. Probably consider it as application instruction? It's not exactly instruction to apply but it's a link. Might be considered boilerplate; safer to remove.
Also "While our roles are 100% remote, we do get together a few times a year for up to one week. Employees are given ample notice and attendance is expected." That's schedule info.
Now we need to format.
We'll produce:
About the Role
- Define and execute the product roadmap for analytics and decision-support solutions.
- Partner with customers to understand challenges, gather feedback, and identify opportunities for innovation.
- Collaborate with Engineering, Analytics, and Data Science teams to deliver data-driven and AI-powered capabilities.
- Lead customer discovery, Voice of Customer programs, and usability testing.
- Develop dashboards, alerts, benchmarks, recommendations, and workflow solutions that drive action and measurable value.
- Manage product backlogs, requirements, and Agile delivery processes.
- Support product launches, customer presentations, and go-to-market initiatives.
Responsibilities
maybe we could skip because About the Role already covers responsibilities. But we need to avoid duplicate sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine About the Role and Responsibilities into one section? But we already used About the Role heading; we could treat that as the responsibilities section. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role as a section. We don't need a separate Responsibilities heading if About the role already covers it. However we might still include Responsibilities if there is distinct content. But we already used all responsibilities in About the Role. So we can omit Responsibilities heading to avoid thin duplicate. Now Requirements (required qualifications):
Requirements
- Bachelor's degree in a related field or equivalent experience.
- 5-7 years of healthcare product management experience.
- Experience with analytics, business intelligence, decision support, or data-driven product development.
- Strong ability to translate complex data into actionable insights.
- Experience conducting customer research and Voice of Customer programs.
- Experience delivering AI-enabled product capabilities.
- Experience working in Agile/Scrum environments.
- Excellent communication, stakeholder management, and problem-solving skills.
Qualifications
- Experience in healthcare supply chain, value analysis, capital planning, sourcing, risk management, or healthcare analytics.
- Familiarity with healthcare systems such as ERP, EHR, MMIS, CMMS, procurement, or supply chain platforms.
- Experience improving healthcare workflows and decision-support processes.
- International or localization product experience.
Skills
- Microsoft Office 365 (Word, Excel, PowerPoint)
- Jira, Confluence, Aha!, Qualtrics, Dovetail, Power BI, or similar product and analytics tools
Benefits
- Comprehensive benefits package including 401k match
- 19 days of paid time off (PTO) per year
- 10 company holidays per year
- Medical, dental, and vision coverage
- Retirement savings plans with company contributions
- Paid parental and family leave
- Access to employee assistance and wellness resources
- Life and disability insurance
- Professional development opportunities
- Flexible work arrangements
Pay
Base compensation range: $175,000 - $185,000 annually, plus performance bonus program.
Schedule: We need to capture remote work environment and travel expectations. Schedule content: "Fully remote work environment", "Travel up to 10% travel, based on business needs. While our roles are 100% remote, we do get together a few times a year for up to one week. Employees are given ample notice and attendance is expected." We could also mention "Work Environment: This position operates primarily in a remote work environment and requires the ability to remain in a stationary position for extended periods while performing work at a desk or workstation. The employee must be able to operate standard office equipment, including a computer, keyboard, mouse, webcam, and telephone. The role also requires the ability to occasionally move throughout a workspace to access files, office equipment, and work-related materials. Effective communication, both written and verbal, is essential for interacting with employees, clients, and stakeholders." That's more about work environment, but could be part of Schedule. However schedule section is about schedule, not physical requirements. Might be better to include under Schedule? The instruction says include a section ONLY when posting has real specific content for it. It does have remote work environment and travel expectations, which is schedule-related. The physical requirements maybe not schedule but could be considered work environment; but we don't have a heading for Work Environment. Could we add a section for Work Environment? Not in the allowed list; but we could fold into Schedule or Benefits? Probably Schedule is okay to include remote and travel, and we could also include the physical requirements as part of Schedule? Might be stretching. Alternatively we could create a Schedule section with remote and travel, and leave out the physical requirements (they are not schedule). But we must preserve ALL substantive information; we cannot omit details. So we need to include that info somewhere. If we don't have a Work Environment heading,
- each sentence.
- Required Qualifications: list of qualifications. Could be under Requirements or Qualifications. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have separate sections: Requirements (maybe required qualifications) and Qualifications (preferred). Or we could combine. But we need to include sections only when posting has real specific content. It does have Required Qualifications and Preferred Qualifications. So we can have Requirements (for required) and Qualifications (for preferred). Or we could have Requirements for required, Qualifications for preferred. Let's do that.
- Technical Skills: list of tools. Could be under Skills.
- What We Offer: includes Competitive salary..., Fully remote..., Comprehensive benefits..., 19 days PTO..., 10 holidays..., Opportunity..., Travel..., Work Environment..., Benefits Statement etc. We need to extract Benefits, Pay, Schedule. Pay: they gave base compensation range $175,000 - $185,000 annually, plus benefits. Also mention compensation offered will depend on factors. So we have Pay section with that info.
Schedule: They mention "Fully remote work environment" and "Travel Up to 10% travel, based on business needs. While our roles are 100% remote, we do get together a few times a year for up to one week." Also maybe schedule not explicit but we can infer remote and travel. However schedule section should only be included if posting actually states them. They mention remote work environment and travel expectations. That's about work arrangement, not schedule like hours. Could be considered Schedule? Might be better to put under Benefits? But we have a Benefits section for benefits package. The "What We Offer" includes many items: Competitive salary and performance bonus program (Pay), Fully remote work environment (maybe Schedule?), Comprehensive benefits package including 401k match (Benefits), 19 days of PTO per year; 10 holidays per year (Benefits), Opportunity to work in a mission-driven organization (maybe not needed), Travel Up to 10% travel... (Schedule?), Work Environment (maybe not needed). The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide if we have enough specific content for Benefits, Pay, Schedule.
Benefits: they list comprehensive benefits package including 401k match, 19 days PTO, 10 holidays, medical/dental/vision, retirement savings plans with company contributions, paid parental/family leave, employee assistance, wellness resources, life and disability insurance, professional development, flexible work arrangements. That's specific. So Benefits section yes.
Pay: they give base compensation range $175k-$185k annually, plus performance bonus program. That's specific. So Pay section yes.
Schedule: they mention Fully remote work environment, Travel up to 10% travel, a few times a year for up to one week. That's about work arrangement and travel, not exactly schedule like hours. Could be considered Schedule? Might be okay to include Schedule section with remote and travel details. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state remote work environment and travel expectations. So we can include Schedule.
We also have Work Environment details (stationary position, ability to operate equipment). That could be part of Schedule or maybe separate but we don't have a heading for Work Environment. Could fold into Schedule or maybe under Benefits? Probably Schedule.
Now we need to remove boilerplate: Equal Opportunity / Affirmative Action Statement, Accommodation Statement, Pay Transparency Statement, Benefits Statement (some of that is duplicated with Benefits we already captured). Also "Learn more about us by visiting www.staritas.com." That's boilerplate? It's not navigation but maybe okay to keep? It's not substantive about the role; it's a call to action. Probably consider it as application instruction? It's not exactly instruction to apply but it's a link. Might be considered boilerplate; safer to remove.
Also "While our roles are 100% remote, we do get together a few times a year for up to one week. Employees are given ample notice and attendance is expected." That's schedule info.
Now we need to format.
We'll produce:
- for any list of duties/requirements/benefits, and