Product Owner
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. The posting includes: About Inspire Medical Systems (company description) maybe not exactly "About the role". Could treat as "About the company" but not in list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if appropriate. We have content for: Responsibilities (Main Duties/Responsibilities), Qualifications, Benefits, Pay (Salary). Also maybe "About the role" could be Position Summary. We could use "About the role" heading for Position Summary. Also "Skills" maybe not explicit separate; qualifications include skills. Could combine.
We must not create sections with filler like "commensurate with experience". Salary is given as range $90,000—$120,000 USD, so we can include Pay section.
Benefits: there is a Benefits And Other Compensation section with list.
We must not include boilerplate like EEO, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
About the role
Position Summary ...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Salary $90,000—$120,000 USD
We need to ensure we preserve all substantive info from each section. Let's extract details. About Inspire Medical Systems: description about company, mission, etc. Also "WHY JOIN OUR FAST-GROWING TEAM": benefits description (but we already have benefits). Could combine into About the role? Actually "About Inspire Medical Systems" is company overview; "WHY JOIN OUR FAST-GROWING TEAM" is culture/benefits. But we have separate Benefits section; we could put company overview under About the role? Might be okay. Position Summary: The Service Desk Product Owner is responsible for the vision, strategy, roadmap, and continual improvement of Service Desk services, processes, and enabling technologies. This role translates business and user needs into prioritized product outcomes that improve employee experience, service quality, operational efficiency, and measurable business value. The Product Owner serves as the primary liaison among Service Desk operations, Digital and Information Technology teams, business stakeholders, and delivery partners. The role owns the Service Desk ticket backlog and partners with platform administrators, engineers, process owners, vendors, and support leaders to deliver capabilities across ServiceNow ITSM, knowledge management, self-service, automation, virtual agents, reporting, and the broader digital employee support experience. This position does not have primary responsibility for day-to-day people management or shift scheduling. Instead, it provides cross-functional product leadership, establishes priorities and ensures delivered solutions align with organizational, security, regulatory, and service management requirements. Main Duties/Responsibilities: list bullet points under headings: Vision, Strategy, and Roadmap; Backlog and Delivery Management; ServiceNow And ITSM Responsibilities; Stakeholder And Customer Experience Management; Metrics and Continual Improvement. We need to preserve each bullet. Let's extract each bullet: Vision, Strategy, and Roadmap: - Define and communicate the Service Desk operations vision, strategy, goals, and multi-year roadmap in alignment with organizational priorities. - Identify opportunities to improve the end-user support experience through process redesign, self-service, automation, knowledge, analytics, and emerging technologies. - Develop outcome-based objectives, success measures, and value realization plans. - Prepare business cases and recommendations for investments, enhancements, and lifecycle decisions. Backlog and Delivery Management: - Own, maintain, and prioritize the Service Desk ticket backlog based on business value, risk, user impact, operational need, compliance requirements, and technical dependencies. - Balance new capabilities, technical debt, defects, platform maintenance, and continual improvement work. ServiceNow And ITSM Responsibilities: - Provide direction for Service Desk capabilities within ServiceNow ITSM and related employee support technologies. - Partner with ITSM process owners to improve Incident, Request, Knowledge, Problem, and Major Incident Management capabilities. - Ensure solutions align with ITIL-based service management practices and organizational technology standards. Stakeholder And Customer Experience Management: - Build strong relationships with Service Desk leader, support teams, infrastructure, security, applications, Human Resources, business functions, and end users. - Facilitate discovery sessions, roadmap reviews, backlog refinement, prioritization discussions, and product demonstrations. - Collect and analyze user feedback, customer satisfaction data, service trends, and operational pain points. - Champion intuitive, accessible, and consistent support experiences across channels. - Communicate priorities, decisions, dependencies, risks, and outcomes to stakeholders and leadership. Metrics and Continual Improvement: - Define and monitor product and service outcomes, including adoption, customer satisfaction, self-service effectiveness, automation value, service performance, and operational efficiency. - Use ticket trends, demand data, voice-of-customer feedback, and performance reporting to identify and prioritize improvements. - Develop and maintain dashboards and executive-level reporting that demonstrate platform and service health. Qualifications: - Bachelor’s degree in information technology, Computer Science, Business, or a related discipline, or equivalent practical experience. - 5+ years of progressive experience in IT service management, Service Desk operations, enterprise platform delivery, product ownership, or a related field. - Strong understanding of ITIL and IT Service Management principles. - Experience with ServiceNow ITSM or a comparable enterprise service management platform. - Experience leading cross-functional initiatives and influencing decisions without direct authority. - Strong analytical, facilitation, organizational, and problem-solving skills. - Excellent written, verbal, presentation, and interpersonal communication skills. - Proven ability to manage competing priorities in a fast-paced environment. Benefits And Other Compensation: list: - Multiple health insurance plan options. - Employer contributions to Health Savings Account. - Dental, Vision, Life and Disability benefits. - 401k plan + employer match. - Identity Protection. - Flexible time off. - Tuition Reimbursement. - Employee Assistance program. - All employees have the opportunity to participate in the ownership and success of Inspire. Employees at all levels can participate through equity awards and the Employee Stock Purchase Program. We should not include EEO etc. Pay: Salary $90,000—$120,000 USD. We also have "The salary for this position will be offered at a level consistent with the experience and qualifications of the candidate. This information reflects the anticipated salary range for this position at the time of posting. The salary range may be modified in the future and actual compensation may vary from the posting based on various factors such as geographic location, work experience, education and/or skill level." This is somewhat filler but still substantive? It's generic. Might be considered boilerplate? It's not specific like "commensurate with experience". It's a description of salary determination. Might be okay to include but could be considered filler. The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". This is not exactly those but still generic. Might be okay to include but we could keep just the range. The instruction says "Prefer a few substantive sections over many thin ones." So we can include Pay section with just the range. We also need to include About Inspire Medical Systems and WHY JOIN OUR FAST-GROWING TEAM maybe as part of About the role? Could create an "About the company" section but not in allowed headings. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we can use those. Probably we should stick to those headings. So we can put company overview under About the role? Might be odd but acceptable. Alternatively we could omit company overview if not needed? But we must preserve ALL substantive information. So we need to include it somewhere. Could put it under About the role heading, describing the role and company? Might be okay. Better: Use About the role heading for Position Summary (which includes role description). Then we could add a separate
for company overview before that? But that would be outside a heading; maybe allowed as prose. The instruction: Use
for section headings, - for any list,
for prose. So we can have prose outside headings. So we can have a
for company overview, then
About the role
for Position Summary, then other sections.
Thus we preserve all.
Let's craft:
About Inspire Medical Systems Inspire is the first of its kind medical device designed to make a difference in the lives of those living with Obstructive Sleep Apnea (OSA). We are revolutionizing the sleep industry with our FDA-approved medical device, designed to reduce OSA severity for those who cannot tolerate or get consistent benefit from CPAP. Inspire Medical Systems is committed to enhancing patients’ lives through sleep innovation. We are steadfast in our commitment to prioritize patient outcomes, act with integrity and lead with respect. With positive persistence at our core, we are committed to all those we serve. WHY JOIN OUR FAST-GROWING TEAM At Inspire, we value people – your diverse experiences, backgrounds, and thoughts. We elevate voices and encourage learning opportunities to build a professional network that grows into community. We embrace a people-first culture by offering excellent benefits, 401k matching, ESPP, flexible time off (FTO), and tuition reimbursement. If you’re passionate about making a difference in people’s lives and want to work with innovative technology, come be a part of our great team!
Then About the role
Position Summary ...
Then responsibilities, qualifications, benefits, pay.
Make sure to not duplicate content: The WHY JOIN section includes benefits description; we already have Benefits section; we might be duplicating. But we need to preserve all substantive information; if we include both, we might duplicate benefits text. Could we incorporate the WHY JOIN text into Benefits section? The WHY JOIN includes culture and benefits; we could keep it as prose under About the role? But then Benefits section would duplicate. To avoid duplication, maybe we omit the WHY JOIN prose and keep only Benefits section list. However the WHY JOIN also includes cultural statements about valuing people, elevating voices, etc. That's substantive and not in Benefits list. We could incorporate that into About the role prose (or a separate before Benefits). Let's do: keep a
for company overview and WHY JOIN cultural statements (excluding the benefits list). Then Benefits section will list the specific benefits.
Thus extract from WHY JOIN: "At Inspire, we value people – your diverse experiences, backgrounds, and thoughts. We elevate voices and encourage learning opportunities to build a professional network that grows into community. We embrace a people-first culture by offering excellent benefits, 401k matching, ESPP, flexible time off (FTO), and tuition reimbursement. If you’re passionate about making a difference in people’s lives and want to work with innovative technology
for prose. So we can have prose outside headings. So we can have a
for company overview, then
About the role
for Position Summary, then other sections. Thus we preserve all. Let's craft:About Inspire Medical Systems Inspire is the first of its kind medical device designed to make a difference in the lives of those living with Obstructive Sleep Apnea (OSA). We are revolutionizing the sleep industry with our FDA-approved medical device, designed to reduce OSA severity for those who cannot tolerate or get consistent benefit from CPAP. Inspire Medical Systems is committed to enhancing patients’ lives through sleep innovation. We are steadfast in our commitment to prioritize patient outcomes, act with integrity and lead with respect. With positive persistence at our core, we are committed to all those we serve. WHY JOIN OUR FAST-GROWING TEAM At Inspire, we value people – your diverse experiences, backgrounds, and thoughts. We elevate voices and encourage learning opportunities to build a professional network that grows into community. We embrace a people-first culture by offering excellent benefits, 401k matching, ESPP, flexible time off (FTO), and tuition reimbursement. If you’re passionate about making a difference in people’s lives and want to work with innovative technology, come be a part of our great team!
ThenAbout the role
Position Summary ...
Then responsibilities, qualifications, benefits, pay. Make sure to not duplicate content: The WHY JOIN section includes benefits description; we already have Benefits section; we might be duplicating. But we need to preserve all substantive information; if we include both, we might duplicate benefits text. Could we incorporate the WHY JOIN text into Benefits section? The WHY JOIN includes culture and benefits; we could keep it as prose under About the role? But then Benefits section would duplicate. To avoid duplication, maybe we omit the WHY JOIN prose and keep only Benefits section list. However the WHY JOIN also includes cultural statements about valuing people, elevating voices, etc. That's substantive and not in Benefits list. We could incorporate that into About the role prose (or a separatebefore Benefits). Let's do: keep a
for company overview and WHY JOIN cultural statements (excluding the benefits list). Then Benefits section will list the specific benefits. Thus extract from WHY JOIN: "At Inspire, we value people – your diverse experiences, backgrounds, and thoughts. We elevate voices and encourage learning opportunities to build a professional network that grows into community. We embrace a people-first culture by offering excellent benefits, 401k matching, ESPP, flexible time off (FTO), and tuition reimbursement. If you’re passionate about making a difference in people’s lives and want to work with innovative technology