Product Manager
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes EEO statement at end: "ESO is committed to creating a diverse and inclusive work environment..." That's boilerplate; remove. Also "All offers are contingent upon a successful background check." Might be considered boilerplate but it's substantive? It's a condition; maybe keep? It's not a list; could be a short p. However it's generic; but it's not EEO. Might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The background check line is not exactly EEO; it's a condition. Might keep as part of role? But it's not about role; it's a hiring condition. Could be considered boilerplate? Not sure. Safer to keep? The instruction says remove legal boilerplate; background check is legal. I'd remove it.
Also "Applicant Privacy Notice – please click here..." remove.
Also "Are you ready to Make a Difference?" etc is motivational; could be part of About the role? Might keep as prose.
We need to preserve all substantive information: responsibilities list, requirements list, benefits list.
Let's extract sections.
About the role: combine "How You’ll Support Our Mission" paragraph and maybe "Are you ready to Make a Difference?" and "At ESO, we believe..." etc. But we should not repeat job title. We'll put that as prose.
Responsibilities: bullet list from "What You’ll Be Doing - the Day to Day" includes many items. We'll turn each bullet into
- . The paragraph before bullet list: "You manage the planning and execution throughout the product lifecycle..." could be prose before list. We'll include that as
then
.
Requirements/Qualifications/Skills: The "Who You Are - some of the essential things required to be successful in the role:" includes bullet-like list but not formatted as bullet; it's sentences separated by line breaks. We'll need to turn into list? The instruction: use - for any list of duties/requirements/benefits. So we should treat each requirement as list item. We'll split by sentences or line breaks. Let's extract:
- Five or more years of experience in product management, product ownership, or a similar backlog-ownership role, including experience across more than one team or domain.
- Experience in product management at a fast-growing software company.
- Proficient and experienced using AI to optimize your day-to-day job, as well as building AI-first product solutions.
- Hands-on experience using AI tools (for example, Claude, Magic Patterns, or similar platforms) for drafting requirements, building functional prototypes, synthesizing feedback, or generating status communications.
- Strong judgment for reviewing and correcting AI-generated content before it reaches a team or a stakeholder.
- Working knowledge of Agile and Scrum practices, including backlog refinement, story writing, and sprint ceremonies.
- Strong track record monitoring success via outcomes and metrics.
- Significant experience defining and launching features that meet the needs of both the customers and the business.
- Demonstrated strategic planning and operational execution skills, including process improvement.
- Experience mentoring and developing junior talent and driving product excellence.
- Clear written and verbal communication across technical and non-technical audiences.
Also "Also great to have:" items are optional; we could treat as Skills? Might include as separate list under Skills? But we have no separate Skills section; we could incorporate into Requirements or Qualifications. The instruction: prefer a few substantive sections over many thin ones. We could have Requirements section covering both required and nice-to-have. Or we could have Qualifications for required, Skills for nice-to-have. But we need to decide based on content. The posting separates "Who You Are - some of the essential things required..." and "Also great to have:" So we could have Requirements (essential) and Skills (nice-to-have). That seems reasonable.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
We must not include Pay or Schedule.
Now Benefits: list from "Benefits & Perks". Items:
- Competitive health plan (medical, dental, & vision insurance)
- RRSP with company match
- Telemedicine service provided by ESO
- Front-loaded vacation and sick time
- Employee Assistance Program (EAP)
- Peace of mind benefits such as life insurance and disability insurance
We'll put as
.
Now ensure we don't include any boilerplate like "About ESO" etc. Could we include a brief "About ESO" as part of About the role? Might be okay but it's not about the role. Might be considered extra but not prohibited. However instruction: "Prefer a few substantive sections over many thin ones." Including About ESO may be thin. I'd omit it.
Now produce HTML fragment.
We'll start with About the role
then ... combine intro paragraphs.
Intro paragraphs: "How You’ll Support Our Mission We are looking for an experienced Product Manager to take the reins of the products EMS agencies and fire departments rely on every day: from the moment a 911 call comes in, through patient care and transport, to the reporting that follows. As a Product Manager behind these product lines, you will combine technology and design to solve real customer problems in a way that meets the needs of the business. This is achieved by engaging with stakeholders, applying product discovery techniques, and evaluating success through leading and lagging indicators. Our vision is to provide our customers with meaningful information that leads to actionable outcomes, improving community health and safety outcomes through the power of data. This role carries that work across more teams than a traditional structure allows. You will hold product-owner-level rigor for backlog priorities, user stories, and delivery detail across multiple team/domains, using AI tooling to absorb the administrative volume: first-draft story writing, request triage, dependency mapping, and status reporting. This is not a traditional Product Manager role scoped to strategy alone, and it is not a single-team Product Owner role. It sits between the two: strategic enough to make trade-off calls across a portfolio and detailed enough to remain accountable for the backlog quality each team depends on. The ideal candidate has strong product acumen and experience using AI for efficiency gains, as well as the soft skills to coordinate with all functional areas of the organization toward successful product launches."
Then maybe add "Are you ready to Make a Difference? At ESO, we believe in bringing your true self to work every single day. If you don’t match all the qualifications on the job description, we encourage you to apply anyway! We are looking for passionate, innovative, and authentic people to help drive our mission." This is motivational; could be included.
We'll combine into one
or multiple
. Use
for prose; we can have multiple
elements.
Now Responsibilities:
Responsibilities
then You manage the planning and execution throughout the product lifecycle: market analysis, requirements gathering, ideation, decision making, software development, and go-to-market readiness with cross-functional teams. You know how to manage by influence, listening to your partners and guiding toward a common goal. You consistently assess the value behind any action. You enjoy getting firsthand feedback from agencies and knowing how your work reaches the crews who use it on every call. You can expect to:
then with each bullet.
List items from bullet list:
- Define product vision, strategy, and roadmap for the Fire and EMS domains you own.
- Own, prioritize, and maintain the product backlog for each assigned team or domain, ensuring every backlog reflects current business value and portfolio priorities.
- Communicate the product vision by highlighting proposed features and their business value.
- Use rapid prototyping tools such as Magic Patterns to turn concepts into functional prototypes, putting working examples in front of stakeholders and customers to test desirability and usability before engineering commits build time.
- Use AI tools to draft user stories and acceptance criteria from source material such as customer requests, support tickets, and stakeholder notes, then review and refine each draft before it reaches a team.
- Maintain a single, consistent definition of priority across all owned backlogs so teams are not working against conflicting signals.
- Engage with a variety of stakeholders (Sales, Support, Customer Success, Onboarding, Executives) in an ongoing dialogue to understand and manage competing priorities and trade-offs.
- Gather and refine product requirements from a variety of input streams, from direct customer input through support channels, to steering committees and time spent with agencies and departments in the field.
- Prioritize initiatives based on a multitude of variables: prehospital and fire reporting requirements such as the National Emergency Response Information System (NERIS), National EMS Information System (NEMSIS), state and local compliance, customer needs, sales drivers, technology changes, and more.
- Use AI tools to triage incoming requests, bugs, and enhancement ideas across domains, and route or reprioritize based on business value and dependency.
- Own the intake and triage of customer feedback through Pendo to optimize Net Promoter Scores (NPS) and Product Engagement Scores (PES).
- Use AI tools to surface cross-team dependencies and sequencing conflicts before they affect a sprint.
- Work as a product trio with product design and engineering to determine viability, feasibility, and desirability.
- Participate in Scrum ceremonies (backlog refinement, sprint review, planning) across owned teams, adjusting cadence and depth of involvement to each team’s needs.
- Partner with Technical Program Managers (TPMs), Engineering, and Product Managers on adjacent domains to keep priorities aligned at the portfolio level.
- Manage releases as a collection of new and incremental features, architectural improvements, and allocations for technical debt.
- Generate first-draft sprint summaries, release notes, and stakeholder updates using AI tools, then edit for accuracy and tone before sharing.
- Review all AI-drafted stories, requirements, and communications for accuracy before they are finalized; AI output is a draft, not a deliverable.
- Keep customer and business context, not AI output, as the final authority on prioritization decisions, and flag gaps or errors in tooling to product leadership.
- Work with system architects to understand architectural work, to assist with decision-making and sequencing of the key technological infrastructures that support your products.
- Create enablement documentation and playbooks to empower internal teams.
- Escalate trade-offs that cannot be resolved at the team level to product leadership with a clear recommendation.
- Contribute to retrospectives and evaluate returns on investment.
- Provide direct support and coaching to all levels of management as they help their direct reports.
- Plan and execute the adoption of ESO development methodology (PIs and Sprints, PRDs and BRDs, release notes, product enablement) and tools (Jira, Confluence, Teams) in close collaboration with Engineering leadership.
Now Success in the role looks like: bullet list. Should we include that as part of Responsibilities? It's more about success metrics; could be part of Responsibilities or a separate section? The instruction: include a section only when posting has real specific content. This is specific
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes EEO statement at end: "ESO is committed to creating a diverse and inclusive work environment..." That's boilerplate; remove. Also "All offers are contingent upon a successful background check." Might be considered boilerplate but it's substantive? It's a condition; maybe keep? It's not a list; could be a short p. However it's generic; but it's not EEO. Might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The background check line is not exactly EEO; it's a condition. Might keep as part of role? But it's not about role; it's a hiring condition. Could be considered boilerplate? Not sure. Safer to keep? The instruction says remove legal boilerplate; background check is legal. I'd remove it. Also "Applicant Privacy Notice – please click here..." remove. Also "Are you ready to Make a Difference?" etc is motivational; could be part of About the role? Might keep as prose. We need to preserve all substantive information: responsibilities list, requirements list, benefits list. Let's extract sections. About the role: combine "How You’ll Support Our Mission" paragraph and maybe "Are you ready to Make a Difference?" and "At ESO, we believe..." etc. But we should not repeat job title. We'll put that as prose. Responsibilities: bullet list from "What You’ll Be Doing - the Day to Day" includes many items. We'll turn each bullet into
then
- .
Requirements/Qualifications/Skills: The "Who You Are - some of the essential things required to be successful in the role:" includes bullet-like list but not formatted as bullet; it's sentences separated by line breaks. We'll need to turn into list? The instruction: use
- for any list of duties/requirements/benefits. So we should treat each requirement as list item. We'll split by sentences or line breaks. Let's extract:
- Five or more years of experience in product management, product ownership, or a similar backlog-ownership role, including experience across more than one team or domain.
- Experience in product management at a fast-growing software company.
- Proficient and experienced using AI to optimize your day-to-day job, as well as building AI-first product solutions.
- Hands-on experience using AI tools (for example, Claude, Magic Patterns, or similar platforms) for drafting requirements, building functional prototypes, synthesizing feedback, or generating status communications.
- Strong judgment for reviewing and correcting AI-generated content before it reaches a team or a stakeholder.
- Working knowledge of Agile and Scrum practices, including backlog refinement, story writing, and sprint ceremonies.
- Strong track record monitoring success via outcomes and metrics.
- Significant experience defining and launching features that meet the needs of both the customers and the business.
- Demonstrated strategic planning and operational execution skills, including process improvement.
- Experience mentoring and developing junior talent and driving product excellence.
- Clear written and verbal communication across technical and non-technical audiences.
Also "Also great to have:" items are optional; we could treat as Skills? Might include as separate list under Skills? But we have no separate Skills section; we could incorporate into Requirements or Qualifications. The instruction: prefer a few substantive sections over many thin ones. We could have Requirements section covering both required and nice-to-have. Or we could have Qualifications for required, Skills for nice-to-have. But we need to decide based on content. The posting separates "Who You Are - some of the essential things required..." and "Also great to have:" So we could have Requirements (essential) and Skills (nice-to-have). That seems reasonable.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
We must not include Pay or Schedule.
Now Benefits: list from "Benefits & Perks". Items:
- Competitive health plan (medical, dental, & vision insurance)
- RRSP with company match
- Telemedicine service provided by ESO
- Front-loaded vacation and sick time
- Employee Assistance Program (EAP)
- Peace of mind benefits such as life insurance and disability insurance
We'll put as
- .
Now ensure we don't include any boilerplate like "About ESO" etc. Could we include a brief "About ESO" as part of About the role? Might be okay but it's not about the role. Might be considered extra but not prohibited. However instruction: "Prefer a few substantive sections over many thin ones." Including About ESO may be thin. I'd omit it.
Now produce HTML fragment.
We'll start with
About the role
then... combine intro paragraphs. Intro paragraphs: "How You’ll Support Our Mission We are looking for an experienced Product Manager to take the reins of the products EMS agencies and fire departments rely on every day: from the moment a 911 call comes in, through patient care and transport, to the reporting that follows. As a Product Manager behind these product lines, you will combine technology and design to solve real customer problems in a way that meets the needs of the business. This is achieved by engaging with stakeholders, applying product discovery techniques, and evaluating success through leading and lagging indicators. Our vision is to provide our customers with meaningful information that leads to actionable outcomes, improving community health and safety outcomes through the power of data. This role carries that work across more teams than a traditional structure allows. You will hold product-owner-level rigor for backlog priorities, user stories, and delivery detail across multiple team/domains, using AI tooling to absorb the administrative volume: first-draft story writing, request triage, dependency mapping, and status reporting. This is not a traditional Product Manager role scoped to strategy alone, and it is not a single-team Product Owner role. It sits between the two: strategic enough to make trade-off calls across a portfolio and detailed enough to remain accountable for the backlog quality each team depends on. The ideal candidate has strong product acumen and experience using AI for efficiency gains, as well as the soft skills to coordinate with all functional areas of the organization toward successful product launches." Then maybe add "Are you ready to Make a Difference? At ESO, we believe in bringing your true self to work every single day. If you don’t match all the qualifications on the job description, we encourage you to apply anyway! We are looking for passionate, innovative, and authentic people to help drive our mission." This is motivational; could be included. We'll combine into one
or multiple
. Use
for prose; we can have multiple
elements. Now Responsibilities:
Responsibilities
thenYou manage the planning and execution throughout the product lifecycle: market analysis, requirements gathering, ideation, decision making, software development, and go-to-market readiness with cross-functional teams. You know how to manage by influence, listening to your partners and guiding toward a common goal. You consistently assess the value behind any action. You enjoy getting firsthand feedback from agencies and knowing how your work reaches the crews who use it on every call. You can expect to:
then- with each bullet.
List items from bullet list:
- Define product vision, strategy, and roadmap for the Fire and EMS domains you own.
- Own, prioritize, and maintain the product backlog for each assigned team or domain, ensuring every backlog reflects current business value and portfolio priorities.
- Communicate the product vision by highlighting proposed features and their business value.
- Use rapid prototyping tools such as Magic Patterns to turn concepts into functional prototypes, putting working examples in front of stakeholders and customers to test desirability and usability before engineering commits build time.
- Use AI tools to draft user stories and acceptance criteria from source material such as customer requests, support tickets, and stakeholder notes, then review and refine each draft before it reaches a team.
- Maintain a single, consistent definition of priority across all owned backlogs so teams are not working against conflicting signals.
- Engage with a variety of stakeholders (Sales, Support, Customer Success, Onboarding, Executives) in an ongoing dialogue to understand and manage competing priorities and trade-offs.
- Gather and refine product requirements from a variety of input streams, from direct customer input through support channels, to steering committees and time spent with agencies and departments in the field.
- Prioritize initiatives based on a multitude of variables: prehospital and fire reporting requirements such as the National Emergency Response Information System (NERIS), National EMS Information System (NEMSIS), state and local compliance, customer needs, sales drivers, technology changes, and more.
- Use AI tools to triage incoming requests, bugs, and enhancement ideas across domains, and route or reprioritize based on business value and dependency.
- Own the intake and triage of customer feedback through Pendo to optimize Net Promoter Scores (NPS) and Product Engagement Scores (PES).
- Use AI tools to surface cross-team dependencies and sequencing conflicts before they affect a sprint.
- Work as a product trio with product design and engineering to determine viability, feasibility, and desirability.
- Participate in Scrum ceremonies (backlog refinement, sprint review, planning) across owned teams, adjusting cadence and depth of involvement to each team’s needs.
- Partner with Technical Program Managers (TPMs), Engineering, and Product Managers on adjacent domains to keep priorities aligned at the portfolio level.
- Manage releases as a collection of new and incremental features, architectural improvements, and allocations for technical debt.
- Generate first-draft sprint summaries, release notes, and stakeholder updates using AI tools, then edit for accuracy and tone before sharing.
- Review all AI-drafted stories, requirements, and communications for accuracy before they are finalized; AI output is a draft, not a deliverable.
- Keep customer and business context, not AI output, as the final authority on prioritization decisions, and flag gaps or errors in tooling to product leadership.
- Work with system architects to understand architectural work, to assist with decision-making and sequencing of the key technological infrastructures that support your products.
- Create enablement documentation and playbooks to empower internal teams.
- Escalate trade-offs that cannot be resolved at the team level to product leadership with a clear recommendation.
- Contribute to retrospectives and evaluate returns on investment.
- Provide direct support and coaching to all levels of management as they help their direct reports.
- Plan and execute the adoption of ESO development methodology (PIs and Sprints, PRDs and BRDs, release notes, product enablement) and tools (Jira, Confluence, Teams) in close collaboration with Engineering leadership.
Now Success in the role looks like: bullet list. Should we include that as part of Responsibilities? It's more about success metrics; could be part of Responsibilities or a separate section? The instruction: include a section only when posting has real specific content. This is specific