Water Supply Planning Lead (Senior Advisor)

We need to output HTML fragment with sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: There's a description of role (What You Will Do) - that's responsibilities. There's "What You Will Need" - that's requirements/qualifications/skills. There's "The Halff Water Supply Planning Advantage" - maybe about the role? Could be "About the role" or "Company Overview". There's "Company Overview" - maybe about the firm. There's "We Offer Excellent Benefits..." - benefits. There's "Salary is competitive and commensurate with experience." - that's pay but it's vague "commensurate with experience" - we should NOT include Pay section if it's just "commensurate with experience" (placeholder). The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits: they list specific benefits (medical, dental, etc.) So we can include Benefits section. Pay: they say "Salary is competitive and commensurate with experience." That's placeholder, so we should NOT include Pay section. Schedule: not mentioned, so omit. We need to include sections: About the role? Possibly we can combine role description and company overview into About the role? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which headings to use. We need to preserve all substantive information. Let's structure: -

About the role

: include description of role as senior advisor, what they do? Actually "What You Will Do" is responsibilities. Could put role overview in About the role, and responsibilities separate. But we need to avoid duplication. Let's think: The posting includes: first paragraph describing role (recognized expert, provides companywide leadership...). Then "What You Will Do" bullet list (actually paragraphs). Then "What You Will Need". Then "The Halff Water Supply Planning Advantage". Then "Company Overview". Then benefits. So we could have: About the role: summary paragraph (first paragraph). Responsibilities: the "What You Will Do" list. Requirements: maybe combine "What You Will Need" and "The Halff Water Supply Planning Advantage"? Actually "What You Will Need" is qualifications/requirements. Could split into Requirements (education, experience) and Skills (specific expertise). Qualifications maybe similar. But we have limited headings; we can use Requirements and Skills. Qualifications maybe not needed if we cover in Requirements. Let's decide: - About the role: introductory paragraph. - Responsibilities: the bullet points under "What You Will Do". - Requirements: education, degree, license, years experience, external recognition. - Skills: specific expertise (demand forecasting, source reliability, etc.), ability to lead initiatives, client relationships, mentoring, industry presence. - Benefits: list of benefits. We should not include Pay or Schedule. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to keep all details from each section. Let's extract content. About the role paragraph: "The Water Supply Planning Lead (Senior Advisor) is a recognized water supply planning expert and trusted advisor who provides companywide leadership on complex water resources challenges. This role guides long-range water supply planning, demand forecasting, source reliability and yield analysis, conservation, drought preparedness, alternative water supplies, and resilient infrastructure strategies. Working across offices and disciplines, the Senior Advisor helps clients make informed decisions that support reliable service, regulatory compliance, sustainable growth, and long-term water security. The ideal candidate is an externally recognized thought leader with deep experience evaluating surface water, groundwater, reuse, conservation, and other supply options; leading regional and statewide water planning initiatives; and solving the most complex technical, regulatory, financial, and stakeholder challenges. The role translates advanced analyses into clear, actionable recommendations for utility leaders, public agencies, elected officials, and multidisciplinary teams. Consistent with Halff’s Senior Advisor career level, this position focuses primarily on strategic planning, market and client development, major pursuits, technical mentoring, industry leadership, and advancement of the firm’s water supply planning capabilities, while serving as a technical or project advisor on select high-impact assignments." That's a lot; we can keep as prose in

  . Responsibilities: Under "What You Will Do" there are bullet-like paragraphs each starting with bold label. We need to turn each into

