Senior Product Owner I

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 boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph: "This role sits in the Product Management team within Sage Technology, the department responsible for building and maintaining the systems that run our business. You will report into Product Management and work alongside other product owners, product managers, engineers, and architects across the technology estate. Your product is Microsoft Dynamics CRM, and your internal customers are our college textbook sales and journal advertising sales divisions. Dynamics is where their pipeline is managed, customer relationships are tracked, and revenue decisions get made. You own the backlog for that platform and you are accountable for making it genuinely better for the people who depend on it every day. This is a role for a technologist with real commercial awareness. You will spend your time between two worlds: out in the business understanding what is slowing sales teams down, and back with your delivery team turning that into work that ships. Because Dynamics sits at the center of several business processes, you will also manage dependencies with other product teams inside Sage Technology." That's about the role. Could be "About the role" section. - Then "What You Will Do" list: bullet points. - Then "What You Will Bring": bullet points (requirements/qualifications). Then "Preferred Requirements": bullet points. - Then "Helpful context, not a requirement." etc. - Then "Pay Transparency & Benefits Package": includes compensation description, benefits details. - Then "In addition to compensation, Sage offers a highly competitive and comprehensive PPO medical, dental, and vision care benefits package with SAGE covering most of the premium costs. Unique program benefits that support a healthy life, a company-sponsored anniversary trip every 5 years, a 401(k)-matching program of 100% up to 5% of pay, and other significant meaningful benefits. In alignment with our value for education, Sage offers financial support for bachelor's and graduate-level degree programs as well as learning for personal interest. Sage offers freedom and autonomy in your day-to-day with hybrid or remote work, depending on the role." - Then "Join the nearly 2,000 Sage employees worldwide..." etc. That's more fluff but still substantive? Might be considered boilerplate? It's about company mission. Might be okay to include in About the role? But we can keep as part of About the role or maybe a separate "About Sage" but not required. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The mission statement is somewhat generic but still content. However we might consider it as part of About the role or maybe not needed. Safer to keep it within About the role. - Then "Diversity, Equity, and Inclusion" etc. That's boilerplate EEO; we should remove. - Also "We’d love to meet you!" etc. - Also "Learn about Sage | About our companies | Open editor positions" etc. Remove. - Also "Sage is committed to the full inclusion of all qualified applicants. Accommodations will be made for any part of the interview process." That's accommodation statement; could be considered EEO/legal; we should remove. - Also "If you have a disability and you need any support during the application process, please contact hr.resume@sagepub.com" - remove. - Also "All qualified applicants are encouraged to apply." - remove. - Also "If you are excited about this role and feel you would be a good fit, please apply." - remove. - Also "If your desired salary falls outside of this range, we hope you'll still apply as there may be other positions that better align." - remove. - Also "Please note that the compensation details listed in U.S. role postings reflect the base salary only and do not include bonuses or benefits. Your recruiter can share more about the specific salary range and additional aspects of the compensation/benefits package for this position during the hiring process." This is part of Pay Transparency & Benefits Package; we can keep some of it but not the application instruction. The sentence about recruiter sharing more is okay as it's about compensation details. However it's somewhat generic but still about pay. We'll keep. - Also "Compensation at Sage is influenced by several factors, including but not limited to skill set, nature and level of experience, qualifications, and other relevant considerations." Keep. - Also "Sage Publishing is committed to being an inclusive employer where all individuals are treated with fairness and respect." That's EEO; remove. - Also "Sage is proud to be an equal opportunity workplace and is an affirmative action employer." Remove. Now we need to decide sections. We have: - About the role: intro paragraph + maybe mission statement? We'll keep intro paragraph only. - Responsibilities: "What You Will Do" bullet list. - Requirements: "What You Will Bring" bullet list (mandatory). Could also include "Preferred Requirements" as part of Requirements or separate "Preferred Requirements" but we only have allowed headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map "What You Will Bring" to Requirements (or Qualifications). "Preferred Requirements" could be Skills or Qualifications. Let's think. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We have mandatory experience: 3-5 years experience as product owner etc. That's a requirement. We have track record of writing clear user stories etc. That's requirement. Strong stakeholder management. Confidence working with data. Experience working in agile delivery teams. Genuine curiosity about the business. Those are requirements/qualifications. Preferred Requirements: Experience with Microsoft Dynamics 365, or another CRM; Background in publishing, higher education, media, or advertising sales; Experience with system integrations, data migration, or wider Microsoft Power Platform; Experience supporting teams through changes in process or tooling; A product owner or agile certification such as CSPO. Those could be Skills or Qualifications. We could have: - Requirements: mandatory items. - Qualifications: preferred items (or Skills). But we need to avoid thin sections. Could combine Requirements and Qualifications into one? But we need to follow headings; we can have both if they have substantive content. Better: Use Requirements for mandatory, Qualifications for preferred (or Skills). Let's decide: - Requirements: mandatory experience and skills. - Qualifications: preferred experience/background/certification. - Skills: maybe we could list technical skills like Dynamics 365, data analysis, agile, stakeholder management. But we already covered. We could also have a Skills section for technical skills: Experience with Microsoft Dynamics 365, Salesforce, HubSpot; System integrations; Data migration; Microsoft Power Platform; Agile methodologies; etc. But we risk duplication. Given the instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to follow the allowed headings; we can choose to include only Requirements and maybe Skills. Let's think: The posting has clear "What You Will Bring" (mandatory) and "Preferred Requirements". Could treat "What You Will Bring" as Requirements, and "Preferred Requirements" as Skills (or Qualifications). Since Skills heading is allowed, we can put preferred items there. Thus: - About the role: intro paragraph. - Responsibilities: bullet list of What You Will Do. - Requirements: bullet list of What You Will Bring (mandatory). - Skills: bullet list of Preferred Requirements. - Benefits: bullet list of benefits described. - Pay: paragraph about compensation details. - Schedule: mention hybrid or remote work depending on role. We need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to format. Use

