Jobs · OTHR · Indiana

Water Resources Lead

Jobot · Indianapolis, IN · 1 mo ago
On-siteOTHR$125k–$165k/yrFull-time
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. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, navigation, etc. Must preserve all substantive info. Let's parse the posting. Content: - Lead the growth of an established Water Resources practice while helping deliver infrastructure projects that strengthen communities throughout Indiana. (role description) - This Jobot Job is hosted by: Alex Dickinson (metadata, maybe minor) - Salary: $125,000 - $165,000 per year (Pay) - A bit about us: Our client is a highly respected multidisciplinary engineering consulting firm with a reputation for delivering innovative infrastructure solutions throughout Indiana. Backed by decades of client relationships and an established presence in transportation and municipal engineering, the firm is making a strategic investment in growing its Water Resources practice. Rather than starting from scratch, you'll inherit existing client relationships, active contracts, and executive support to help expand water resources services throughout the region. This is an outstanding opportunity for a technical leader who enjoys mentoring engineers, strengthening client partnerships, and helping shape the future of a growing practice. (About the role / About us) - Why join us? (list of bullet points): - Lead the continued growth of an established Water Resources practice with full executive support - Build upon existing municipal and transportation relationships rather than creating a client base from the ground up - Collaborate with experienced transportation, bridge, and civil engineering professionals on multidisciplinary infrastructure projects - Join a collaborative consulting firm with exceptionally low turnover and a long-term, relationship-driven culture - Enjoy direct access to leadership with real opportunities to influence the direction of the business - Job Details: - Bachelor's degree in Civil Engineering - Professional Engineer (PE) license required - 10+ years of consulting engineering experience preferred - Strong background in drainage, stormwater management, water distribution, wastewater collection systems, lift stations, and municipal infrastructure - INDOT drainage and transportation experience highly preferred - Experience managing engineering projects from proposal through construction - Ability to develop and maintain client relationships while supporting business development initiatives - Interested in hearing more? Easy Apply now by clicking the "Easy Apply" button. (application instruction, remove) - Jobot is an Equal Opportunity Employer... (boilerplate, remove) - ... privacy policy etc (remove) - Want to learn more about this role and Jobot? Click our Jobot logo and follow our LinkedIn page! (remove) We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: could be the description "Lead the growth of an established Water Resources practice while helping deliver infrastructure projects that strengthen communities throughout Indiana." plus "A bit about us:" maybe qualifies as About the role. Could combine. - Responsibilities: maybe the "Why join us?" bullet points are more benefits? Actually those are reasons to join, not responsibilities. Responsibilities could be the job details bullet list: Bachelor's degree etc? Those are qualifications. Responsibilities might be: Lead growth, deliver infrastructure projects, mentor engineers, strengthen client partnerships, shape future of practice, manage engineering projects from proposal through construction, develop/maintain client relationships, support business development. We can extract from text. - Requirements: maybe the required qualifications: Bachelor's degree in Civil Engineering, PE license required, 10+ years consulting engineering experience preferred, strong background in drainage etc, INDOT experience highly preferred, experience managing engineering projects from proposal through construction, ability to develop/maintain client relationships while supporting business development initiatives. - Qualifications: maybe similar to requirements; but we can differentiate: Qualifications could be education and licensure; Requirements could be experience and skills. But we need to avoid duplication. The instruction: Use sections only when posting has real specific content. We can decide to have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Benefits and Schedule not present (no specifics). So we omit Benefits and Schedule. We need to include Pay section with salary range. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. We need to ensure we include all substantive info: The description about leading growth, delivering infrastructure projects, strengthening communities, etc. The "A bit about us:" paragraph. The "Why join us?" bullet points. The job details bullet list (education, PE license, experience, background, INDOT preference, managing projects, client relationships, business development). Also the salary. We also have "This Jobot Job is hosted by: Alex Dickinson" - maybe minor metadata; we can fold into a short

    or drop. Probably we can include as a short paragraph under About the role? But instruction: fold minor metadata into a short

    or drop it. We can include a short p: "Hosted by Alex Dickinson." Might be okay. We must not include boilerplate like EEO, privacy, etc. Now craft HTML. Structure:

    About the role

    Lead the growth of an established Water Resources practice while helping deliver infrastructure projects that strengthen communities throughout Indiana. Hosted by Alex Dickinson.

    A bit about us: Our client is a highly respected multidisciplinary engineering consulting firm with a reputation for delivering innovative infrastructure solutions throughout Indiana. Backed by decades of client relationships and an established presence in transportation and municipal engineering, the firm is making a strategic investment in growing its Water Resources practice. Rather than starting from scratch, you'll inherit existing client relationships, active contracts, and executive support to help expand water resources services throughout the region. This is an outstanding opportunity for a technical leader who enjoys mentoring engineers, strengthening client partnerships, and helping shape the future of a growing practice.

    Responsibilities

    • Lead the continued growth of an established Water Resources practice with full executive support
    • Build upon existing municipal and transportation relationships rather than creating a client base from the ground up
    • Collaborate with experienced transportation, bridge, and civil engineering professionals on multidisciplinary infrastructure projects
    • Enjoy direct access to leadership with real opportunities to influence the direction of the business
    • Manage engineering projects from proposal through construction
    • Develop and maintain client relationships while supporting business development initiatives
    But note some of these are from "Why join us?" which are more benefits but we can treat as responsibilities? Might be okay. However we also have responsibilities like leading growth, delivering infrastructure projects, mentoring engineers, strengthening client partnerships, shaping future of practice. The "Why join us?" list includes leading growth, building upon relationships, collaborating, low turnover culture, direct access to leadership. Those are more about the role/benefits. But we can still put them under Responsibilities as they describe what you'll do. Might be okay. Alternatively we could split: Responsibilities: lead growth, deliver infrastructure projects, mentor engineers, strengthen client partnerships, shape future, manage projects, develop client relationships, support business development. Qualifications: education, PE license, experience, background, INDOT preference. Skills: maybe strong background in drainage etc, ability to manage projects, client relationship skills. But we have limited time. We need to avoid duplication. Let's decide: - About the role: description + "A bit about us". - Responsibilities: list of duties: Lead growth, deliver infrastructure projects, mentor engineers, strengthen client partnerships, shape future of practice, manage engineering projects from proposal through construction, develop/maintain client relationships, support business development initiatives. We need to extract mentor engineers and strengthen client partnerships from "A bit about us": "This is an outstanding opportunity for a technical leader who enjoys mentoring engineers, strengthening client partnerships, and helping shape the future of a growing practice." So we can include those. Thus responsibilities list: - Lead the growth of an established Water Resources practice - Help deliver infrastructure projects that strengthen communities throughout Indiana - Mentor engineers - Strengthen client partnerships - Help shape the future of a growing practice - Manage engineering projects from proposal through construction - Develop and maintain client relationships while supporting business development initiatives Also maybe "Build upon existing municipal and transportation relationships rather than creating a client base from the ground up" could be a responsibility. - Collaborate with experienced transportation, bridge, and civil engineering professionals on multidisciplinary infrastructure projects - Enjoy direct access to leadership with real opportunities to influence the direction of the business (maybe more benefit). But we can include. We need to ensure we don't miss any substantive info. Now Requirements: maybe the required qualifications: Bachelor's degree in Civil Engineering, Professional Engineer (PE) license required, 10+ years of consulting engineering experience preferred, Strong background in drainage, stormwater management, water distribution, wastewater collection systems, lift stations, and municipal infrastructure, INDOT drainage and transportation experience highly preferred. Qualifications: maybe similar but we can separate: Qualifications: Bachelor's degree in Civil Engineering, PE license required. Requirements: 10+ years experience, strong background, INDOT preference, experience managing projects, ability to develop/maintain client relationships while supporting business development. Skills: maybe ability to develop/maintain client relationships, business development, project management, collaboration, mentoring. But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But we have to use headings only if there is real specific content. We could have sections: About the role, Responsibilities, Requirements (which includes education, licensure, experience, background, etc.), Pay. That might be enough. But we also have "Why join us?" bullet points which are more about benefits/culture; we could put them under Responsibilities or maybe a separate section "Benefits"? However Benefits section only if posting actually states them. The "Why join us?" bullet points are more about why join, could be considered benefits. But they are not explicit benefits like health insurance, etc. They are more about role advantages. Could be considered "Why join us" but not standard Benefits. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid having a Benefits section if there is content like "Join a collaborative consulting firm with exceptionally low turnover and a long-term, relationship-driven culture" etc. That is a benefit. So we could create a Benefits section with those bullet points. Thus we could have sections: - About the role (description + about us) - Responsibilities (core duties) - Requirements (education, licensure, experience, background, INDOT preference, project management, client relationship/business development) - Benefits (why join us points: lead growth with executive support, build upon existing relationships, collaborate with experienced professionals, low turnover culture, direct access to leadership) - Pay (salary range) We should not include Schedule (none). Now ensure we preserve all substantive info: Did we miss any? Let's list all substantive sentences from posting: 1. Lead the growth of an established Water Resources practice while helping deliver infrastructure projects that strengthen communities throughout Indiana. 2. This Jobot Job is hosted by: Alex Dickinson 3. Salary: $125,000 - $165,000 per year 4. A bit about us: Our client is a highly respected multidisciplinary engineering consulting firm with a reputation for delivering innovative infrastructure solutions throughout Indiana. Backed by decades of client relationships and an established presence in transportation and municipal engineering, the firm is making a strategic investment in growing its Water Resources practice. Rather than starting from scratch, you'll inherit existing client relationships, active contracts, and executive support to help expand water resources services throughout the region. This is an outstanding opportunity for a technical leader who enjoys mentoring engineers, strengthening client partnerships, and helping shape the future of a growing practice. 5. Why join us? - Lead the continued growth of an established Water Resources practice with full executive support - Build upon existing municipal and transportation relationships rather

Similar jobs

Water Resources Lead

HorrocksMeridian, ID· 2 wk ago
$140k–$170k/yrapply on trilongroup.pinpointhq.com