• . Let's list them: - Strategic Technical Leadership: Serve as Halff’s senior subject matter expert and trusted client advisor for long-range water supply planning, water availability, demand forecasting, system yield and reliability, conservation, drought preparedness, and source diversification. - Complex Planning and Problem Solving: Proactively identify, define, and solve complex water supply challenges that integrate technical, regulatory, financial, environmental, infrastructure, and stakeholder considerations. - Water Supply Evaluations: Guide assessments of surface water, groundwater, reuse, conservation, interconnections, transfers, storage, and other alternative supplies, including feasibility, permitting, reliability, risk, cost, and implementation considerations. - Multidisciplinary Initiative Leadership: Lead major regional and statewide water planning studies and initiatives across offices and practices, aligning teams around scope, technical approach, quality, schedule, budget, risk, and client objectives. - Strategy and Market Growth: Influence water supply planning strategy, identify emerging business and regulatory challenges, develop market-positioning plans, and help shape service improvements that strengthen Halff’s competitive advantage. - Client and Business Development: Build long-term relationships with utilities, districts, river authorities, groundwater districts, public agencies, and industry partners; lead strategic pursuits, capture planning, teaming, technical approaches, and client presentations. - Technical Quality and Risk: Provide senior-level review and advisory oversight for models, planning assumptions, technical memoranda, reports, regulatory documentation, and implementation plans; promote consistent QA/QC and defensible decision-making. - Staff Development: Mentor and coach technical professionals, project managers, and emerging leaders; identify training needs; share best practices; and strengthen the firmwide water supply planning talent pipeline. - Industry Leadership: Represent Halff through professional organizations, conferences, publications, presentations, and advisory roles that expand the firm’s reputation as a leader in water supply planning. We need to keep each as
• with the bold label maybe as part of text. We'll keep the label and colon. Requirements: From "What You Will Need": - Bachelor’s degree in civil, environmental, or water resources engineering, planning, or a closely related field; advanced degree preferred. - Professional Engineer license or other relevant professional credential preferred, based on discipline and responsibilities. - More than 15 years of relevant experience in water supply planning, water resources planning, utility planning, or a related field. - External recognition as a water supply planning thought leader and trusted advisor to utilities, agencies, and industry partners. We can put these as
• . Skills: The rest of "What You Will Need" after those bullet points? Actually after those bullet points there are more lines: - Demonstrated expertise in demand forecasting, source reliability and yield analysis, conservation, drought planning, alternative water supplies, infrastructure phasing, and regulatory coordination. - Proven ability to lead multidisciplinary planning initiatives and solve complex problems with broad client and business impact. - Strong record of developing client relationships, positioning for strategic work, leading pursuits, and contributing to market and practice strategy. - Demonstrated success mentoring technical staff and communicating complex information clearly to technical and non-technical audiences. - Established industry presence through presentations, publications, professional organizations, or key advisory roles. These are skills/expertise. We'll put them as
• under Skills. Benefits: Under "We Offer Excellent Benefits, Including But Not Limited To" then list: - Medical, dental, prescription and life insurance - Long-term and short-term disability insurance - Paid time off (PTO) and 8 company paid holidays (and Veteran's Day for our veterans) - Traditional and Roth 401(k) plans - Employee Stock Ownership Plan (ESOP) - Health Savings Accounts (HSA) - 529 College Savings Plan - Flexible Spending Accounts (FSA) - Employee Assistance Plan (EAP) - Click here for a more comprehensive list of Halff's benefits We should keep the list items. The "Click here for a more comprehensive list..." is a link; we can keep as
• with text. We must not include boilerplate like EEO, drug-free workplace, etc. Remove those. Also remove "Learn more about Halff's water solutions, projects, and team Halff's Water Supply Planning Services ..." that's maybe a link list; but it's under "The Halff Water Supply Planning Advantage" maybe? Actually after advantages there is a line: "Learn more about Halff's water solutions, projects, and team Halff's Water Supply Planning Services Long-Range Water Supply and Regional Planning..." That seems like a list of services. This is substantive? It describes services offered. Might be considered part of "About the role" or "Company Overview"? It's a list of service lines. We should preserve it if it's substantive. It appears after "The Halff Water Supply Planning Advantage" paragraph. Let's capture that. The text: "Learn more about Halff's water solutions, projects, and team Halff's Water Supply Planning Services Long-Range Water Supply and Regional PlanningWater Demand Forecasting and Conservation PlanningWater Availability, Source Reliability, and System Yield AnalysisSurface Water, Groundwater, Reuse, and Alternative Supply EvaluationsDrought Preparedness, Risk Assessment, and Resilience PlanningInfrastructure Phasing, Capital Planning, and Implementation StrategyRegulatory, Agency, and Stakeholder Coordination" It seems like a run-on without spaces. But we can treat as a list of services. We'll need to parse into items. The original likely had line breaks. We'll create
  • for each service line. List items: - Long-Range Water Supply and Regional Planning - Water Demand Forecasting and Conservation Planning - Water Availability, Source Reliability, and System Yield Analysis - Surface Water, Groundwater, Reuse, and Alternative Supply Evaluations - Drought Preparedness, Risk Assessment, and Resilience Planning - Infrastructure Phasing, Capital Planning, and Implementation Strategy - Regulatory, Agency, and Stakeholder Coordination We need to decide where to put this. Could be under "About the role" as additional description, or maybe a separate section like "Services". But we only have allowed headings list; we could put under "About the role" as part of prose? Better to create a section "Services" but not in allowed headings. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings if we need sections. It doesn't say we cannot use other headings, but to follow the example. Safer to stick to those headings. We could incorporate the services list into "About the role" or "Responsibilities". Probably "About the role" includes description of what the role does; the services list is more about the firm's offerings. Could go under "About the role" as additional detail. Alternatively, we could create a section "Company Overview" but not in list. But we have "About the role" which could include company overview. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other