for each section heading. Inside each section, use

• for lists,

  for prose. We must not repeat job title. We must not include Job ID/requisition numbers. We must preserve all substantive information. Let's extract the exact text for each. Intro paragraph: We'll copy the first paragraph(s) up to before "What You Will Do". Let's capture: "This role sits in the Product Management team within Sage Technology, the department responsible for building and maintaining the systems that run our business. You will report into Product Management and work alongside other product owners, product managers, engineers, and architects across the technology estate. Your product is Microsoft Dynamics CRM, and your internal customers are our college textbook sales and journal advertising sales divisions. Dynamics is where their pipeline is managed, customer relationships are tracked, and revenue decisions get made. You own the backlog for that platform and you are accountable for making it genuinely better for the people who depend on it every day. This is a role for a technologist with real commercial awareness. You will spend your time between two worlds: out in the business understanding what is slowing sales teams down, and back with your delivery team turning that into work that ships. Because Dynamics sits at the center of several business processes, you will also manage dependencies with other product teams inside Sage Technology." That's the About the role. Now Responsibilities: bullet points from "What You Will Do". Let's list them exactly: - Own and prioritize the product backlog, making clear decisions about sequencing and trade-offs, and keeping the roadmap connected to both business objectives and the wider technology strategy. - Build strong relationships with your internal customers in textbook sales and journal advertising sales, translating their needs into well-defined, valuable work for the delivery team. - Lead discovery and validation. Talk to users, interrogate the data, and test assumptions before committing engineering effort. - Partner closely with engineers and architects in Sage Technology, developing enough technical understanding of the platform to anticipate delivery risks and shape feasible solutions. - Manage competing priorities and cross-team dependencies within the technology estate, negotiating openly when demands conflict and keeping stakeholders aligned on what is happening and why. - Define what success looks like, then measure it. Use adoption data, performance metrics, and user feedback to judge whether changes actually worked. - Contribute to the Product Management team's own practice, supporting your delivery team's agile ways of working and mentoring colleagues in good product habits. Now Requirements: bullet points from "What You Will Bring". Let's list: - 3-5 years of experience as a product owner, product manager, or in a comparable role, with hands-on responsibility for a backlog. If your experience sits slightly outside that range but you can show the capability, we would still like to hear from you. - A track record of writing clear user stories and acceptance criteria, and running effective refinement with a delivery team. - Strong stakeholder management. You can hold your ground with senior people, say no with a reason, and keep relationships intact. - Confidence working with data to inform prioritization, and the critical thinking to question what the numbers are actually telling you. - Experience working in agile delivery teams, ideally with colleagues in multiple locations and time zones. - Genuine curiosity about the business you support and the users you serve. Now Skills: bullet points from "Preferred Requirements". Let's list: - Experience with Microsoft Dynamics 365, or with another CRM platform such as Salesforce or HubSpot. - Background in publishing, higher education, media, or advertising sales. - Experience with system integrations, data migration, or the wider Microsoft Power Platform. - Experience supporting teams through changes in process or tooling. - A product owner or agile certification such as CSPO. - Helpful context, not a requirement. We are more interested in how you think than in whether you tick every box. The last bullet is a bit meta; we could keep it as part of Skills but it's more a note. It's substantive? It says "Helpful context, not a requirement. We are more interested in how you think than in whether you tick every box." That's not a specific requirement but still content.