Senior Water Resources / Senior Dam Engineer
CME Associates · Manchester, NH · 4 wk ago
HybridFull-time
We need to output HTML fragment with sections only if real content. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Content:
Intro paragraph: "Creativity. Innovation. A desire to effect positive change. That’s what it takes to work at Fuss & O’Neill – because that’s what we do for the communities in which we work: we create, innovate, and design long-lasting improvements that improve quality of life. Quality of life is also important on the job, so we’ve prioritized work-life balance by offering flexible/remote work opportunities, part-time benefits, and generous PTO. We believe that each day is an opportunity to support one another, to support our clients, and to support our communities. If you feel the same, then you’ve found your future."
That's about the company, could be "About the role"? Actually "About the role" heading is for description of role. The intro is more about company culture. Could be placed under "About the role" or maybe we can have a heading "About the role" with that content.
Then: "We are seeking a Senior Water Resources / Senior Dam Engineer to join our growing Water Resources team. This is a newly created role driven by a significant and expanding portfolio of dam repair, dam removal, and climate-resiliency projects across New England. The successful candidate will play a key leadership role, overseeing complex projects from planning through design and permitting, while mentoring junior staff and supporting business development initiatives. This position is ideal for a licensed Professional Engineer with deep technical expertise in dam engineering and water resources, strong project management skills, and a passion for resilient, sustainable infrastructure solutions."
That's also about role.
Then "Key Responsibilities" list bullet points.
Then "Skills, Knowledge And Expertise" list bullet points.
Then "This is a hybrid role, offering the best of both worlds—collaborate in-office with a high-performing team and enjoy the flexibility of working remotely part of the week. We're committed to supporting work-life balance while maintaining strong team connection and project delivery."
Then "Why You’ll Love Working with Us" list bullet points: Schedule Flexibility, Health & Wellness, Continuous Learning, Paid Time Off, Career Advancement, Fun Team Culture.
Then "The base salary range for this role is indicated in the posting. This range reflects the company’s good faith estimate of the compensation for this position at the time of posting. Final compensation will be determined based on factors such as experience, skills, qualifications, internal equity, and geographic location."
Thus we have Pay info: base salary range indicated but not given explicitly. The posting says "The base salary range for this role is indicated in the posting." but we don't have actual numbers. Since we cannot invent or summarize away detail, and we must not create Pay section unless posting actually states them. It says the range is indicated in the posting, but we don't have the numbers. The text does not give actual numbers. So we cannot include Pay section because we don't have specific numbers. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Since we don't have actual numbers, we should not create Pay section.
Schedule: The posting mentions hybrid role, flexible/remote work opportunities, part-time benefits, generous PTO, schedule flexibility. There's a "Schedule Flexibility" bullet under Why You’ll Love Working with Us. Also earlier: "flexible/remote work opportunities". So we have schedule info. We could create a Schedule section with that content. However we also have a Benefits section that includes health benefits, PTO, etc. The "Why You’ll Love Working with Us" includes Schedule Flexibility, Health & Wellness, Continuous Learning, Paid Time Off, Career Advancement, Fun Team Culture. Those could be split into Benefits and maybe other sections. But we need to follow headings: Benefits, Pay, Schedule. We can put schedule info under Schedule heading. Benefits under Benefits heading. Pay we omit.
We need to ensure we don't duplicate content. Let's extract schedule-specific content: "flexible/remote work opportunities", "Schedule Flexibility: Customize your work schedule to fit your life." Also "hybrid role, offering the best of both worlds—collaborate in-office with a high-performing team and enjoy the flexibility of working remotely part of the week." So schedule content.
Benefits: "part-time benefits", "generous PTO", "Comprehensive health benefits", "Paid Time Off", maybe also "part-time benefits" (though that's ambiguous). Also "continuous learning", "career advancement", "fun team culture" could be considered benefits but maybe better as separate sections? The instruction: Prefer a few substantive sections over many thin ones. So we could combine those under Benefits. But we also have a separate "Skills, Knowledge And Expertise" heading which maps to Skills or Requirements. The posting has "Skills, Knowledge And Expertise". That could be under Skills heading. Also there is "Requirements" maybe we can combine with Skills? The posting includes bullet list under "Skills, Knowledge And Expertise" which includes Bachelor's degree, PE license, 10+ years experience, etc. Those are requirements/qualifications. So we can put them under Requirements or Qualifications. The headings list includes Requirements, Qualifications, Skills. We need to decide which to use. Since the content includes both requirements (education, license, experience) and skills (knowledge of dam safety, modeling software, CAD, project management, communication, mentoring). Could split: Requirements heading for education, license, experience; Skills heading for technical skills. But we have to avoid many thin sections. Perhaps combine into one "Requirements" section that includes both education/experience and skills. However the instruction says use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to use only those that have real content. We have About the role (company intro + role description). Responsibilities (list). Requirements (education, license, experience). Qualifications maybe similar to Requirements; we could skip Qualifications if we already used Requirements. Skills (technical proficiencies). Benefits (health, PTO, learning, advancement, culture). Schedule (flexible/remote, hybrid). Pay we omit.
We must not repeat job title as heading. Good.
We must not include boilerplate like EEO, visa sponsorship, background check, e-Verify, etc. Remove those lines.
Now we need to preserve all substantive information. Let's extract each piece.
About the role: combine intro paragraph and the paragraph about seeking Senior Water Resources / Senior Dam Engineer, newly created role, etc. Also maybe include the sentence about ideal candidate? That could be part of About the role or Requirements. Let's put it in About the role.
Responsibilities: list bullet points under Key Responsibilities.
Requirements: Bachelor’s degree in civil engineering or related discipline; Professional Engineer (PE) license; 10+ years of experience in water resources and dam engineering.
Qualifications: maybe we could include "Strong knowledge of dam safety regulations, codes, and industry standards; Experience leading dam repair and removal design efforts; Proven ability to prepare high-quality technical reports and permit applications; Proficiency with hydrologic and hydraulic modeling software; Working knowledge of CAD-based design tools; Strong project management, communication, and mentoring skills; Ability to travel up to 10–15% throughout New England". Those could be under Qualifications or Skills. Since we have Skills heading separate, we could put the technical proficiencies under Skills, and the experience/knowledge under Qualifications. But we need to avoid thin sections. Let's think: Qualifications could be the knowledge/experience items; Skills could be software/tools and soft skills. However the posting lumps them under "Skills, Knowledge And Expertise". Might be better to put all under Skills heading. But we have both Requirements and Skills headings available. We could use Requirements for education/license/experience, and Skills for the rest (knowledge, software, soft skills, travel). That seems reasonable.
Thus:
Requirements:
- Bachelor’s degree in civil engineering or related discipline
- Professional Engineer (PE) license
- 10+ years of experience in water resources and dam engineering
Skills:
- Strong knowledge of dam safety regulations, codes, and industry standards
- Experience leading dam repair and removal design efforts
- Proven ability to prepare high-quality technical reports and permit applications
- Proficiency with hydrologic and hydraulic modeling software
- Working knowledge of CAD-based design tools
- Strong project management, communication, and mentoring skills
- Ability to travel up to 10–15% throughout New England
Benefits:
- Flexible/remote work opportunities (part-time benefits mentioned)
- Generous PTO
- Comprehensive health benefits
- Access to online courses, conferences, and learning materials
- Clear paths for promotions and opportunity to take on new challenges
- Regular team-building activities, happy hours, and company outings
Schedule:
- Hybrid role: collaborate in-office with a high-performing team and enjoy flexibility of working remotely part of the week
- Schedule flexibility: customize your work schedule to fit your life
We need to ensure we didn't miss any substantive info: The posting also mentions "part-time benefits" under work-life balance. We included flexible/remote work opportunities and part-time benefits maybe under Benefits. Also "generous PTO" we have. Also "We believe that each day is an opportunity to support one another, to support our clients, and to support our communities." That's part of About the role.
Also "We are seeking a Senior Water Resources / Senior Dam Engineer to join our growing Water Resources team." Already in About.
Also "This is a newly created role driven by a significant and expanding portfolio of dam repair, dam removal, and climate-resiliency projects across New England." In About.
Also "The successful candidate will play a key leadership role, overseeing complex projects from planning through design and permitting, while mentoring junior staff and supporting business development initiatives." In About.
Also "This position is ideal for a licensed Professional Engineer with deep technical expertise in dam engineering and water resources, strong project management skills, and a passion for resilient, sustainable infrastructure solutions." Could be in About or Requirements. We already have PE license in Requirements; deep technical expertise maybe covered in Skills. Passion for resilient sustainable infrastructure maybe not captured; could be added to About.
We should preserve that sentence. Let's incorporate into About.
Now check for any other info: "Coordinate and support local, state, and federal permitting and grant applications" under Responsibilities. Already captured.
"Apply hydrologic and hydraulic modeling to support design and regulatory submissions" captured.
"Collaborate with clients, regulators, and internal multidisciplinary teams across New England" captured.
"Support business development efforts, including funding strategy development and proposals" captured.
"Mentor and provide technical oversight to junior and mid-level engineers" captured.
Now ensure we didn't include boilerplate: lines about Visa sponsorship NOT available, background check, Affirmative Action/Equal Opportunity, e-Verify. Remove.
Now produce HTML fragment.
Structure:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Content:
Intro paragraph: "Creativity. Innovation. A desire to effect positive change. That’s what it takes to work at Fuss & O’Neill – because that’s what we do for the communities in which we work: we create, innovate, and design long-lasting improvements that improve quality of life. Quality of life is also important on the job, so we’ve prioritized work-life balance by offering flexible/remote work opportunities, part-time benefits, and generous PTO. We believe that each day is an opportunity to support one another, to support our clients, and to support our communities. If you feel the same, then you’ve found your future."
That's about the company, could be "About the role"? Actually "About the role" heading is for description of role. The intro is more about company culture. Could be placed under "About the role" or maybe we can have a heading "About the role" with that content.
Then: "We are seeking a Senior Water Resources / Senior Dam Engineer to join our growing Water Resources team. This is a newly created role driven by a significant and expanding portfolio of dam repair, dam removal, and climate-resiliency projects across New England. The successful candidate will play a key leadership role, overseeing complex projects from planning through design and permitting, while mentoring junior staff and supporting business development initiatives. This position is ideal for a licensed Professional Engineer with deep technical expertise in dam engineering and water resources, strong project management skills, and a passion for resilient, sustainable infrastructure solutions."
That's also about role.
Then "Key Responsibilities" list bullet points.
Then "Skills, Knowledge And Expertise" list bullet points.
Then "This is a hybrid role, offering the best of both worlds—collaborate in-office with a high-performing team and enjoy the flexibility of working remotely part of the week. We're committed to supporting work-life balance while maintaining strong team connection and project delivery."
Then "Why You’ll Love Working with Us" list bullet points: Schedule Flexibility, Health & Wellness, Continuous Learning, Paid Time Off, Career Advancement, Fun Team Culture.
Then "The base salary range for this role is indicated in the posting. This range reflects the company’s good faith estimate of the compensation for this position at the time of posting. Final compensation will be determined based on factors such as experience, skills, qualifications, internal equity, and geographic location."
Thus we have Pay info: base salary range indicated but not given explicitly. The posting says "The base salary range for this role is indicated in the posting." but we don't have actual numbers. Since we cannot invent or summarize away detail, and we must not create Pay section unless posting actually states them. It says the range is indicated in the posting, but we don't have the numbers. The text does not give actual numbers. So we cannot include Pay section because we don't have specific numbers. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Since we don't have actual numbers, we should not create Pay section.
Schedule: The posting mentions hybrid role, flexible/remote work opportunities, part-time benefits, generous PTO, schedule flexibility. There's a "Schedule Flexibility" bullet under Why You’ll Love Working with Us. Also earlier: "flexible/remote work opportunities". So we have schedule info. We could create a Schedule section with that content. However we also have a Benefits section that includes health benefits, PTO, etc. The "Why You’ll Love Working with Us" includes Schedule Flexibility, Health & Wellness, Continuous Learning, Paid Time Off, Career Advancement, Fun Team Culture. Those could be split into Benefits and maybe other sections. But we need to follow headings: Benefits, Pay, Schedule. We can put schedule info under Schedule heading. Benefits under Benefits heading. Pay we omit.
We need to ensure we don't duplicate content. Let's extract schedule-specific content: "flexible/remote work opportunities", "Schedule Flexibility: Customize your work schedule to fit your life." Also "hybrid role, offering the best of both worlds—collaborate in-office with a high-performing team and enjoy the flexibility of working remotely part of the week." So schedule content.
Benefits: "part-time benefits", "generous PTO", "Comprehensive health benefits", "Paid Time Off", maybe also "part-time benefits" (though that's ambiguous). Also "continuous learning", "career advancement", "fun team culture" could be considered benefits but maybe better as separate sections? The instruction: Prefer a few substantive sections over many thin ones. So we could combine those under Benefits. But we also have a separate "Skills, Knowledge And Expertise" heading which maps to Skills or Requirements. The posting has "Skills, Knowledge And Expertise". That could be under Skills heading. Also there is "Requirements" maybe we can combine with Skills? The posting includes bullet list under "Skills, Knowledge And Expertise" which includes Bachelor's degree, PE license, 10+ years experience, etc. Those are requirements/qualifications. So we can put them under Requirements or Qualifications. The headings list includes Requirements, Qualifications, Skills. We need to decide which to use. Since the content includes both requirements (education, license, experience) and skills (knowledge of dam safety, modeling software, CAD, project management, communication, mentoring). Could split: Requirements heading for education, license, experience; Skills heading for technical skills. But we have to avoid many thin sections. Perhaps combine into one "Requirements" section that includes both education/experience and skills. However the instruction says use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to use only those that have real content. We have About the role (company intro + role description). Responsibilities (list). Requirements (education, license, experience). Qualifications maybe similar to Requirements; we could skip Qualifications if we already used Requirements. Skills (technical proficiencies). Benefits (health, PTO, learning, advancement, culture). Schedule (flexible/remote, hybrid). Pay we omit.
We must not repeat job title as heading. Good.
We must not include boilerplate like EEO, visa sponsorship, background check, e-Verify, etc. Remove those lines.
Now we need to preserve all substantive information. Let's extract each piece.
About the role: combine intro paragraph and the paragraph about seeking Senior Water Resources / Senior Dam Engineer, newly created role, etc. Also maybe include the sentence about ideal candidate? That could be part of About the role or Requirements. Let's put it in About the role.
Responsibilities: list bullet points under Key Responsibilities.
Requirements: Bachelor’s degree in civil engineering or related discipline; Professional Engineer (PE) license; 10+ years of experience in water resources and dam engineering.
Qualifications: maybe we could include "Strong knowledge of dam safety regulations, codes, and industry standards; Experience leading dam repair and removal design efforts; Proven ability to prepare high-quality technical reports and permit applications; Proficiency with hydrologic and hydraulic modeling software; Working knowledge of CAD-based design tools; Strong project management, communication, and mentoring skills; Ability to travel up to 10–15% throughout New England". Those could be under Qualifications or Skills. Since we have Skills heading separate, we could put the technical proficiencies under Skills, and the experience/knowledge under Qualifications. But we need to avoid thin sections. Let's think: Qualifications could be the knowledge/experience items; Skills could be software/tools and soft skills. However the posting lumps them under "Skills, Knowledge And Expertise". Might be better to put all under Skills heading. But we have both Requirements and Skills headings available. We could use Requirements for education/license/experience, and Skills for the rest (knowledge, software, soft skills, travel). That seems reasonable.
Thus:
Requirements:
- Bachelor’s degree in civil engineering or related discipline
- Professional Engineer (PE) license
- 10+ years of experience in water resources and dam engineering
Skills:
- Strong knowledge of dam safety regulations, codes, and industry standards
- Experience leading dam repair and removal design efforts
- Proven ability to prepare high-quality technical reports and permit applications
- Proficiency with hydrologic and hydraulic modeling software
- Working knowledge of CAD-based design tools
- Strong project management, communication, and mentoring skills
- Ability to travel up to 10–15% throughout New England
Benefits:
- Flexible/remote work opportunities (part-time benefits mentioned)
- Generous PTO
- Comprehensive health benefits
- Access to online courses, conferences, and learning materials
- Clear paths for promotions and opportunity to take on new challenges
- Regular team-building activities, happy hours, and company outings
Schedule:
- Hybrid role: collaborate in-office with a high-performing team and enjoy flexibility of working remotely part of the week
- Schedule flexibility: customize your work schedule to fit your life
We need to ensure we didn't miss any substantive info: The posting also mentions "part-time benefits" under work-life balance. We included flexible/remote work opportunities and part-time benefits maybe under Benefits. Also "generous PTO" we have. Also "We believe that each day is an opportunity to support one another, to support our clients, and to support our communities." That's part of About the role.
Also "We are seeking a Senior Water Resources / Senior Dam Engineer to join our growing Water Resources team." Already in About.
Also "This is a newly created role driven by a significant and expanding portfolio of dam repair, dam removal, and climate-resiliency projects across New England." In About.
Also "The successful candidate will play a key leadership role, overseeing complex projects from planning through design and permitting, while mentoring junior staff and supporting business development initiatives." In About.
Also "This position is ideal for a licensed Professional Engineer with deep technical expertise in dam engineering and water resources, strong project management skills, and a passion for resilient, sustainable infrastructure solutions." Could be in About or Requirements. We already have PE license in Requirements; deep technical expertise maybe covered in Skills. Passion for resilient sustainable infrastructure maybe not captured; could be added to About.
We should preserve that sentence. Let's incorporate into About.
Now check for any other info: "Coordinate and support local, state, and federal permitting and grant applications" under Responsibilities. Already captured.
"Apply hydrologic and hydraulic modeling to support design and regulatory submissions" captured.
"Collaborate with clients, regulators, and internal multidisciplinary teams across New England" captured.
"Support business development efforts, including funding strategy development and proposals" captured.
"Mentor and provide technical oversight to junior and mid-level engineers" captured.
Now ensure we didn't include boilerplate: lines about Visa sponsorship NOT available, background check, Affirmative Action/Equal Opportunity, e-Verify. Remove.
Now produce HTML fragment.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Schedule
- ... ...
Creativity, innovation, and a desire to effect positive change are what it takes to work at Fuss & O’Neill, because that’s what we do for the communities in which we work: we create, innovate