Senior Product Owner I
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract content.
About the role: The first 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.
Responsibilities: bullet list under "What You Will Do". Let's capture each bullet:
- 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.
That's responsibilities.
Requirements: "What you will bring" bullet 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.
That's required.
Preferred Requirements: 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. If you are excited about this role and feel you would be a good fit, please apply.
We could keep the last sentence as part of preferred requirements paragraph.
Benefits: details:
- 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.
- Join the nearly 2,000 Sage employees worldwide who deliver products and services that serve to fulfill our noble goal of education and dissemination of knowledge globally.
We might keep the last sentence as part of benefits? It's more about company mission; could be considered benefits? It's not a benefit per se but could be considered part of benefits section. However it's somewhat generic; but it's substantive. We'll include it as part of benefits paragraph.
Schedule: hybrid or remote work depending on role. That's already in benefits; but we could also make a Schedule section with that line. However to avoid duplication, we could put schedule info in Benefits section? The rule: we should not create Schedule section unless posting actually states them. It does state hybrid or remote work. We could make a Schedule section with that line. But we already have hybrid/remote in benefits; duplication might be okay but better to keep schedule separate. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine schedule into Benefits? But schedule is distinct. However we could include Schedule section with that line only; that's thin but it's actual content. Might be okay. But we could also incorporate schedule into Benefits as a bullet: "Hybrid or remote work options". That would avoid a thin schedule section. Let's do that: include hybrid/remote work as a benefit bullet.
Thus Benefits section will have bullets: PPO medical/dental/vision, company-sponsored anniversary trip every 5 years, 401(k)-matching 100% up to 5% of pay, financial support for bachelor's and graduate-level degree programs and learning for personal interest, hybrid or remote work options, and the mission statement maybe as prose.
We must not include boilerplate like EEO, diversity statement, etc. So we will omit the Diversity, Equity, and Inclusion section at end.
Also remove "All qualified applicants are encouraged to apply." etc.
Also remove "If you have a disability and you need any support during the application process, please contact hr.resume@sagepub.com". That's application instruction; remove.
Also remove "We’d love to meet you!" etc.
Also remove "Helpful context, not a requirement."? It's part of preferred requirements; we can keep as a sentence.
Now construct HTML.
We'll have:
About the role
... (the about role paragraph)
Responsibilities
- ... each bullet
Requirements
- ... each bullet
Preferred Requirements
- ... each bullet
Benefits
- ... each bullet
... any prose not in list (maybe the mission statement)
We need to ensure we don't include empty sections.
Let's craft the about role paragraph exactly as given, preserving details.
About role 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."
Now responsibilities bullets exactly as given.
Let's list them:
1. 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.
2. 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
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract content. About the role: The first 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. Responsibilities: bullet list under "What You Will Do". Let's capture each bullet: - 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. That's responsibilities. Requirements: "What you will bring" bullet 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. That's required. Preferred Requirements: 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. If you are excited about this role and feel you would be a good fit, please apply. We could keep the last sentence as part of preferred requirements paragraph. Benefits: details: - 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. - Join the nearly 2,000 Sage employees worldwide who deliver products and services that serve to fulfill our noble goal of education and dissemination of knowledge globally. We might keep the last sentence as part of benefits? It's more about company mission; could be considered benefits? It's not a benefit per se but could be considered part of benefits section. However it's somewhat generic; but it's substantive. We'll include it as part of benefits paragraph. Schedule: hybrid or remote work depending on role. That's already in benefits; but we could also make a Schedule section with that line. However to avoid duplication, we could put schedule info in Benefits section? The rule: we should not create Schedule section unless posting actually states them. It does state hybrid or remote work. We could make a Schedule section with that line. But we already have hybrid/remote in benefits; duplication might be okay but better to keep schedule separate. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine schedule into Benefits? But schedule is distinct. However we could include Schedule section with that line only; that's thin but it's actual content. Might be okay. But we could also incorporate schedule into Benefits as a bullet: "Hybrid or remote work options". That would avoid a thin schedule section. Let's do that: include hybrid/remote work as a benefit bullet. Thus Benefits section will have bullets: PPO medical/dental/vision, company-sponsored anniversary trip every 5 years, 401(k)-matching 100% up to 5% of pay, financial support for bachelor's and graduate-level degree programs and learning for personal interest, hybrid or remote work options, and the mission statement maybe as prose. We must not include boilerplate like EEO, diversity statement, etc. So we will omit the Diversity, Equity, and Inclusion section at end. Also remove "All qualified applicants are encouraged to apply." etc. Also remove "If you have a disability and you need any support during the application process, please contact hr.resume@sagepub.com". That's application instruction; remove. Also remove "We’d love to meet you!" etc. Also remove "Helpful context, not a requirement."? It's part of preferred requirements; we can keep as a sentence. Now construct HTML. We'll have:
About the role
... (the about role paragraph)
Responsibilities
- ... each bullet
Requirements
- ... each bullet
Preferred Requirements
- ... each bullet
Benefits
- ... each bullet
... any prose not in list (maybe the mission statement)
We need to ensure we don't include empty sections. Let's craft the about role paragraph exactly as given, preserving details. About role 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." Now responsibilities bullets exactly as given. Let's list them: 1. 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. 2. 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