IT Product Owner

We need to output HTML fragment with sections: About the role? Actually we have "About Leaf Home" at top, but we should not repeat job title. The posting includes sections: About Leaf Home, Why Leaf Home, Position Summary, Essential Duties and Responsibilities, Experience and Minimum Qualifications, Preferred Knowledge..., Travel Requirements, Other travel..., Overtime..., Physical Requirements, Disclaimer, Are We Your Company? (Focused on Growth), What We Offer, Additional Perks, Awards and Recognition, Diversity and Equal Opportunity, Americans with Disabilities Act Statement. We need to include only sections with real specific content, not filler. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we can use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings if applicable, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they want us to map content to those standard headings. But we can also include other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests we should use those for typical sections. Probably we should map content to those headings where appropriate. For example: About the role could be Position Summary. Responsibilities could be Essential Duties and Responsibilities. Requirements could be Experience and Minimum Qualifications. Qualifications could be Preferred Knowledge... Skills could be maybe not present. Benefits could be What We Offer (benefits). Pay and Schedule only if present; we have no explicit pay or schedule details, so we should NOT include Pay or Schedule sections. We must not repeat the job title as a heading. The job title is "IT Product Owner". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should strip out the Diversity and Equal Opportunity, Americans with Disabilities Act Statement? Those are EEO boilerplate; we should remove them. Also disclaimer maybe boilerplate? It's a generic disclaimer; might be considered boilerplate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the Disclaimer, Diversity and Equal Opportunity, Americans with Disabilities Act Statement. Also maybe "Are We Your Company?" is marketing fluff but not boilerplate; could keep as "About the company"? But we have "About Leaf Home" already. The "Are We Your Company? Focused on Growth" seems like marketing; could be considered part of About Leaf Home. Might be okay to keep as part of About Leaf Home? But we already have About Leaf Home section earlier. Might combine. We need to preserve all substantive information. So we need to keep details about responsibilities, qualifications, benefits, travel, overtime, physical requirements, awards, etc. We need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

Position Summary: ...

Responsibilities

• ... each duty

Requirements

• ... minimum qualifications

Qualifications

• ... preferred knowledge, skills, abilities or certifications

Skills

maybe not needed; we could omit if no specific skills beyond those listed. Could combine with Qualifications. But instruction: prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one? But they said use headings like Requirements, Qualifications, Skills. Could have separate sections if content exists. We have both minimum qualifications and preferred qualifications. So we can have Requirements (minimum) and Qualifications (preferred). Skills maybe not separate.

Benefits

• ... benefits list

We also have Travel Requirements, Overtime/Additional Hours Requirements, Physical Requirements. Those could be under a section like "Additional Information" but not in the list. Could we create a section "Travel & Schedule"? But we shouldn't create Schedule unless actual schedule info. We have travel and overtime info. Could create a section "Work Details" but not in the prescribed headings. However 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 suggests we should use those for typical sections. Might be okay to add other headings like "Travel Requirements", "Physical Requirements". But to be safe, we could incorporate travel and overtime into Responsibilities or Additional Notes? But they are substantive; we should keep them. Perhaps we can create a section "Additional Details" with

but not in the list; risk of violating instruction? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, just gives examples. So we can use other headings as needed. However they also say "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. Travel, overtime, physical requirements could be combined into a single "Working Conditions" section. Thus:

Working Conditions

• Travel: Occasional overnight travel required (1-10%); travel to Canada may be required, project dependent.
• Overtime: Additional and non-standard hours may be required (exempt); project dependent, could work weekends or after normal business hours.
• Physical Requirements: Normal office environment; sedentary work; exerting up to 10 pounds of force occasionally.

We also have Awards and Recognition; could be under "Awards and Recognition" section. We also have "What We Offer" benefits; we already have Benefits. We also have "Additional Perks" could be part of Benefits. We also have "Are We Your Company? Focused on Growth" maybe part of About Leaf Home. We need to avoid duplication: The "About Leaf Home" at top includes mission statement etc. We'll put that under About the role? Actually About the role is about the position; but we have "About Leaf Home" describing company. Could treat as "About the company" but not in list. Could put under About the role? Might be okay to have a section "About Leaf Home" as

