Product Manager

We need to output HTML fragment with sections for headings where there is real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, EEO, etc. Keep substantive info. We need to parse the posting. Content: Intro paragraph about HDR culture etc. Could be "About the role"? Actually "About the role" maybe includes description of role and company. We'll include a

with that intro. Then responsibilities: bullet list from "In the role of Product Manager, we'll count on you to:" followed by many items. Then Preferred Qualifications: list. Then Required Qualifications: list. Then maybe "What We Believe" and "Our Commitment" could be part of About the role? Could be separate sections but we only create headings when there is real specific content. Could have "About the role" covering company description and role context. Could also have "Skills" maybe not needed. Benefits, Pay, Schedule: we have Schedule: Full-time mentioned. Also Employee Status: Regular. BusinessClass: Digital. Location etc. But we should only include Schedule if posting actually states them. It says Schedule:Full-time Employee Status:Regular BusinessClass:Digital Job Posting:Sep 28, 2026. So we have schedule info: Full-time. Also location: Primary Location: United States-Texas-Round Rock Other Locations: United States-Texas-Austin. Could be included maybe under About the role? But we have no heading for Location; we could put location in a

under About the role or maybe a separate section? Not required headings. We'll include location in About the role paragraph. We should not create Benefits or Pay sections because not mentioned. We should not create Skills section unless we have specific skills list; we have qualifications but those are under Requirements/Qualifications. Could combine Requirements and Qualifications? The instruction: use headings for those categories if content exists. We have both Preferred Qualifications and Required Qualifications. Could put them under "Qualifications" heading with sub-sections? But we must follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications headings if we have content. However we have both "Preferred Qualifications" and "Required Qualifications". Could treat Required Qualifications as "Requirements" and Preferred Qualifications as "Qualifications". That seems appropriate. Thus:

About the role

... (company description + location)

Responsibilities

• ... each responsibility

Requirements

• ... Required Qualifications list

Qualifications

• ... Preferred Qualifications list

Schedule

Full-time

