Data Scientist

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. The posting includes: - Intro about HDR culture (maybe "About the role"? Actually that's about company, not role. Could be "About the role" or maybe "About HDR". The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections are present. We have: - Responsibilities: bullet list after "In the role of Data Scientist, we'll count on you to:" then list items. - Preferred Qualifications: line "Preferred Qualifications Bachelor's degree". Actually that seems like a heading "Preferred Qualifications" then "Bachelor's degree". Might be considered under Qualifications. - Required Qualifications: list after "Required Qualifications". Many bullet-like lines. - Skills: many proficiency statements etc. Could be under Skills. - Benefits: Not mentioned. No benefits details. - Pay: Not mentioned. - Schedule: "Schedule:Full-time" appears near the end under "Primary Location...". So we have schedule info: Full-time. - Also there is "Industry:Water", "BusinessClass:Water Treatment", "Job Posting:Sep 1, 2026". Those are metadata; we can fold into a short p or drop. We must not repeat job title as heading. The title is Data Scientist (implied). We should not put that as heading. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information; do not invent or summarize away detail. We need to output only HTML fragment, no html/body tags, no markdown fences. We need to use

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide sections: - About the role? Could include the introductory paragraph about HDR and the role description? The instruction says "About the role" as an example heading. We could put a short prose about the role and company under About the role. But we must not repeat job title as heading. That's fine. We have a paragraph at start: "At HDR, our employee-owners are fully engaged...". That's about company culture. Could be under About the role or maybe we could omit if not specific to role. But we need to preserve all substantive information. So we should include that somewhere. Perhaps under About the role we put that prose. Then Responsibilities: list of duties after "In the role of Data Scientist, we'll count on you to:" each sentence ends with period. We'll make each as

• . Then Qualifications: Could split into Required Qualifications and Preferred Qualifications. But we could combine under Qualifications heading with sub-sections? The instruction only allows headings from list; we could have Qualifications heading and then inside we can have

  for prose? But we need to list items; we can use

  • for any list of duties/requirements/benefits. So we can put Required Qualifications and Preferred Qualifications as separate
    under Qualifications heading, maybe with a

    indicating which is which? But we must not invent filler. We could have two headings: Requirements and Qualifications? The list includes Requirements and Qualifications as possible headings. We could use "Requirements" for required qualifications, and "Qualifications" for preferred? Or we could have "Requirements" heading for required qualifications, and "Preferred Qualifications" not in list but we could still use heading? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should stick to those headings; we can use any of those as appropriate. So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. We have schedule info. We need to decide what goes where. - About the role: prose about HDR and role. - Responsibilities: list of duties. - Requirements: maybe the "Required Qualifications" list. - Qualifications: maybe the "Preferred Qualifications" (Bachelor's degree) plus maybe other preferred? Actually only "Preferred Qualifications Bachelor's degree". That's minimal. - Skills: the proficiency statements (MS Office, data engineering tools, BI tools, data science languages, handling confidential info, writing and people skills, math and organizational skills, flexibility, communication skills, attitude commitment). Those could be under Skills. - Schedule: Full-time. We must not include sections with placeholder or vague content like "commensurate with experience". Not relevant. We must not include boilerplate like EEO etc. We must not include duplicated lines. We must preserve all substantive information. Let's extract substantive content: Intro paragraph(s): "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? 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. 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." We could keep that as prose under About the role. Then responsibilities list: - Leverage AI, automation, and data analytics tools to improve project delivery, quality assurance, and operational efficiency. - Develop and maintain automated processes to validate project documentation, compliance requirements, checklists, and project standards. - Design and implement dashboards, reports, and visualizations that provide project managers and leadership with actionable insights into project performance and resource utilization. - Analyze project data to identify trends, risks, cost impacts, schedule concerns, and opportunities for process improvement. - Handle highly sensitive and confidential information with professionalism and discretion - Collaborate with stakeholders to improve business decisions by identifying patterns and trends in data Note: The last bullet missing period but okay. Then Preferred Qualifications: "Bachelor's degree" Then Required Qualifications list (looks like each line is a qualification): - A degree in a closely related field or combination of education and relevant experience - Self-motivated, detail-oriented professional, ability to multitask a must - Proficiency with MS Office including Word and Outlook - Proficiency with data engineering tools and languages such as SQL, Power Query, and Pandas - Proficiency with business intelligence tools such as Power BI, Tableau, Plotly, Seaborn, and Matplotlib - Proficiency with data science languages such as Python and R - Ability to handle confidential information - Excellent writing and people skills - Strong math and organizational skills - Flexibility and ability to prioritize and handle multiple tasks and various managers in a fast-paced environment - Excellent verbal and written communication skills including grammar, punctuation, proofreading, spelling and telephone skills - An attitude and commitment to being an active participant of our employee-owned culture is a must We need to ensure we don't duplicate: "Ability to handle confidential information" appears also in responsibilities? Actually responsibilities includes "Handle highly sensitive and confidential information with professionalism and discretion". That's similar but not duplicate exactly; we keep both. Now Skills: Many of the required qualifications are actually skills. But we have separate Skills section maybe for the proficiency statements. However we already used Required Qualifications for those. Could we instead treat Required Qualifications as Requirements, and Skills as separate for the proficiency statements? But the required qualifications list includes many skill proficiencies. To avoid duplication, we need to decide where each piece goes. The instruction: "Use

    • for any list of duties/requirements/benefits". So we can have multiple lists. We could put the required qualifications list under Requirements heading. Then we could put the "Proficiency with MS Office..." etc under Skills heading. But that would split the same content across two sections, which may be okay but could be considered duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid splitting across sections as long as we keep all info. However we should avoid redundancy; but it's not prohibited to list same item in two places? Might be considered duplication but not explicitly forbidden. Safer to keep each piece only once. Thus we need to categorize: Responsibilities list (duties). Then we have qualifications (both preferred and required). Then we have skills (maybe overlapping). But we could treat the required qualifications as a mix of education/experience and skills. Could we put all under Requirements? Then we wouldn't need a separate Skills section. But we have a Skills heading in the list of possible headings; we could omit Skills if we don't have distinct skill content beyond what's already in Requirements. However the posting includes "Proficiency with MS Office including Word and Outlook", "Proficiency with data engineering tools and languages such as SQL, Power Query, and Pandas", etc. Those are skills. If we put them under Requirements, that's fine because Requirements can include skill requirements. The heading "Requirements" is appropriate for required qualifications. Then we could have a separate "Qualifications" heading for preferred qualifications (Bachelor's degree). That seems reasonable. Thus sections: - About the role (prose) - Responsibilities (ul) - Requirements (ul) for required qualifications - Qualifications (ul) for preferred qualifications (Bachelor's degree) - Schedule (p) for Full-time We might also include Industry? Not a heading; we could fold into a short p under About the role or separate? The instruction says fold minor metadata into a short p or drop it. So we could add a p with "Industry: Water; Business Class: Water Treatment; Job Posting: Sep 1, 2026." But that's minor metadata; we can include as a short p after About the role maybe. We must not include Pay/Benefits sections because not stated. We must not include repeated lines. Now produce HTML. Structure:

      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? 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