Hydrologist Project Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions (the link and note to third-party recruiters). Also remove overview? Overview is about company; maybe we can include as About the role? The posting includes "Overview: At Weston & Sampson..." That's about company; we could put under About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (maybe summarizing the role description). Must not invent or summarize away detail; preserve all substantive info. So we need to extract details: The role description: "Weston & Sampson is currently seeking a Hydrologic & Hydraulic Project Manager with 5-10 years of experience in our Water Discipline out of any our New England-based office locations. The position will generally focus on projects that involve hydrologic and hydraulic modeling and design in support of a range of stream restoration, bank stabilization, dam rehabilitation, bridge and culvert replacement, climate resilience planning, and flood mitigation projects in complex environments and integrating coastal, riverine, and piped infrastructure flooding environments." That's about the role. Then "What You'll Do:" list bullet points: Direct client communications..., Lead and coordinate..., Develop and maintain..., Support business development..., Supervise, mentor..., Lead project teams..., Typical projects include: ... (list). Those are responsibilities. Then "What You'll Bring:" list qualifications: BS..., MS..., 5-10 years experience..., Strong understanding..., Expertise..., Experience..., Experience..., Project management experience..., Strong experience..., Certified Floodplain Manager..., Proven leadership..., Excellent written..., Some travel..., Valid driver’s license required. Then Salary Range: $95,000 - $122,000 based on experience. Then Overview about company: maybe we can put under About the role or maybe a separate section like "About the company"? Not in allowed headings. Could incorporate into About the role? But About the role should be about role, not company. However we could treat Overview as About the role? Might be okay to include as About the role (since it's about the firm). But we must not invent content. We can include Overview as a paragraph under About the role? Might be okay. Benefits: The posting lists "We offer: Meaningful work..., Ownership mindset..., Growth opportunities..., Flexible workplace..., Strong culture:" That's benefits. So we can create Benefits section with those bullet points. Schedule: Not mentioned explicitly; only "Some travel to client meetings and project sites required." No schedule like full-time, part-time, remote. So we should not create Schedule section because no specific content. Pay: we have Salary Range. Thus sections: About the role (maybe combine role description and overview?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we need to avoid duplication: Requirements vs Qualifications vs Skills. The posting lumps many items; we need to decide how to split. Could treat Requirements as the mandatory items (BS required, 5-10 years experience, valid driver's license, some travel). Qualifications as preferred (MS preferred, CFM preferred). Skills as expertise items (hydrology/hydraulics principles, software expertise, floodplain analysis, stormwater design, transportation infrastructure evaluation, permitting requirements, project management, business development, proposal preparation, client management, leadership, communication, organizational, time-management). That seems reasonable. We must preserve all substantive info; not lose any. Let's extract each piece. Role description paragraph: "Weston & Sampson is currently seeking a Hydrologic & Hydraulic Project Manager with 5-10 years of experience in our Water Discipline out of any our New England-based office locations. The position will generally focus on projects that involve hydrologic and hydraulic modeling and design in support of a range of stream restoration, bank stabilization, dam rehabilitation, bridge and culvert replacement, climate resilience planning, and flood mitigation projects in complex environments and integrating coastal, riverine, and piped infrastructure flooding environments." Overview paragraph: "At Weston & Sampson, you’ll work alongside more than 1,000 employee-owners who are passionate about improving our communities. From providing clean water to designing resilient infrastructure and sustainable environments, our work has a direct impact on quality of life. We’re looking for curious, driven professionals who want to contribute to innovative, impactful projects and grow with a team that supports them. We are a 100% employee-owned, interdisciplinary firm offering design, engineering, and environmental services. Since our founding in 1899, we have worked to build a collaborative, forward-thinking environment grounded in respect for each other’s ideas." We could combine these under About the role? Might be okay but the overview is about company not role. However we have no other heading for company. Could we create a section "About the company"? Not allowed. The instruction says use those headings as examples; we could still add other headings? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add others if needed? Safer to stick to those. So we need to fit company overview somewhere; maybe under About the role we can include both role description and company overview as it's still about the role context. It's not inventing; it's preserving. Responsibilities: from "What You'll Do:" bullet points: - Direct client communications on technical design aspects, project schedule, budget, and scope. - Lead and coordinate project teams across multiple design disciplines. - Develop and maintain long-term relationships with clients, contributing to business development and project opportunities. - Support business development efforts, including marketing, proposal preparation, and client outreach. - Supervise, mentor, and train junior engineers and designers. - Lead project teams in the design and delivery of transportation or hydrology projects, ensuring all aspects are met including studies, modeling, and final design. - Typical projects include: * Hydrologic and hydraulic modeling for urban and rural infrastructure, including stormwater, drainage, and flood management. * Evaluating complex transportation networks and floodplain management in varied environments (e.g., urban, coastal, riverine). * Integrating climate resilience and sustainability planning into infrastructure projects. * Conducting site assessments, designing improvements, and leading technical studies to inform project development. We need to format as

• . The "Typical projects include:" could be a heading? But we can just include as a list item with sublist? Simpler: make each bullet as li; for the typical projects we could have a li with a sub-ul. But we can also just list them as separate li items preceded by a sentence. The instruction: Use
  • for any list of duties/requirements/benefits. So we can have a ul for responsibilities, each li being a duty. For the typical projects, we could embed a ul inside li. That's acceptable. Requirements: mandatory items: BS in Civil Engineering, Environmental Engineering, Hydrology, or a related field (required). 5-10 years of experience in transportation or hydrology project management. Valid driver’s license required. Some travel to client meetings and project sites required. (Also maybe "Strong understanding of hydrology and hydraulics principles and transportation infrastructure systems." That's more skill/experience; but could be requirement. However we already have skills. Let's treat as requirement? Might be ambiguous. We'll keep as requirement? But we have separate Skills section for expertise. Let's decide: Requirements: education, years experience, driver's license, travel. Also maybe "Project management experience, including scheduling, budgeting, and scope control." That's also a requirement. But we could put under Skills. Hmm. Qualifications: preferred items: MS in Civil Engineering, Environmental Engineering, Hydrology, or similar field (preferred). Certified Floodplain Manager (CFM) preferred. Skills: expertise items: Strong understanding of hydrology and hydraulics principles and transportation infrastructure systems. Expertise in using hydrologic (e.g., HEC-HMS, HydroCAD), hydraulic (e.g., HEC-RAS), and integrated modeling software (e.g., PCSWMM, ICM). Experience with floodplain analysis, stormwater design, and transportation infrastructure evaluation. Experience with the permitting requirements of instream projects in multiple states in the Northeast. Project management experience, including scheduling, budgeting, and scope control. Strong experience in business development, proposal preparation, and client management. Proven leadership and team management skills. Excellent written and verbal communication, organizational, and time-management skills. Benefits: list from "We offer:": - Meaningful work: Contribute to projects that protect and enhance the natural and built environments - Ownership mindset: As an employee-owner, your work directly contributes to our shared success - Growth opportunities: Build your career through mentorship, diverse projects, and clear advancement pathways - Flexible workplace: Work in a way that supports your life and not the other way around - Strong culture: Join a team that values collaboration, inclusion, and recognition Pay: Salary Range: $95,000 - $122,000 based on experience. Schedule: none. Now produce HTML fragment with

    headings and appropriate

    or

    . We must not include any extra text outside HTML. No markdown fences. Let's craft. Structure:

    About the role

    Weston & Sampson is currently seeking a Hydrologic & Hydraulic Project Manager with 5-10 years of experience in our Water Discipline out of any our New England-based office locations. The position will generally focus on projects that involve hydrologic and hydraulic modeling and design in support of a range of stream restoration, bank stabilization, dam rehabilitation, bridge and culvert replacement, climate resilience planning, and flood mitigation projects in complex environments and integrating coastal, riverine, and piped infrastructure flooding environments.

    At Weston & Sampson, you’ll work alongside more than 1,000 employee-owners who are passionate about improving our communities. From providing clean water to designing resilient infrastructure and sustainable environments, our work has a direct impact on quality of life. We’re looking for curious, driven professionals who want to contribute to innovative, impactful projects and grow with a team that supports them. We are a 100% employee-owned, interdisciplinary firm offering design, engineering, and environmental services. Since our founding in 1899, we have worked to build a collaborative, forward-thinking environment grounded in respect for each other’s ideas.

    Responsibilities

    • Direct client communications on technical design aspects, project schedule, budget, and scope.
    • Lead and coordinate project teams across multiple design disciplines.
    • Develop and maintain long-term relationships with clients, contributing to business development and project opportunities.
    • Support business development efforts, including marketing, proposal preparation, and client outreach.
    • Supervise, mentor, and train junior engineers and designers.
    • Lead project teams in the design and delivery of transportation or hydrology projects, ensuring all aspects are met including studies, modeling, and final design.
    • Typical projects include:
      • Hydrologic and hydraulic modeling for urban and rural infrastructure, including stormwater, drainage, and flood management.
      • Evaluating complex transportation networks and floodplain management in varied environments (e.g., urban, coastal, riverine).
      • Integrating climate resilience and sustainability planning into infrastructure projects.
      • Conducting site assessments, designing improvements, and leading technical studies to inform project development.

    Requirements

    • BS in Civil Engineering, Environmental Engineering, Hydrology, or a related field (required