We might also include Employee Status? Not needed. We must not include boilerplate like "At HDR, we are committed to the principles..." etc. Remove EEO etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given. Let's extract responsibilities list: - Define and communicate product vision, strategy, and roadmaps aligned with business objectives and user needs. - Partner with business stakeholders, users, and technical teams to identify opportunities for new products, features, and process improvements. - Gather, analyze, and prioritize business requirements, customer feedback, and market insights to inform product direction. - Create and maintain product backlogs, user stories, acceptance criteria, and release plans. - Collaborate closely with software developers, architects, designers, and quality assurance teams throughout the product lifecycle. - Lead product planning activities and ensure alignment between strategic priorities and development efforts. - Track product performance, adoption, and user satisfaction metrics to drive continuous improvement. - Facilitate stakeholder reviews, demonstrations, and feedback sessions to ensure delivered solutions meet expectations. - Coordinate product releases and communicate feature enhancements, roadmap updates, and business value to stakeholders. - Evaluate emerging technologies, automation opportunities, and AI capabilities that can create value for the organization. - Support organizational change management, training, and user adoption activities for new products and features. - Act as the primary advocate for users, ensuring solutions deliver measurable business outcomes and exceptional user experiences Now Required Qualifications list: - Bachelor's degree or equivalent experience - Proven work experience in an agile software development team - Proven work experience in software quality assurance - Strong knowledge of software QA methodologies, tools and processes - Experience in writing clear, concise and comprehensive test plans and test cases - Hands-on experience with both white box and black box testing - Hands-on experience with automated testing tools - Solid knowledge of SQL and scripting - Experience working in an Agile/Scrum development process Preferred Qualifications list: - A minimum of 2 years of experience supporting the development and delivery of enterprise software products. - Experience defining product vision, strategy, and roadmaps aligned with business objectives. - Experience gathering, documenting, prioritizing, and managing product requirements and user stories. - Experience working with Agile software development teams as a Product Manager, Product Owner, Business Analyst, or similar role. - Demonstrated ability to balance stakeholder priorities, customer needs, technical constraints, and business value. - Experience managing product lifecycles from concept through deployment and ongoing support. - Experience utilizing product management and Agile planning tools such as Jira, Azure DevOps, or similar platforms. - Experience analyzing data, product metrics, and user feedback to support product decisions and prioritization. - Experience collaborating with software developers, UX designers, architects, and business leaders to deliver successful products. - Experience with cloud-based applications, APIs, automation solutions, data platforms, or artificial intelligence technologies. - Knowledge of change management, user adoption strategies, and organizational communications. - Experience supporting digital transformation initiatives and process improvement efforts. - Understanding of Architecture, Engineering, and Construction (AEC) workflows, professional services, or related technical industries preferred. - Certified Scrum Product Owner (CSPO), Professional Scrum Product Owner (PSPO), Pragmatic Institute Certification, or similar certification preferred. Now About the role paragraph: combine the introductory paragraphs about HDR culture, employee-ownership, service lines, etc., plus location. We need to preserve all substantive information; not invent or summarize away detail. So we need to include the descriptive text about HDR, employee-ownership, service lines, etc. Also location. Let's extract the descriptive text before responsibilities: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story:' https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. At HDR, our employee‑ownership model shapes everything we do, including how we support and care for our people. Our diverse service lines, including Water, Architecture, Building Engineering Services, Field Services, Power, Waste, Industrial, and Transportation reflect our commitment to shaping resilient, sustainable, and forward‑thinking communities around the world. Across these disciplines, our teams design and deliver solutions that safeguard public health, enhance quality of life, power innovation, and drive responsible growth. Whether advancing clean water, creating healing and learning environments, engineering next‑generation facilities, or building the infrastructure that moves people and energy, our work is rooted in technical excellence and a shared sense of purpose. Our employee‑owners collaborate across specialties, combining creativity, precision, and deep expertise to solve the most complex challenges facing our clients and communities." We should keep that as is, maybe remove the URL? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not boilerplate; it's a link to Our Story. Might be considered navigation? It's a link; but it's part of the description. Probably we keep it? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The URL is not necessarily boilerplate; it's a reference. Might be okay to keep. But we could drop it as it's a link; but it's not navigation per se. Safer to keep? However the instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The URL is not metadata; it's a reference. I'd keep it. But we need to ensure we don't include any application instructions. There's none. Now location: "Primary Location:United States-Texas-Round Rock Other Locations:United States-Texas-Austin". We'll include that in About the role paragraph maybe as a sentence. Now Schedule: "Schedule:Full-time Employee Status:Regular BusinessClass:Digital Job Posting:Sep 28, 2026". We'll include schedule as Full-time. Could also include Employee Status etc but not needed. Now we need to output only HTML fragment. Let's construct:

About the role

At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. At HDR, our employee‑ownership model shapes everything we do, including how we support and care for our people. Our diverse service lines, including Water, Architecture, Building Engineering Services, Field Services, Power, Waste, Industrial, and Transportation reflect our commitment to shaping resilient, sustainable, and forward‑thinking communities around the world. Across these disciplines, our teams design and deliver solutions that safeguard public health, enhance quality of life, power innovation, and drive responsible growth. Whether advancing clean water, creating healing and learning environments, engineering next‑generation facilities, or building the infrastructure that moves people and energy, our work is rooted in technical excellence and a shared sense of purpose. Our employee‑owners collaborate across specialties, combining creativity, precision, and deep expertise to solve the most complex challenges facing our clients and communities. Primary Location: United States-Texas-Round Rock. Other Locations: United States-Texas-Austin.

Responsibilities

• Define and communicate product vision, strategy, and roadmaps aligned with business objectives and user needs.
• Partner with business stakeholders, users, and technical teams to identify opportunities for new products, features, and process improvements.
• Gather, analyze, and prioritize business requirements, customer feedback, and market insights to inform product direction.
• Create and maintain product backlogs, user stories, acceptance criteria, and release plans.
• Collaborate closely with software developers, architects, designers, and quality assurance teams throughout the product lifecycle.
• Lead product planning activities and ensure alignment between strategic priorities and development efforts.
• Track product performance, adoption, and user satisfaction metrics to drive continuous improvement.
• Facilitate stakeholder reviews, demonstrations, and feedback sessions to ensure delivered solutions meet expectations.
• Coordinate product releases and communicate feature enhancements, roadmap updates, and