Senior Water Engineer / Project Manager
for section headings.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which content goes into which section.
Potential sections:
- About the role: maybe introductory paragraph about SEH and role overview.
- Responsibilities: list of duties.
- Requirements: essential qualifications (Bachelor's degree, PE registration, significant experience).
- Qualifications: preferred qualifications (15 years experience, etc). Could be separate "Qualifications" heading (maybe includes both essential and preferred? But we have both Requirements and Qualifications headings available. We can put essential under Requirements, preferred under Qualifications.
- Skills: maybe not needed; we could omit if no specific skill list.
- Benefits: list of benefits.
- Pay: salary range.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual pay range.
Now format.
We need to avoid repeating job title as heading. So no heading for Senior Water Engineer / Project Manager.
We need to include the intro text maybe as
under About the role.
Let's craft.
Section About the role: Could include the first paragraph about culture and invitation, plus maybe the "You belong at SEH" line.
We'll combine:
Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together, we are Building a Better World for All of Us®. You belong at SEH. SEH is currently searching for a Senior Water Engineer / Project Manager to join our talented Water/Wastewater team.
Note: fix typo "currenting" to "currently". We must preserve substantive information; we can correct obvious typo? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Changing a typo might be considered altering text. However "currenting" is clearly a typo; but we might keep as is? The instruction says preserve ALL substantive information; does fixing a typo count as inventing? It's not substantive; it's a minor error. Safer to keep original text? It says "preserve ALL substantive information". The typo is not substantive; but altering it could be considered inventing? I'd keep as is to be safe. However the phrase "SEH is currenting searching" is obviously wrong; but we could keep it. I'd keep original.
Thus: "SEH is currenting searching for a Senior Water Engineer / Project Manager to join our talented Water/Wastewater team!"
Now Responsibilities: We'll list bullet points.
From text:
- Lead critical water infrastructure projects, including treatment, pumping, conveyance, storage, and distribution systems throughout the state of Minnesota and beyond.
- Lead multidisciplinary teams to develop practical, cost-effective solutions.
- Manage project scope, schedule, budget, and quality.
- Foster strong client relationships.
- Support business development efforts.
- Mentor emerging professionals.
- Provide overall leadership for the planning, design, and delivery of water infrastructure projects, including treatment, pumping, conveyance, storage, and distribution systems.
- Serve as a senior client partner, maintaining long-term relationships and supporting clients from project planning through delivery and beyond.
- Lead and mentor a multidisciplinary team of engineers and designers, setting technical direction and fostering a high-performing, collaborative culture.
- Guide the development of creative and resilient solutions to complex water challenges.
- Partner with cross-functional teams to identify and manage project risk, ensure quality, and drive consistent project outcomes.
- Support practice growth through proposal development, strategic pursuits, and expansion of client relationships and market presence.
We may have some duplicates; but we should preserve all substantive information, not remove duplicates unless they are duplicated lines (the instruction says remove duplicated lines). So we need to deduplicate identical lines. Let's see duplicates: "Lead critical water infrastructure projects..." vs "Provide overall leadership for the planning, design, and delivery of water infrastructure projects..." Not identical but similar. We'll keep both as they are distinct.
We need to remove duplicated lines exactly same. I don't see exact duplicates.
Now Requirements (Essential Qualifications):
- Bachelor’s degree in civil, environmental, or related engineering field
- Professional Engineer registration
- Significant experience leading the design and delivery of water and or wastewater treatment and conveyance projects
Now Qualifications (Preferred):
- Fifteen (15) years of experience leading market or regional growth strategies, with accountability for business development, client expansion, and delivery performance
- Demonstrated success overseeing complex, multidisciplinary project portfolios, balancing strategic vision with operational execution
- Ability to influence and collaborate at the executive level, partnering with internal leaders to shape investment priorities and long-term growth plans
- Prior experience in, or strong alignment with, an employee-owned organization, embracing shared accountability for growth, profitability, and legacy
Now Benefits: list from "Why You’ll Love SEH" section.
- Collaborate on amazing projects of varying size and complexity that positively impact communities
- Being 100% employee-owned means we all share in the company’s success
- Career development through continued education, licensure/certification, skills, and technical training
- Work arrangements that promote work/life balance
- Flexible holidays enable individuals to tailor their festivities
- Paid Family Leave provides time to care for loved ones, whether family by birth or family by choice
Also there were quotes earlier but those are testimonials; could be considered part of About the role or Benefits? They are substantive but not a list; we could include them as prose under About the role or maybe a separate section like "What employee-owners say". But we only allowed headings from list; we could put them under About the role as prose.
We have quotes:
"I was on vacation last week and had zero concerns that my colleagues would help out with anything that came into my inbox!" – GIS Analyst
"What company has a CEO who cares enough to seek out one-on-one conversations ranging from 'How are you?' to 'What do you think would help the company?' SEH, that's who. " – Civil Engineering Technician
"Having the feeling that my voice matters and believing that SEH truly cares about the employees is so satisfying!" – Sr Financial Analyst
"It feels good having colleagues and supervisors that provide support and resources for growth and learning!" – Civil Engineer
"This is the first company I've worked for with a true entrepreneurial spirit." – Sr Mechanical Engineer
We could include them as a or but we only have
for prose. We'll put them as
with the quotes.
Now Pay: salary range.
We need to output as
Base compensation is expected to be in the range of $140,000 and $180,000 based on skill set and experience.
Now we must not include Schedule section.
Now ensure we don't include any boilerplate like EEO, visa sponsorship, location restrictions, etc. Remove those.
Now produce HTML fragment.
Structure:
About the role
... intro ...
Quotes...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
Make sure no extra whitespace issues.
Now craft the About the role paragraph: combine the initial imaginative paragraph and the SEH line.
We'll keep exactly as in text: "Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together
for prose. We need to decide which content goes into which section. Potential sections: - About the role: maybe introductory paragraph about SEH and role overview. - Responsibilities: list of duties. - Requirements: essential qualifications (Bachelor's degree, PE registration, significant experience). - Qualifications: preferred qualifications (15 years experience, etc). Could be separate "Qualifications" heading (maybe includes both essential and preferred? But we have both Requirements and Qualifications headings available. We can put essential under Requirements, preferred under Qualifications. - Skills: maybe not needed; we could omit if no specific skill list. - Benefits: list of benefits. - Pay: salary range. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual pay range. Now format. We need to avoid repeating job title as heading. So no heading for Senior Water Engineer / Project Manager. We need to include the intro text maybe as
under About the role. Let's craft. Section About the role: Could include the first paragraph about culture and invitation, plus maybe the "You belong at SEH" line. We'll combine:
Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together, we are Building a Better World for All of Us®. You belong at SEH. SEH is currently searching for a Senior Water Engineer / Project Manager to join our talented Water/Wastewater team.
Note: fix typo "currenting" to "currently". We must preserve substantive information; we can correct obvious typo? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Changing a typo might be considered altering text. However "currenting" is clearly a typo; but we might keep as is? The instruction says preserve ALL substantive information; does fixing a typo count as inventing? It's not substantive; it's a minor error. Safer to keep original text? It says "preserve ALL substantive information". The typo is not substantive; but altering it could be considered inventing? I'd keep as is to be safe. However the phrase "SEH is currenting searching" is obviously wrong; but we could keep it. I'd keep original. Thus: "SEH is currenting searching for a Senior Water Engineer / Project Manager to join our talented Water/Wastewater team!" Now Responsibilities: We'll list bullet points. From text: - Lead critical water infrastructure projects, including treatment, pumping, conveyance, storage, and distribution systems throughout the state of Minnesota and beyond. - Lead multidisciplinary teams to develop practical, cost-effective solutions. - Manage project scope, schedule, budget, and quality. - Foster strong client relationships. - Support business development efforts. - Mentor emerging professionals. - Provide overall leadership for the planning, design, and delivery of water infrastructure projects, including treatment, pumping, conveyance, storage, and distribution systems. - Serve as a senior client partner, maintaining long-term relationships and supporting clients from project planning through delivery and beyond. - Lead and mentor a multidisciplinary team of engineers and designers, setting technical direction and fostering a high-performing, collaborative culture. - Guide the development of creative and resilient solutions to complex water challenges. - Partner with cross-functional teams to identify and manage project risk, ensure quality, and drive consistent project outcomes. - Support practice growth through proposal development, strategic pursuits, and expansion of client relationships and market presence. We may have some duplicates; but we should preserve all substantive information, not remove duplicates unless they are duplicated lines (the instruction says remove duplicated lines). So we need to deduplicate identical lines. Let's see duplicates: "Lead critical water infrastructure projects..." vs "Provide overall leadership for the planning, design, and delivery of water infrastructure projects..." Not identical but similar. We'll keep both as they are distinct. We need to remove duplicated lines exactly same. I don't see exact duplicates. Now Requirements (Essential Qualifications): - Bachelor’s degree in civil, environmental, or related engineering field - Professional Engineer registration - Significant experience leading the design and delivery of water and or wastewater treatment and conveyance projects Now Qualifications (Preferred): - Fifteen (15) years of experience leading market or regional growth strategies, with accountability for business development, client expansion, and delivery performance - Demonstrated success overseeing complex, multidisciplinary project portfolios, balancing strategic vision with operational execution - Ability to influence and collaborate at the executive level, partnering with internal leaders to shape investment priorities and long-term growth plans - Prior experience in, or strong alignment with, an employee-owned organization, embracing shared accountability for growth, profitability, and legacy Now Benefits: list from "Why You’ll Love SEH" section. - Collaborate on amazing projects of varying size and complexity that positively impact communities - Being 100% employee-owned means we all share in the company’s success - Career development through continued education, licensure/certification, skills, and technical training - Work arrangements that promote work/life balance - Flexible holidays enable individuals to tailor their festivities - Paid Family Leave provides time to care for loved ones, whether family by birth or family by choice Also there were quotes earlier but those are testimonials; could be considered part of About the role or Benefits? They are substantive but not a list; we could include them as prose under About the role or maybe a separate section like "What employee-owners say". But we only allowed headings from list; we could put them under About the role as prose. We have quotes: "I was on vacation last week and had zero concerns that my colleagues would help out with anything that came into my inbox!" – GIS Analyst "What company has a CEO who cares enough to seek out one-on-one conversations ranging from 'How are you?' to 'What do you think would help the company?' SEH, that's who. " – Civil Engineering Technician "Having the feeling that my voice matters and believing that SEH truly cares about the employees is so satisfying!" – Sr Financial Analyst "It feels good having colleagues and supervisors that provide support and resources for growth and learning!" – Civil Engineer "This is the first company I've worked for with a true entrepreneurial spirit." – Sr Mechanical Engineer We could include them as a orbut we only have
for prose. We'll put them as
with the quotes. Now Pay: salary range. We need to output as
Base compensation is expected to be in the range of $140,000 and $180,000 based on skill set and experience.
Now we must not include Schedule section. Now ensure we don't include any boilerplate like EEO, visa sponsorship, location restrictions, etc. Remove those. Now produce HTML fragment. Structure:About the role
... intro ...
Quotes...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
Make sure no extra whitespace issues. Now craft the About the role paragraph: combine the initial imaginative paragraph and the SEH line. We'll keep exactly as in text: "Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together