Product Owner

We need to produce HTML fragment with sections: About the role? The posting includes description of Winsupply, purpose, etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting: - Intro: "Winsupply is in the business of creating and enabling entrepreneurs to achieve their dreams through wholesale distribution. Winsupply is a group of over 670 locally-owned companies that operate across a variety of industries, including HVAC, Plumbing, Electrical and more. The purpose of the support services campus is to eliminate obstacles and provide support to help our entrepreneurs succeed. Support service employees assist entrepreneurs in achieving their dreams through finance, accounting, IT, and other back-office operations." That could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put "About the role" heading for that intro. Then "Job Description" includes many bullet-like sentences: "Will work on the project from inception to end using Agile, Competitive Benchmarking, Project Planning & Prioritization, Market Research, Go-to-Market Strategy, Customer Interviews, User Stories, Product Marketing, Road Mapping, Customer Journey, Brand Management, Change Management, Inventory Management, Logistics and Transportation Management, Procurement and Sourcing, Supply chain planning and optimization, Lean and Six Sigma Methodologies, Data analytics, Project Management, Risk Management, Vendor Management and Negotiations Technologies: Selenium, SQL, HTML, CSS, C, C++, Python, SAP, R, Figma, HPALM, qTest, AWS, Microsoft Excel, PowerPoint, Power BI, JIRA, Confluence, Google suite, Canva, Trello, MATLAB, LTSpice, VERILOG, RPA, Miro, Arduino, Blynk. Will define and communicate the product vision, ensuring the development team understands the long-term goals and how each piece of work contributes to the bigger picture, own the product backlog end to end, including creating, prioritizing, and continuously refining user stories based on business value, customer impact, and technical feasibility, write clear and detailed user stories with well-defined acceptance criteria so the dev team knows exactly what success looks like before they start building, make real-time scope and priority trade-off decisions when competing demands arise, balancing stakeholder needs against team capacity and delivery timelines, gather requirements from multiple sources including stakeholders, end users, leadership, and cross-functional partners, then translate those inputs into actionable backlog items, serve as the primary point of contact between the business side and the development team, ensuring both sides stay aligned and informed throughout the sprint cycle, review deliverables against acceptance criteria to validate and accept or reject completed work, ensuring quality standards are met before anything goes to production. Will define success metrics (KPIs) to ensure success is tracked in a measurable, data driven way and communicate product progress, risks, blockers, and upcoming plans to stakeholders and leadership through regular status updates, demos, and reporting. Will conduct or participate in backlog refinement sessions with the dev team to break down large epics, clarify requirements, estimate effort, and ensure upcoming work is sprint-ready and stay close to end users by gathering feedback, analyzing usage data, monitoring support issues, and conducting research to inform what gets built next and in what order. Will manage and validate external dependencies with partners and vendors, ensuring their deliverables align with internal sprint timelines and don't create downstream delays and agile ceremony leadership including sprint planning, sprint demos, and sprint retrospectives. Will define and own the product roadmap, adjusting it as priorities shift based on new business needs, market changes, or technical discoveries, champion the user experience by advocating for usability, consistency, and quality in every feature and screen the team delivers. Will drive alignment across teams by facilitating conversations, resolving conflicting priorities, and ensuring everyone works toward the same outcomes." That's responsibilities. Could be split into Responsibilities and Skills (technologies). The technologies list is a long list: Selenium, SQL, HTML, CSS, C, C++, Python, SAP, R, Figma, HPALM, qTest, AWS, Microsoft Excel, PowerPoint, Power BI, JIRA, Confluence, Google suite, Canva, Trello, MATLAB, LTSpice, VERILOG, RPA, Miro, Arduino, Blynk. We can put Skills section with that list. Qualifications: "Master of Science in Engineering Management or Computer Science with 12 months experience as Software Developer or Product Owner, foreign equivalent accepted, 40 hrs a week, Send resume to Winsupply Inc., Attn: Michelle Derrickson, it-recruitment@winsupply.com" Also there is "Additional Information Physical Demands ..." and EEO statement. We need to remove boilerplate like EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. The "Send resume to ..." is application instruction; we should remove application instructions. The instruction says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the line "Send resume to Winsupply Inc., Attn: Michelle Derrickson, it-recruitment@winsupply.com". Also remove the Physical Demands? That's not boilerplate; it's part of Additional Information. It might be considered relevant? It's not a standard heading but we could include as a paragraph under maybe "Additional Information". However the instruction only allows certain headings; we could just put it as a