About Leaf Home

but instruction says use

for section headings (e.g. About the role, Responsibilities...). It didn't forbid About Leaf Home. So we can include that. Thus final HTML:

About Leaf Home

At Leaf Home, we are powered by people on a single mission to make homeownership easy. We’ve crafted a team of the very best to ensure we make a difference by winning every day. In addition to serving our customers, Leaf Home strives to build a welcoming and inclusive workplace. We are proud to be a certified Great Place to Work® as well as a multi-year recipient of Top Workplaces recognition. From competitive medical benefits to people-focused committees like the Women’s Committee, Diversity & Inclusion Committee, and VetConnect, we are dedicated to making Leaf Home a workplace where you can win every day. Come grow your career with us.

About the role

Position Summary: The IT Product Owner is responsible for defining, prioritizing, and delivering software solutions and business processes that support internal business operations. This role serves as the bridge between business stakeholders and technical teams, ensuring internal tools and platforms align with organizational goals, improve operational efficiency, and deliver measurable business value. The IT Product Owner manages the product backlog, gathers requirements from internal stakeholders, and works closely with development teams to deliver high-quality software solutions that meet the needs of the organization.

Responsibilities

• Product Strategy & Vision: Define and communicate the vision, roadmap, and goals for internal software products; align internal software initiatives with business objectives and operational needs; identify opportunities to improve internal workflows through technology.
• Stakeholder Collaboration: Partner with internal teams (operations, sales, finance, marketing, etc.) to understand pain points and requirements; act as the primary liaison between business stakeholders and business analysts.
• Product Backlog Management: Create, prioritize, and maintain the product backlog; ensure backlog items are clearly defined and ready for development.
• Agile Development Support: Participate in sprint planning, standups, reviews, and retrospectives; provide guidance and clarification to developers during the development process; ensure delivered features meet acceptance criteria and business expectations.
• Product Delivery & Optimization: Validate completed features and ensure they deliver expected value; monitor product performance and user adoption; continuously identify enhancements and process improvements.
• Documentation & Communication: Maintain product documentation, workflows, business processes, and standard operating procedures; communicate updates, releases, and changes to internal stakeholders; provide training or guidance for internal users when needed.

Requirements

• Undergraduate (Bachelor's) degree in Business, Information Systems, Computer Science, or related field.
• 3+ years of experience in product management, product ownership, business analysis, or similar roles.
• 2 years of experience in a similar role (duplicate? but we keep as stated).
• Proficient with technology, including ERP, CRM, Data management, HCM, Automation, etc.
• Strong transformational leadership skills.
• Strong commitment to team environment.
• Proficiency using Microsoft Office Suite.
• Must be legally authorized to work in the country of employment without sponsorship for employment visa status (e.g., H1B status).

Qualifications

• Strong analytical and problem-solving skills.
• Experience delivering internal business software, operational systems, or enterprise tools preferred.
• Excellent communication and stakeholder management skills.
• Understanding of the software development lifecycle.
• Strong understanding of business processes across verticals.

Benefits

• Industry-leading compensation package.
• Competitive medical, dental, and vision benefits after 60 days.
• Retirement savings plan with company match.
• Paid parental leave and generous paid time off programs.
• On-campus fitness programs and meal delivery services.
• Comprehensive health, wellbeing, financial wellness, and childcare benefits.
• Opportunities for growth and advancement.
• Employee assistance program with 24/7 legal, financial, and counseling support.
• Employee discount marketplace with thousands of savings options.
• Flexible Gym membership.
• Employee resource groups, including VetConnect and the Women’s Committee.

Awards and Recognition

Leaf Home has been recognized as a top workplace by The Plain Dealer, is a multi-year recipient of Top Workplaces USA by Energage, and is Great Place to Work® Certified™. Additional recognitions include: Remodeling 550 list placements, Qualified Rem