Technical Product Owner

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description (About the role) maybe not explicitly labeled but we can treat first paragraph as About the role. Then Responsibilities & Duties is a section. Qualifications And Experience Required is a section. Skills maybe not explicit but we can infer from qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. The posting includes responsibilities, qualifications, maybe skills (list of skills). Benefits, Pay, Schedule not mentioned. So we should not include those sections. We need to preserve all substantive information, remove boilerplate like cookie/navigation/legal/EEO etc. The posting includes some values and life at Xplor, core values, etc. That might be considered boilerplate? It's not EEO but could be considered company culture; but we need to preserve substantive information. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The values section might be considered not boilerplate but could be kept? It's not directly about the role but maybe part of company description. However we should focus on role specifics. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the values? It's substantive about company but not about role. Might be okay to keep as part of About the role? But we have to avoid filler. The values section is not duplicated. It might be okay to include as part of About the role or maybe a separate section like "Company Overview". But headings limited to given list. Could embed in About the role paragraph. We need to output only HTML fragment, no /, no markdown fences. Structure:

About the role

then

...

. Then

Responsibilities

then

• ... each duty.

. Then

Qualifications

then

• ... each qualification.

. Possibly also Skills? Could extract skills from qualifications list: e.g., excellent oral/written communicator, critical thinking, analytical, data-driven decision-making, fast-paced, urgency, bug tracking, prioritize, influence, negotiation, presentation, manage diverse projects, multi-task, JIRA, Productboard, Pendo, Figma, AI experience, evaluating AI tools, writing AI skills, etc. Those could be considered skills. But we already have qualifications; maybe we can combine. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Qualifications (which includes skills). Avoid separate Skills if not explicitly present. We must not repeat job title as heading. No Job ID. We need to preserve all substantive information: include details about AI, MCP capabilities, Central Account Services, agentic experiences, etc. Ensure we capture all responsibilities bullet points. Let's extract responsibilities list from text: - Serve as Owner of the products; ensure products are meeting and exceeding the needs of external customers and prospects to expand addressable market and reduce/eliminate churn as well as internal stakeholders to allow for ease of implementation and support. - Maintain focus on technological trends and competitive landscape to drive innovation. - Identify opportunities to apply AI and automation within the product to improve efficiency, personalization, and decision-making for customers and internal users. - Drive continued advancement of strategic platform and AI initiatives across the Clubessential suite, with an initial emphasis on expanding our MCP capabilities, deepening integration with Central Account Services and shared platform products, and accelerating agentic experiences across Clubessential products and workflows. - Own the creation and grooming of the product backlog by writing and refining user stories that support sprint goals and align with product strategy. - Serve as the Gatekeeper of the product backlog and primary feedback loop owner regarding product enhancements, issues, bugs and/or tasks related to the products. - Escalate and timely communicate issues, related updates, and resolutions to internal stakeholders as appropriate. - Share and contribute meaningful ideas to achieve overall product success, while balancing needs of external customers, expansion of addressable market, ease to support and implement, and churn reduction in mind. - Coordinate with product leadership, customers, and team to complete research, develop specifications and user stories for the developers that satisfy business requirements and align with the business value. - Partner with engineering and data teams to define requirements, success metrics, and guardrails for AI-powered features, and communicate what those capabilities can and can't do to internal stakeholders and customers. - Provide timely feedback to internal stakeholders on plan for resolution; as appropriate, identify which bugs or enhancements will be worked and/or will not be prioritized. - Play an active role in mitigating impediments impacting successful team completion of Release/Goals; participate in testing and release readiness as required. - Assist with configuration and communicate availability of new features in demo environments. - Act as the go to person/liaison for answering questions the development team has about business rules and product behaviors, and/or other internal stakeholders regarding the respective products. - Assist in Rollout/Management/Feedback gathering where applicable. - Assist in reviewing educational and marketing materials pertaining to the product lines. - Deliver product releases and assist with release note creation/educational efforts with quick time-to-market and optimal resources. - Develop successful launch plans working directly with implementation, project management and support services, marketing, sales, and our customers. - Participate (when appropriate) in additional activities to support the education, marketing and/or success of the product such as webinars, shows, monthly/quarterly update meetings, and/or other activities as applicable. - Lead/Assist/Participate (as applicable) in all Scrum ceremonies. - Perform other responsibilities pertaining to the product, as assigned. Qualifications list: - BS/MS degree in Business, Engineering, or related field preferred - 3+ years’ work experience as product owner, business analyst or subject matter expert in SaaS software applications preferred - Excellent oral and written communicator up, down, across and outside the organization. - Strong critical thinking, analytical and data-driven decision-making skills. - Comfortable working in a fast-paced environment with a strong sense of urgency and accountability - Experience with bug/issue/enhancement tracking, project management software - Excels in ability to prioritize, influence decisions/decision makers, and handle objections - Excellent active listening, negotiation, communication, and presentation skills - Ability to manage numerous diverse projects and multi-task with ease - Experience with JIRA, Productboard, Pendo, and/or Figma a plus - Experience defining or shipping AI-powered product features, or working closely with data science/ML teams, a plus - Comfortable evaluating AI tools and vendors, weighing their capabilities and limitations, and translating them into clear customer value - Hands-on experience writing AI skills, skill chains, or agentic workflows to streamline day-to-day work such as research, spec writing, and backlog grooming a plus Also there is a values section: "Our Five Core Values Guide Us From How We Hire And Recognise Our Team Members To How We Interact With Our Customers Day To Day Find a better wayDo the right thingSay it straightWin togetherOwn the outcome". That could be considered company culture but not required. Might be okay to include as part of About the role? But we already have About the role description from first paragraph. Could add a short paragraph about company values after About the role? Might be considered filler? It's substantive but not about role. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it. Where to put? Could add another section like "Company Values" but not in allowed headings. Could embed in About the role paragraph after description. That would preserve it. Also there is a line: "At Xplor, we believe that the best innovation and ideas happen at the intersections of our differences - people of diverse cultures, generations, disciplines, and lived experiences. So even if you think you do not tick all the boxes, we still encourage you to apply." That's also substantive about encouragement. Could embed. Also "Ready to apply? To start your application, please submit your resume, and we will be in touch as soon as we can. Got questions? You can email us at talentsupport@xplortechnologies.com." That's application instructions, which we should remove per instruction: remove application instructions. So we should drop that. Also "Values and Life at Xplor Our Five Core Values Guide Us ..." that's values; we can keep. Thus final HTML:

About the role

Xplor Technologies powers the experiences at the heart of everyday life. Through modern vertical software, embedded payments, and AI-powered capabilities, we help businesses in fitness, recreation, golf and club, field services, laundry, education, and other membership-based and service-based industries simplify operations, uncover insights, and elevate customer and member experiences. We unite popular brands such as Clubessential, foreUP, myFitApp, Vermont Systems, Momence, Exerp, and many more. Technical Product Owner will work closely with the Clubessential product and development teams, as well as with clients and other internal and external stakeholders, to support the direction and strategy for our products. They will be in charge of informing the group of engineers, designer, and QA testers about the product vision, strategy, and direction. They act as the primary line of communication between the business stakeholders and the delivery teams, who will design, build, and test our products. The Technical Product Owner also will need to be able to communicate to comprehend our business prospects, translate them into a polished and manageable backlog, and manage the team’s deliverables. As AI becomes a bigger part of how we build products, the Technical Product Owner will also help identify where AI and automation can create real value for our customers, and work closely with engineering and data teams to bring those capabilities to life responsibly.

At Xplor, we believe that the best innovation and ideas happen at the intersections of our differences - people of diverse cultures, generations, disciplines, and lived experiences. So even if you think you do not tick all the boxes, we still encourage you to apply. Our Five Core Values Guide Us From How We Hire And Recognise Our Team Members To How We Interact With Our Customers Day To Day: Find a better way, Do the right thing, Say it straight, Win together, Own the outcome.

Responsibilities

• Serve as Owner of the products; ensure products are meeting and exceeding the needs of external customers and prospects to expand addressable market and reduce/eliminate churn as well as internal stakeholders to allow for ease of implementation and support.
• Maintain focus on technological trends and competitive landscape to drive innovation.
• Identify opportunities to apply AI and automation within the product to improve efficiency, personalization, and decision-making for customers and internal users.
• Drive continued advancement of strategic platform and AI initiatives across the Clubessential suite, with an initial emphasis on expanding our MCP capabilities, deepening integration with Central Account Services and shared platform products, and accelerating agentic experiences across Clubessential products and workflows.
• Own the creation and grooming of the product backlog by writing and refining user stories that support sprint goals and align with product strategy.
• Serve as the Gatekeeper of the product backlog and primary feedback loop owner regarding product enhancements, issues, bugs and/or tasks related to the products.
• Escalate and timely communicate issues, related updates, and resolutions to internal stakeholders as appropriate.
• Share and contribute meaningful ideas to achieve overall product success, while balancing needs of external customers, expansion of addressable market, ease to support and implement, and churn reduction in mind.
• Coordinate with product leadership, customers, and team to complete research, develop specifications and user stories for the developers that satisfy business requirements and align with the business value.