Water Systems Intelligence Engineer
McKim & Creed, Inc. · Asheville, NC · 4 wk ago
HybridFull-time
We need to output HTML fragment only, with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, legal, scam warning, application instructions. Also remove "During Your Work-day, You Will" maybe part of responsibilities. We need to parse the posting.
Let's extract sections:
- Summary: description of role: "The Water Systems Intelligence Engineer bridges engineering, operations, and analytics to transform water and wastewater systems into data-driven, intelligent assets. This role combines traditional water infrastructure expertise with real-time operational data, digital twins, predictive analytics, and advanced visualization tools to improve performance, reliability, resilience, and decision-making across utility systems. Turning live system data into smarter decisions, optimized operations, and resilient water infrastructure. This role has two primary objectives: 1. Non-Revenue Water (NRW) Project Management, assistance, and Program development. 2. Technical support for Business Development efforts"
That's about the role.
- "What You'll Need": list of requirements: Bachelor’s degree in civil engineering, Environmental Engineering, Water Resources Engineering, Computer Engineering, Data Science, or related field. 5+ years of experience in water/wastewater engineering, utility operations, hydraulic modeling, or digital water technologies. Experience working with operational data systems including SCADA, GIS, SQL databases, and cloud platforms. Strong analytical and Problem-solving skills. Excellent communication and client-facing abilities. Professional Engineer (PE) license. Experience with digital twin platforms and smart utility programs. Familiarity with machine learning, predictive modeling, and AI-assisted analytics. Experience integrating engineering models with enterprise asset management and operational systems. Consulting experience working directly with utility clients.
- "What Will Make You Stand Out": bullet list: The ideal candidate is passionate about leveraging technology and engineering principles to optimize water and wastewater operations, helping clients move from reactive management to proactive and predictive system operation. Then list: Engineering Analysis, Data Analytics & Visualization, Digital Twin Development, Water & Wastewater Operation, System Optimization, Predictive Modeling, Operational Intelligence, Client Relationship Management, Strategic Thinking, Innovation Leadership. Then "Experience with hydraulic and/or process modeling software such as: InfoWater Pro, InfoWorks WS Pro, InfoWorks ICM, WaterGEMS, SewerGEMS, EPANET". This could be Skills.
- "During Your Work-day, You Will": then subheadings: Digital Water & System Intelligence, Data Analytics & Decision Support, Engineering & System Optimization, Client Consulting & Collaboration, Innovation & Emerging Technologies, Business Development. These are responsibilities.
- "Success Measures": bullet list: The Successful Water Systems Intelligence Engineer Will Transform utility data into actionable operational insights. Identify measurable opportunities for efficiency, resilience, and cost savings. Bridge the gap between engineering, operations, and technology teams. Assist internal and external clients to accelerate their digital transformation journey and maximize the value of their infrastructure investments. This may include direct Project Management. Schedule will include participation in on all weekly client call as well as supporting the efforts of our Business Development Team.. (some grammar issues). This could be part of responsibilities or maybe separate.
- "WHAT WE OFFER:" then bullet list: Employee Stock Ownership Plan (ESOP): All employees are owners & benefit from profits earned. Competitive pay paid holidays, bereavement, and parental, medical, and military leave. Multiple office locations to work from: Stick close to home or travel for a change of scenery. Growth opportunities & training: Grow confidently in your career with our mentoring & training options. Professional development: Tuition reimbursement, early career professional program, online courses & more. Work that makes a difference: See the direct impact your work has on our communities. Collaborative, supportive team: People to help you solve problems, cheer successes & encourage you along the way.
We need to map to sections: About the role (summary), Responsibilities (the "During Your Work-day, You Will" plus maybe Success Measures?), Requirements (What You'll Need), Qualifications (maybe overlapping with Requirements? but we can treat Requirements as qualifications? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which content goes where.
We have:
- About the role: summary description.
- Responsibilities: tasks/duties: the "During Your Work-day, You Will" sections and maybe Success Measures (identify opportunities, bridge gap, assist clients, direct project management, schedule participation). Also Business Development work.
- Requirements: maybe the "What You'll Need" (education, experience, license). Could also include "Professional Engineer (PE) license". That's a requirement.
- Qualifications: maybe the "What Will Make You Stand Out" (desired qualifications, standout factors). Could also include experience with modeling software.
- Skills: maybe the list of competencies: Engineering Analysis, Data Analytics & Visualization, etc. Or we could treat those as Skills.
- Benefits: the WHAT WE OFFER list.
- Pay: not mentioned specifically (only "Competitive pay" but no amount). The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Competitive pay" is stated, but no specific number. Is that enough? It says "Competitive pay paid holidays, bereavement, and parental, medical, and military leave". That is a mention of pay but not a specific figure. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay". So we could include a Pay section with that phrase. However they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Pay with that line.
- Schedule: The posting mentions "Schedule will include participation in on all weekly client call as well as supporting the efforts of our Business Development Team." That's a schedule detail. So we can include Schedule section with that sentence.
But we must avoid filler like "commensurate with experience", "not specified", etc. Here we have actual statements.
Thus we will create sections:
.
List:
- Employee Stock Ownership Plan (ESOP): All employees are owners & benefit from profits earned.
- Competitive pay paid holidays, bereavement, and parental, medical, and military leave.
- Multiple office locations to work from: Stick close to home or travel for a change of scenery.
- Growth opportunities & training: Grow confidently in your career with our mentoring & training options.
- Professional development: Tuition reimburs
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like EEO, etc. Also remove duplicated lines, navigation, cookie, legal, scam warning, application instructions. Also remove "During Your Work-day, You Will" maybe part of responsibilities. We need to parse the posting.
Let's extract sections:
- Summary: description of role: "The Water Systems Intelligence Engineer bridges engineering, operations, and analytics to transform water and wastewater systems into data-driven, intelligent assets. This role combines traditional water infrastructure expertise with real-time operational data, digital twins, predictive analytics, and advanced visualization tools to improve performance, reliability, resilience, and decision-making across utility systems. Turning live system data into smarter decisions, optimized operations, and resilient water infrastructure. This role has two primary objectives: 1. Non-Revenue Water (NRW) Project Management, assistance, and Program development. 2. Technical support for Business Development efforts"
That's about the role.
- "What You'll Need": list of requirements: Bachelor’s degree in civil engineering, Environmental Engineering, Water Resources Engineering, Computer Engineering, Data Science, or related field. 5+ years of experience in water/wastewater engineering, utility operations, hydraulic modeling, or digital water technologies. Experience working with operational data systems including SCADA, GIS, SQL databases, and cloud platforms. Strong analytical and Problem-solving skills. Excellent communication and client-facing abilities. Professional Engineer (PE) license. Experience with digital twin platforms and smart utility programs. Familiarity with machine learning, predictive modeling, and AI-assisted analytics. Experience integrating engineering models with enterprise asset management and operational systems. Consulting experience working directly with utility clients.
- "What Will Make You Stand Out": bullet list: The ideal candidate is passionate about leveraging technology and engineering principles to optimize water and wastewater operations, helping clients move from reactive management to proactive and predictive system operation. Then list: Engineering Analysis, Data Analytics & Visualization, Digital Twin Development, Water & Wastewater Operation, System Optimization, Predictive Modeling, Operational Intelligence, Client Relationship Management, Strategic Thinking, Innovation Leadership. Then "Experience with hydraulic and/or process modeling software such as: InfoWater Pro, InfoWorks WS Pro, InfoWorks ICM, WaterGEMS, SewerGEMS, EPANET". This could be Skills.
- "During Your Work-day, You Will": then subheadings: Digital Water & System Intelligence, Data Analytics & Decision Support, Engineering & System Optimization, Client Consulting & Collaboration, Innovation & Emerging Technologies, Business Development. These are responsibilities.
- "Success Measures": bullet list: The Successful Water Systems Intelligence Engineer Will Transform utility data into actionable operational insights. Identify measurable opportunities for efficiency, resilience, and cost savings. Bridge the gap between engineering, operations, and technology teams. Assist internal and external clients to accelerate their digital transformation journey and maximize the value of their infrastructure investments. This may include direct Project Management. Schedule will include participation in on all weekly client call as well as supporting the efforts of our Business Development Team.. (some grammar issues). This could be part of responsibilities or maybe separate.
- "WHAT WE OFFER:" then bullet list: Employee Stock Ownership Plan (ESOP): All employees are owners & benefit from profits earned. Competitive pay paid holidays, bereavement, and parental, medical, and military leave. Multiple office locations to work from: Stick close to home or travel for a change of scenery. Growth opportunities & training: Grow confidently in your career with our mentoring & training options. Professional development: Tuition reimbursement, early career professional program, online courses & more. Work that makes a difference: See the direct impact your work has on our communities. Collaborative, supportive team: People to help you solve problems, cheer successes & encourage you along the way.
We need to map to sections: About the role (summary), Responsibilities (the "During Your Work-day, You Will" plus maybe Success Measures?), Requirements (What You'll Need), Qualifications (maybe overlapping with Requirements? but we can treat Requirements as qualifications? The instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which content goes where.
We have:
- About the role: summary description.
- Responsibilities: tasks/duties: the "During Your Work-day, You Will" sections and maybe Success Measures (identify opportunities, bridge gap, assist clients, direct project management, schedule participation). Also Business Development work.
- Requirements: maybe the "What You'll Need" (education, experience, license). Could also include "Professional Engineer (PE) license". That's a requirement.
- Qualifications: maybe the "What Will Make You Stand Out" (desired qualifications, standout factors). Could also include experience with modeling software.
- Skills: maybe the list of competencies: Engineering Analysis, Data Analytics & Visualization, etc. Or we could treat those as Skills.
- Benefits: the WHAT WE OFFER list.
- Pay: not mentioned specifically (only "Competitive pay" but no amount). The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Competitive pay" is stated, but no specific number. Is that enough? It says "Competitive pay paid holidays, bereavement, and parental, medical, and military leave". That is a mention of pay but not a specific figure. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay". So we could include a Pay section with that phrase. However they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Pay with that line.
- Schedule: The posting mentions "Schedule will include participation in on all weekly client call as well as supporting the efforts of our Business Development Team." That's a schedule detail. So we can include Schedule section with that sentence.
But we must avoid filler like "commensurate with experience", "not specified", etc. Here we have actual statements.
Thus we will create sections:
About the role
... summary ...
Responsibilities
- ... each duty ...
Requirements
- ...
Qualifications
- ...
Skills
- ...