under maybe no heading or under a generic section? The instruction says: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those headings only. Additional info like Physical Demands could be placed as a

after Qualifications maybe without a heading, or we could incorporate into Qualifications? But it's not qualification. Could be omitted? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep Physical Demands info. We could put it under a heading like "Additional Information" but that's not in the list. However the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive. But safer to follow the instruction: use those headings for sections. We could still add other headings if needed, but maybe better to keep within those. Physical Demands could be placed under "Requirements" or "Qualifications"? It's about physical demands, not qualifications. Could be under "Requirements". But Requirements heading is for list of duties/requirements/benefits. Could include physical demands as a list item under Requirements. However the posting already has Responsibilities etc. We could treat Physical Demands as part of Requirements. Thus we can have sections: About the role, Responsibilities, Skills, Qualifications. Possibly Requirements not needed if we put physical demands elsewhere. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities we should make a list. For Skills also list. For Qualifications maybe list? It's a short sentence; could be

  . For About the role we can use

  . We must not repeat the job title as a heading. No job title given explicitly; we can ignore. We must not put Job ID/requisition numbers as headings. We must not include sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's craft:

  About the role

  Winsupply is in the business of creating and enabling entrepreneurs to achieve their dreams through wholesale distribution. Winsupply is a group of over 670 locally-owned companies that operate across a variety of industries, including HVAC, Plumbing, Electrical and more. The purpose of the support services campus is to eliminate obstacles and provide support to help our entrepreneurs succeed. Support service employees assist entrepreneurs in achieving their dreams through finance, accounting, IT, and other back-office operations.

  Responsibilities

  • Work on the project from inception to end using Agile, Competitive Benchmarking, Project Planning & Prioritization, Market Research, Go-to-Market Strategy, Customer Interviews, User Stories, Product Marketing, Road Mapping, Customer Journey, Brand Management, Change Management, Inventory Management, Logistics and Transportation Management, Procurement and Sourcing, Supply chain planning and optimization, Lean and Six Sigma Methodologies, Data analytics, Project Management, Risk Management, Vendor Management and Negotiations.
  • Define and communicate the product vision, ensuring the development team understands the long-term goals and how each piece of work contributes to the bigger picture.
  • Own the product backlog end to end, including creating, prioritizing, and continuously refining user stories based on business value, customer impact, and technical feasibility.
  • Write clear and detailed user stories with well-defined acceptance criteria so the dev team knows exactly what success looks like before they start building.
  • Make real-time scope and priority trade-off decisions when competing demands arise, balancing stakeholder needs against team capacity and delivery timelines.
  • Gather requirements from multiple sources including stakeholders, end users, leadership, and cross-functional partners, then translate those inputs into actionable backlog items.
  • Serve as the primary point of contact between the business side and the development team, ensuring both sides stay aligned and informed throughout the sprint cycle.
  • Review deliverables against acceptance criteria to validate and accept or reject completed work, ensuring quality standards are met before anything goes to production.
  • Define success metrics (KPIs) to ensure success is tracked in a measurable, data‑driven way and communicate product progress, risks, blockers, and upcoming plans to stakeholders and leadership through regular status updates, demos, and reporting.
  • Conduct or participate in backlog refinement sessions with the dev team to break down large epics, clarify requirements, estimate effort, and ensure upcoming work is sprint‑ready; stay close to end users by gathering feedback, analyzing usage data, monitoring support issues, and conducting research to inform what gets built next and in what order.
  • Manage and validate external dependencies with partners and vendors, ensuring their deliverables align with internal sprint timelines and don't create downstream delays; lead agile ceremonies including sprint planning, sprint demos, and sprint retrospectives.
  • Define and own the product roadmap, adjusting it as priorities shift based on new business needs, market changes, or technical discoveries; champion the user experience by advocating for usability, consistency, and quality in every feature and screen the team delivers.
  • Drive alignment across teams by facilitating conversations, resolving conflicting priorities, and ensuring everyone works toward the same outcomes.

  Skills

  • Selenium
  • SQL
  • HTML
  • CSS
  • C
  • C++
  • Python
  • SAP
  • R
  • Figma
  • HPALM
  • qTest
  • AWS
  • Microsoft Excel
  • PowerPoint
  • Power BI
  • JIRA
  • Confluence
  • Google suite
  • Canva
  • Trello
  • MATLAB
  • LTSpice
  • VERILOG
  • RPA
  • Miro
  • Ar