Water / Wastewater Engineering Internship
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role, Responsibilities, Requirements (maybe Required Qualifications), Skills (Preferred Qualifications), Benefits.
We need to avoid repeating job title as heading (not needed). No Job ID.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus:
About the role
Hazen is seeking Fall 2026, Spring 2027 and Summer 2027 interns for a variety of water-related assignments in our Saratoga Springs office. The successful candidate will be involved in a wide range of drinking water, wastewater, stormwater, and/or conveyance projects. This opportunity includes working within one (or more) of Hazen's discipline groups, which include: CAD/BIM, civil, electrical, HVAC/plumbing/fire protection, instrumentation and controls, process mechanical, structural, or architectural. Responsibilities include integrating with design teams from initial studies and conceptual design through construction of pipelines, pump stations, and/or treatment facilities and attending field investigations and site visits.
Maybe also include the "Why Hazen And Sawyer" paragraph as part of About the role? It's about company, but could be considered part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). It didn't forbid including company description. I'd include it as part of About the role to preserve all substantive info. So after the first paragraph, we can add another with the company description.
Thus:
Founded in 1951 by the son of Allen Hazen (developer of the Hazen-Williams equation), we are an employee-owned company with a singular focus on "all things water." Our work includes planning, design, and oversight of construction of environmental infrastructure – for water, wastewater, and stormwater management. We foster a work environment low on bureaucracy and high in creativity. We recruit talented professionals, provide them with challenging, interesting, and creative assignments, and furnish them with the tools they need to succeed. We currently have over 2,000 employees in 70+ offices throughout the United States, Latin America, Canada, and the UK.
Now Responsibilities: we have bullet list.
We need to capture all responsibilities from both the earlier generic responsibilities and the Key Responsibilities list.
Let's combine:
- Integrating with design teams from initial studies and conceptual design through construction of pipelines, pump stations, and/or treatment facilities
- Attending field investigations and site visits
- Participate in fieldwork, site visits (mostly in-state) and potential client meetings; capable of walking around outdoors in xxx environments-may want to provide any physical specific requirements (this is weird placeholder "xxx environments". It's part of the posting; we must preserve it exactly? It says "capable of walking around outdoors in xxx environments-may want to provide any physical specific requirements". That's weird but we must preserve it. It's not a placeholder like "varies"? It's "xxx environments". Might be a placeholder but it's in the text. We should keep it as is.
- Assist in preparing engineering deliverables, including sampling studies, condition assessments, process modeling, hydraulics, and design reports
- Work directly with experienced engineering team providing mentoring opportunities to learn and develop
- Manage data for process modeling and design
- Coordinate with manufacturers and vendors to select equipment
- Support multiple projects from planning through construction
- Add responsibilities as required by the specific position
We need to output as - items.
Now Requirements: Required Qualifications.
List:
- Currently enrolled in an ABET-accredited Bachelor’s/Master’s degree in environmental, civil, chemical, or mechanical engineering (can add specific discipline to the role i.e. construction management, electrical, applied science)
- Strong written & verbal communication skills
- Self-motivated
- Strong organizational skills with attention to detail
- Ability to work independently and in group settings
- Must be proficient in Microsoft Office Suite
Now Skills: Preferred Qualifications.
List:
- Skilled in AutoCAD, Bluebeam, Civil 3D, GIS
- Strong interest in the water/wastewater industry
- Prior experience in the water/wastewater industry
- Advanced degree (Master’s or Doctorate) in environmental, civil, chemical, or mechanical engineering
Now Benefits: What We Offer.
List:
- Starting pay range for this position depends on skills, experience, education and geographical location (but we decided not to include Pay section; but this is part of What We Offer. However we might still include it in Benefits? The rule says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state starting pay range depends on... That's a statement about pay, but it's vague. However it's part of What We Offer. If we omit Pay section, we might still include this sentence in Benefits? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't say we cannot include pay info inside Benefits. But it's ambiguous. Safer to include the pay statement in Benefits section as a bullet? However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (starting pay range depends...). So we could create a Benefits section and include that bullet. But the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "depends on skills, experience, education and geographical location" is similar to "varies". It's not a specific range. Might be considered filler. But it's not exactly "varies". It's a description that it depends on factors. I'd lean to not include it as a separate Pay section, but could include it in Benefits as a bullet? The rule about filler applies to headings followed by filler text. If we put it under Benefits heading, it's not a heading followed by filler; it's a bullet under Benefits. That might be okay. However the bullet itself is vague. The rule didn't forbid vague bullets, only headings with filler. So we can include it.
Thus Benefits bullets:
- Professional guidance and career counseling
- Direct mentorship with experienced engineers
- Experience with a variety of disciplines within the water industry
- Exposure to the environmental consulting industry
- Potential opportunity for full-time employment upon graduation
- Starting pay range for this position depends on skills, experience, education and geographical location
Now we need to ensure we don't repeat any info.
Now output HTML fragment.
We must not include
for prose. Thus:
About the role
Hazen is seeking Fall 2026, Spring 2027 and Summer 2027 interns for a variety of water-related assignments in our Saratoga Springs office. The successful candidate will be involved in a wide range of drinking water, wastewater, stormwater, and/or conveyance projects. This opportunity includes working within one (or more) of Hazen's discipline groups, which include: CAD/BIM, civil, electrical, HVAC/plumbing/fire protection, instrumentation and controls, process mechanical, structural, or architectural. Responsibilities include integrating with design teams from initial studies and conceptual design through construction of pipelines, pump stations, and/or treatment facilities and attending field investigations and site visits.
Maybe also include the "Why Hazen And Sawyer" paragraph as part of About the role? It's about company, but could be considered part of About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). It didn't forbid including company description. I'd include it as part of About the role to preserve all substantive info. So after the first paragraph, we can add anotherwith the company description. Thus:
Founded in 1951 by the son of Allen Hazen (developer of the Hazen-Williams equation), we are an employee-owned company with a singular focus on "all things water." Our work includes planning, design, and oversight of construction of environmental infrastructure – for water, wastewater, and stormwater management. We foster a work environment low on bureaucracy and high in creativity. We recruit talented professionals, provide them with challenging, interesting, and creative assignments, and furnish them with the tools they need to succeed. We currently have over 2,000 employees in 70+ offices throughout the United States, Latin America, Canada, and the UK.
Now Responsibilities: we have bullet list. We need to capture all responsibilities from both the earlier generic responsibilities and the Key Responsibilities list. Let's combine: - Integrating with design teams from initial studies and conceptual design through construction of pipelines, pump stations, and/or treatment facilities - Attending field investigations and site visits - Participate in fieldwork, site visits (mostly in-state) and potential client meetings; capable of walking around outdoors in xxx environments-may want to provide any physical specific requirements (this is weird placeholder "xxx environments". It's part of the posting; we must preserve it exactly? It says "capable of walking around outdoors in xxx environments-may want to provide any physical specific requirements". That's weird but we must preserve it. It's not a placeholder like "varies"? It's "xxx environments". Might be a placeholder but it's in the text. We should keep it as is. - Assist in preparing engineering deliverables, including sampling studies, condition assessments, process modeling, hydraulics, and design reports - Work directly with experienced engineering team providing mentoring opportunities to learn and develop - Manage data for process modeling and design - Coordinate with manufacturers and vendors to select equipment - Support multiple projects from planning through construction - Add responsibilities as required by the specific position We need to output as- items. Now Requirements: Required Qualifications. List: - Currently enrolled in an ABET-accredited Bachelor’s/Master’s degree in environmental, civil, chemical, or mechanical engineering (can add specific discipline to the role i.e. construction management, electrical, applied science) - Strong written & verbal communication skills - Self-motivated - Strong organizational skills with attention to detail - Ability to work independently and in group settings - Must be proficient in Microsoft Office Suite Now Skills: Preferred Qualifications. List: - Skilled in AutoCAD, Bluebeam, Civil 3D, GIS - Strong interest in the water/wastewater industry - Prior experience in the water/wastewater industry - Advanced degree (Master’s or Doctorate) in environmental, civil, chemical, or mechanical engineering Now Benefits: What We Offer. List: - Starting pay range for this position depends on skills, experience, education and geographical location (but we decided not to include Pay section; but this is part of What We Offer. However we might still include it in Benefits? The rule says do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state starting pay range depends on... That's a statement about pay, but it's vague. However it's part of What We Offer. If we omit Pay section, we might still include this sentence in Benefits? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't say we cannot include pay info inside Benefits. But it's ambiguous. Safer to include the pay statement in Benefits section as a bullet? However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (starting pay range depends...). So we could create a Benefits section and include that bullet. But the rule also says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "depends on skills, experience, education and geographical location" is similar to "varies". It's not a specific range. Might be considered filler. But it's not exactly "varies". It's a description that it depends on factors. I'd lean to not include it as a separate Pay section, but could include it in Benefits as a bullet? The rule about filler applies to headings followed by filler text. If we put it under Benefits heading, it's not a heading followed by filler; it's a bullet under Benefits. That might be okay. However the bullet itself is vague. The rule didn't forbid vague bullets, only headings with filler. So we can include it. Thus Benefits bullets: - Professional guidance and career counseling - Direct mentorship with experienced engineers - Experience with a variety of disciplines within the water industry - Exposure to the environmental consulting industry - Potential opportunity for full-time employment upon graduation - Starting pay range for this position depends on skills, experience, education and geographical location Now we need to ensure we don't repeat any info. Now output HTML fragment. We must not include