Water Utilities & Groundwater Market Leader
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to include a section ONLY when posting has real, specific content for it.
Thus we will create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Check each for content:
About the role: includes description: "Environmental Science Associates (ESA) is a 100% employee-owned environmental consulting firm... ESA is seeking a strategic Water Utilities & Groundwater Market Leader to serve in one of the firm's most senior market leadership roles. This leader will set and execute a firmwide growth strategy, strengthen ESA's position with priority clients, and align client needs with the full range of ESA capabilities across practices and regions. The Market Leader is accountable for market direction and measurable growth, including priority-client development, pipeline and backlog expansion, contract acquisition and activation, strategic investment, and strong financial performance. The role requires a leader who can work through ESA's collaborative matrix and bring together Client Service Managers, Practice Leaders, Regional Directors, Business Group Directors, project leaders, and corporate marketing professionals around shared priorities. The position reports to ESA's Chief Growth Officer and will coordinate closely with the other Market Leaders, the Practice Leaders, and the Regional Directors so that clients experience the full capabilities of ESA. The position may be based in any ESA region - Northern California, Southern California, Pacific Northwest, or Southeast - and will operate on a hybrid schedule with periodic travel to ESA offices, client locations, and industry events."
That's substantive.
Responsibilities: includes "What You Will Do" and "Key Responsibilities". We need to list duties. We'll extract bullet points from those sections.
We have many responsibilities: develop and execute annual market growth plan, use market intelligence, build diversified portfolio, monitor market performance, advise executive leadership on strategic hiring, partnerships, acquisitions, technology investments, new capabilities; executive client leadership: develop trusted relationships, engage clients before projects defined, work with Client Success Managers to develop account plans, translate agency business needs into opportunities, serve as executive sponsor, strategic advisor, or Project Director for selected complex assignments, create disciplined transitions from early strategy into implementation; integrated solutions & delivery: bring together ESA practices, partner with project leaders, identify gaps, support strategic pursuits, proposals, interviews, negotiations, coordinate with Water Resources & Infrastructure Market Leader; market visibility, partnerships & innovation: serve as visible external leader, shape ESA point of view, develop strategic relationships with partners, identify practical applications of emerging technology; matrix leadership & talent: create shared priorities, coach client and technical leaders, work with regional and practice leadership to recruit/retain/deploy talent, model One ESA leadership, contribute to enterprise strategy.
We need to preserve all substantive info; we can list them as
- items.
Requirements: "Who You Are" bullet list: 15+ years progressively responsible experience in water sector within water/wastewater utility, public water agency, environmental/engineering consulting firm, infrastructure organization, or related advisory environment. Senior leadership experience with strong understanding of how water agencies establish priorities, make investment decisions, manage regulatory and operational risk, move initiatives from planning into implementation. Demonstrated ability to build trusted executive relationships and influence complex decisions involving multiple departments, disciplines, stakeholders, and regulatory agencies. Experience developing or advancing significant water programs, client relationships, partnerships, or consulting opportunities, with business judgment to connect client value to measurable growth. Broad knowledge of water supply and reliability, water rights, wastewater and reuse, groundwater management and recharge, resilience, environmental planning, permitting, regulatory compliance, and infrastructure implementation. Strong financial and commercial acumen, including ability to set growth priorities and manage revenue, pipeline, backlog, investment, and profitability expectations. Proven ability to lead through influence in a matrixed organization, build alignment among senior peers, and mobilize multidisciplinary teams. Bachelor's degree in environmental science, engineering, water resources, planning, public administration, business, or related discipline; an advanced degree is valued but not required. Outstanding written, verbal, facilitation, and presentation skills, with ability to communicate credibly with executives, technical professionals, regulators, boards, and community stakeholders.
That's requirements.
Qualifications: maybe separate from requirements? The posting includes "Preferred Experience" after requirements. That could be considered Qualifications? Actually "Preferred Experience" is separate list: well-established network among water, wastewater, groundwater, multipurpose water agencies in one or more ESA regions, ability to expand relationships nationally. Experience integrating strategy, environmental and regulatory requirements, technology, capital planning, and operations. Experience moving between public-agency and consulting environments or leading collaborative teams that include agencies, consultants, engineers, researchers, and technology partners.
We could treat "Preferred Experience" as Qualifications or Skills. But we have separate sections for Qualifications and Skills. We need to decide what goes where.
The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to map content accordingly.
We have:
- Requirements: mandatory qualifications (the "Who You Are").
- Qualifications: maybe education, advanced degree valued? But that is already in Requirements. Could treat "Preferred Experience as Qualifications.
- Skills: maybe specific abilities like financial acumen, leadership, communication, etc. But many of those are in Requirements.
We need to avoid duplication. Perhaps we can put:
- Requirements: the mandatory experience and education.
- Qualifications: the preferred experience (network, integrating strategy, moving between public/consulting, leading collaborative teams).
- Skills: maybe the specific abilities like financial and commercial acumen, ability to lead through influence, outstanding written/verbal/facilitation/presentation skills, ability to build trusted executive relationships, etc. But those are also in Requirements.
We could decide to not have Skills section if content overlaps heavily; but instruction says prefer a few substantive sections over many thin ones. We could combine Skills into Requirements or Qualifications. However we need to include sections only when posting has real specific content for it. If we put Skills, we need to have specific content not already covered elsewhere. Could we extract "Outstanding written, verbal, facilitation, and presentation skills" as Skills? That is a skill. Also "Strong financial and commercial acumen". Also "Proven ability to lead through influence". Those are skills.
But they are also listed under Requirements. However we could still include them under Skills as separate bullet list, but that would duplicate content. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited, but we should avoid unnecessary duplication? Not explicitly prohibited. However they say "Prefer a few substantive sections over many thin ones." So maybe better to not have Skills if it's thin.
We could treat Qualifications as the preferred experience and Skills as the specific abilities (financial acumen, leadership, communication). That would give us three sections: Requirements, Qualifications, Skills.
But we also need About the role, Responsibilities, Benefits, Pay, Schedule.
Thus total sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to ensure each section has substantive content.
Let's extract content for each.
About the role: as above.
Responsibilities: list of duties from "What You Will Do" and "Key Responsibilities". We'll combine.
Requirements: mandatory experience and education (Who You Are). We'll list bullet points.
Qualifications: preferred experience (the three bullet points under "Preferred Experience").
Skills: maybe we can list specific skillsets: financial and commercial acumen, ability to lead through influence, outstanding written/verbal/facilitation/presentation skills, ability to build trusted executive relationships, strategic thinking, etc. But many are already in Requirements. However we could still list them; duplication may be okay but might be considered thin. However we could combine Skills into Requirements and not have Skills section. But we need to decide.
Given instruction: "Prefer a few substantive sections over many thin ones." If we add Skills, we might have many sections (8). That's okay if each is substantive. But Skills might be thin if we just list a few bullet points that are already covered. However we could make Skills substantive by extracting distinct skill items not covered elsewhere: e.g., "financial and commercial acumen", "ability to lead through influence in a matrixed organization", "outstanding written, verbal, facilitation, and presentation skills", "ability to build trusted executive relationships and influence complex decisions", "strategic thinking and market intelligence", "ability to translate agency business needs into opportunities", "executive sponsorship and project direction", "ability to coach and mentor", "ability to create shared priorities across matrix". Many of these are already in Requirements or Responsibilities.
Thus Skills may be redundant.
Given the instruction to prefer fewer sections, maybe we omit Skills and put those skill items under Requirements or Qualifications. But we already have Requirements (mandatory) and Qualifications (preferred). Could we put skill items under Requirements? They are already there. So we could just have Requirements and Qualifications.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
That's 7 sections.
Check if we need Skills: maybe not.
Now Benefits: we have description: medical, dental, vision insurance (paid at 70% for you AND your family), annual allocations of company share through ESOP, 401(k) plan with company match, paid vacation, sick leave, holidays, tuition reimbursement, professional development bonuses, attendance at conferences. Also specific programs to further technical expertise, sharpen business acumen, help lead next generation of employee-owners. We'll list as bullet list.
Pay: salary range $250,000—$300,000 USD. Also note that actual compensation determined by factors including experience, education, skills, city. We'll include that as prose.
Schedule: hybrid schedule with periodic travel to ESA offices, client locations, industry events. Also position may be based in any ESA region - Northern California, Southern California, Pacific Northwest, or Southeast. That's location, but schedule is hybrid. We'll include schedule info.
Now we need to ensure we don't include boilerplate like "We are a 100% employee-owned environmental consulting firm who values diversity and inclusion..." That's at end; we can drop as boilerplate? It's about culture, maybe not required. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement might be considered EEO/equal-opportunity
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section ONLY when posting has real, specific content for it. Thus we will create sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Check each for content: About the role: includes description: "Environmental Science Associates (ESA) is a 100% employee-owned environmental consulting firm... ESA is seeking a strategic Water Utilities & Groundwater Market Leader to serve in one of the firm's most senior market leadership roles. This leader will set and execute a firmwide growth strategy, strengthen ESA's position with priority clients, and align client needs with the full range of ESA capabilities across practices and regions. The Market Leader is accountable for market direction and measurable growth, including priority-client development, pipeline and backlog expansion, contract acquisition and activation, strategic investment, and strong financial performance. The role requires a leader who can work through ESA's collaborative matrix and bring together Client Service Managers, Practice Leaders, Regional Directors, Business Group Directors, project leaders, and corporate marketing professionals around shared priorities. The position reports to ESA's Chief Growth Officer and will coordinate closely with the other Market Leaders, the Practice Leaders, and the Regional Directors so that clients experience the full capabilities of ESA. The position may be based in any ESA region - Northern California, Southern California, Pacific Northwest, or Southeast - and will operate on a hybrid schedule with periodic travel to ESA offices, client locations, and industry events." That's substantive. Responsibilities: includes "What You Will Do" and "Key Responsibilities". We need to list duties. We'll extract bullet points from those sections. We have many responsibilities: develop and execute annual market growth plan, use market intelligence, build diversified portfolio, monitor market performance, advise executive leadership on strategic hiring, partnerships, acquisitions, technology investments, new capabilities; executive client leadership: develop trusted relationships, engage clients before projects defined, work with Client Success Managers to develop account plans, translate agency business needs into opportunities, serve as executive sponsor, strategic advisor, or Project Director for selected complex assignments, create disciplined transitions from early strategy into implementation; integrated solutions & delivery: bring together ESA practices, partner with project leaders, identify gaps, support strategic pursuits, proposals, interviews, negotiations, coordinate with Water Resources & Infrastructure Market Leader; market visibility, partnerships & innovation: serve as visible external leader, shape ESA point of view, develop strategic relationships with partners, identify practical applications of emerging technology; matrix leadership & talent: create shared priorities, coach client and technical leaders, work with regional and practice leadership to recruit/retain/deploy talent, model One ESA leadership, contribute to enterprise strategy. We need to preserve all substantive info; we can list them as
- items. Requirements: "Who You Are" bullet list: 15+ years progressively responsible experience in water sector within water/wastewater utility, public water agency, environmental/engineering consulting firm, infrastructure organization, or related advisory environment. Senior leadership experience with strong understanding of how water agencies establish priorities, make investment decisions, manage regulatory and operational risk, move initiatives from planning into implementation. Demonstrated ability to build trusted executive relationships and influence complex decisions involving multiple departments, disciplines, stakeholders, and regulatory agencies. Experience developing or advancing significant water programs, client relationships, partnerships, or consulting opportunities, with business judgment to connect client value to measurable growth. Broad knowledge of water supply and reliability, water rights, wastewater and reuse, groundwater management and recharge, resilience, environmental planning, permitting, regulatory compliance, and infrastructure implementation. Strong financial and commercial acumen, including ability to set growth priorities and manage revenue, pipeline, backlog, investment, and profitability expectations. Proven ability to lead through influence in a matrixed organization, build alignment among senior peers, and mobilize multidisciplinary teams. Bachelor's degree in environmental science, engineering, water resources, planning, public administration, business, or related discipline; an advanced degree is valued but not required. Outstanding written, verbal, facilitation, and presentation skills, with ability to communicate credibly with executives, technical professionals, regulators, boards, and community stakeholders. That's requirements. Qualifications: maybe separate from requirements? The posting includes "Preferred Experience" after requirements. That could be considered Qualifications? Actually "Preferred Experience" is separate list: well-established network among water, wastewater, groundwater, multipurpose water agencies in one or more ESA regions, ability to expand relationships nationally. Experience integrating strategy, environmental and regulatory requirements, technology, capital planning, and operations. Experience moving between public-agency and consulting environments or leading collaborative teams that include agencies, consultants, engineers, researchers, and technology partners. We could treat "Preferred Experience" as Qualifications or Skills. But we have separate sections for Qualifications and Skills. We need to decide what goes where. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to map content accordingly. We have: - Requirements: mandatory qualifications (the "Who You Are"). - Qualifications: maybe education, advanced degree valued? But that is already in Requirements. Could treat "Preferred Experience as Qualifications. - Skills: maybe specific abilities like financial acumen, leadership, communication, etc. But many of those are in Requirements. We need to avoid duplication. Perhaps we can put: - Requirements: the mandatory experience and education. - Qualifications: the preferred experience (network, integrating strategy, moving between public/consulting, leading collaborative teams). - Skills: maybe the specific abilities like financial and commercial acumen, ability to lead through influence, outstanding written/verbal/facilitation/presentation skills, ability to build trusted executive relationships, etc. But those are also in Requirements. We could decide to not have Skills section if content overlaps heavily; but instruction says prefer a few substantive sections over many thin ones. We could combine Skills into Requirements or Qualifications. However we need to include sections only when posting has real specific content for it. If we put Skills, we need to have specific content not already covered elsewhere. Could we extract "Outstanding written, verbal, facilitation, and presentation skills" as Skills? That is a skill. Also "Strong financial and commercial acumen". Also "Proven ability to lead through influence". Those are skills. But they are also listed under Requirements. However we could still include them under Skills as separate bullet list, but that would duplicate content. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited, but we should avoid unnecessary duplication? Not explicitly prohibited. However they say "Prefer a few substantive sections over many thin ones." So maybe better to not have Skills if it's thin. We could treat Qualifications as the preferred experience and Skills as the specific abilities (financial acumen, leadership, communication). That would give us three sections: Requirements, Qualifications, Skills. But we also need About the role, Responsibilities, Benefits, Pay, Schedule. Thus total sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to ensure each section has substantive content. Let's extract content for each. About the role: as above. Responsibilities: list of duties from "What You Will Do" and "Key Responsibilities". We'll combine. Requirements: mandatory experience and education (Who You Are). We'll list bullet points. Qualifications: preferred experience (the three bullet points under "Preferred Experience"). Skills: maybe we can list specific skillsets: financial and commercial acumen, ability to lead through influence, outstanding written/verbal/facilitation/presentation skills, ability to build trusted executive relationships, strategic thinking, etc. But many are already in Requirements. However we could still list them; duplication may be okay but might be considered thin. However we could combine Skills into Requirements and not have Skills section. But we need to decide. Given instruction: "Prefer a few substantive sections over many thin ones." If we add Skills, we might have many sections (8). That's okay if each is substantive. But Skills might be thin if we just list a few bullet points that are already covered. However we could make Skills substantive by extracting distinct skill items not covered elsewhere: e.g., "financial and commercial acumen", "ability to lead through influence in a matrixed organization", "outstanding written, verbal, facilitation, and presentation skills", "ability to build trusted executive relationships and influence complex decisions", "strategic thinking and market intelligence", "ability to translate agency business needs into opportunities", "executive sponsorship and project direction", "ability to coach and mentor", "ability to create shared priorities across matrix". Many of these are already in Requirements or Responsibilities. Thus Skills may be redundant. Given the instruction to prefer fewer sections, maybe we omit Skills and put those skill items under Requirements or Qualifications. But we already have Requirements (mandatory) and Qualifications (preferred). Could we put skill items under Requirements? They are already there. So we could just have Requirements and Qualifications. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Check if we need Skills: maybe not. Now Benefits: we have description: medical, dental, vision insurance (paid at 70% for you AND your family), annual allocations of company share through ESOP, 401(k) plan with company match, paid vacation, sick leave, holidays, tuition reimbursement, professional development bonuses, attendance at conferences. Also specific programs to further technical expertise, sharpen business acumen, help lead next generation of employee-owners. We'll list as bullet list. Pay: salary range $250,000—$300,000 USD. Also note that actual compensation determined by factors including experience, education, skills, city. We'll include that as prose. Schedule: hybrid schedule with periodic travel to ESA offices, client locations, industry events. Also position may be based in any ESA region - Northern California, Southern California, Pacific Northwest, or Southeast. That's location, but schedule is hybrid. We'll include schedule info. Now we need to ensure we don't include boilerplate like "We are a 100% employee-owned environmental consulting firm who values diversity and inclusion..." That's at end; we can drop as boilerplate? It's about culture, maybe not required. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The diversity statement might be considered EEO/equal-opportunity