Water Resources Engineer
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Key info:
- Company description: Stanley Consultants is award-winning etc. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
- Job title: Water Resources Engineer (not to be repeated as heading). Locations: Chicago, IL | Minneapolis, MN. Job type: Hybrid. Requisition ID: 11263 (should be folded into short p or dropped). Probably we can include a short p with location and job type.
- The posting includes: "Stanley Consultants is currently looking for a Water Resources Engineer for our Chicago or Minneapolis office. We are team of water resource, geotechnical, structural, and civil engineers that deliver water resource engineering projects focused on hydraulic and hydrologic systems, navigation, flood risk reduction, and site improvement projects for clients nationally and globally. We are seeking motivated candidates that enjoy working in a team environment on challenging projects to join our team."
That's about the role.
- "You are a licensed Civil Engineer (4+ years experience) holding a Bachelor’s Degree in Civil Engineering related field." That's a requirement/qualification.
- Responsibilities: "Your responsibilities will include leading a team of engineers in the technical analysis, design, preparation of construction documents, reports, and cost estimates for water resources, infrastructure, environmental, structural, and energy projects. Project development including hydrologic and hydraulic analysis, ponding and detention area sizing and design, streambank stabilization, civil design layout, surface modeling, grading and drainage, utility layout and design, and low impact development feature layout and design. Project management skills and the ability to work directly with clients in the development of projects is desirable. Some field work and travel may be required. Be comfortable with leading and mentoring a team of younger engineers and technical staff. You will have the opportunity to working on a wide range of water resources and civil engineering projects and develop your career towards more project management or team managerial responsibilities."
- Required Qualifications: list bullet points: Bachelor of Science degree in Civil Engineering; Professional Engineer (PE) licensed or ability to become licensed within 6 months of employment; Wide knowledge with water resources engineering background, with the ability to lead project development and determination of solutions to meet client needs; Varied software experience including hydraulic/hydrologic modeling, HEC RAS, XPSWMM, HydroCAD or other modeling softwares in the development of project solutions; Working knowledge and experience with ACAD Civil 3D or Microstation products; Familiarity with site grading design, surface runoff management, detention design, conveyance; Strong oral communication and technical writing skills; Ability to work in a team environment.
- Then "Work-Life Balance" section: description of benefits: Member-Owned, Paid Time Away, Health Insurance, Financial Health, Professional Growth, Financial Rewards. Also mention flexible work options, competitive pay and great benefits earlier.
- Pay: The posting includes a note: "(Salary range for IL & MN locations) Stanley Consultants is committed to maintaining transparency... The starting salary for the successful candidate in this position is competitive and will be determined by the selected candidate's qualifications and experience, geographic location, internal equity, company policy and practices. In compliance with pay transparency laws, pay ranges are disclosed for positions and locations where required." No actual numbers given. So we should NOT create a Pay section because no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits are stated (list of benefits). So we can include Benefits section.
- Schedule: Not mentioned besides hybrid work options. No explicit schedule like full-time, part-time, shift. So we should not create Schedule section.
- About the role: we have description.
- Responsibilities: we have.
- Requirements: maybe combine with Qualifications? The instruction says we can have Requirements and Qualifications separate if content. We have "You are a licensed Civil Engineer (4+ years experience) holding a Bachelor’s Degree in Civil Engineering related field." That's a requirement. Also "Required Qualifications:" list. Could treat Requirements as the brief statement, Qualifications as the detailed list. Or we could combine. But we need to avoid thin sections. Probably better to have Requirements (short) and Qualifications (detailed list). Or we could have only Qualifications and skip Requirements if it's redundant. But we have both.
- Skills: maybe we can extract from qualifications: software experience, communication, teamwork. Could be a Skills section.
- Benefits: we have list.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. So we can include a short p with location and job type: e.g.,
Locations: Chicago, IL | Minneapolis, MN • Job type: Hybrid
. Also maybe include the requisition ID? Could fold into same p or drop. Probably include as minor metadata: Requisition ID: 11263
but maybe drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. So we can include a short p with that info.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract all substantive info:
- Company description (Stanley Consultants is award-winning... etc). That's substantive; we can include in About the role or maybe a separate "About the company" but not in allowed headings. Could put in About the role as part of description.
- Job title: Water Resources Engineer (not heading).
- Locations: Chicago, IL | Minneapolis, MN.
- Job type: Hybrid.
- Requisition ID: 11263.
- The team description: "We are team of water resource, geotechnical, structural, and civil engineers that deliver water resource engineering projects focused on hydraulic and hydrologic systems, navigation, flood risk reduction, and site improvement projects for clients nationally and globally. We are seeking motivated candidates that enjoy working in a team environment on challenging projects to join our team."
- Requirement: "You are a licensed Civil Engineer (4+ years experience) holding a Bachelor’s Degree in Civil Engineering related field."
- Responsibilities: leading a team of engineers in technical analysis, design, preparation of construction documents, reports, cost estimates for water resources, infrastructure, environmental, structural, and energy projects. Project development including hydrologic and hydraulic analysis, ponding and detention area sizing and design, streambank stabilization, civil design layout, surface modeling, grading and drainage, utility layout and design, and low impact development feature layout and design. Project management skills and ability to work directly with clients desirable. Some field work and travel may be required. Be comfortable with leading and mentoring a team of younger engineers and technical staff. Opportunity to work on wide range of water resources and civil engineering projects and develop career towards more project management or team managerial responsibilities.
- Required Qualifications list (as above).
- Skills: maybe we can extract from qualifications: software experience (HEC RAS, XPSWMM, HydroCAD, etc), ACAD Civil 3D or Microstation, site grading design, surface runoff management, detention design, conveyance, strong oral communication and technical writing, ability to work in team environment.
- Benefits: Member-Owned, Paid Time Away (paid holidays, generous PTO, parental leave, professional development leave), Health Insurance (medical, dental, vision, FSA, HSA, Doctor On Demand, wellness reimbursement, mental health resources), Financial Health (life insurance, short- and long-term disability insurance, identity theft protection, many other benefits), Professional Growth (tuition assistance, professional society membership, more), Financial Rewards (company stock ownership, generous 401K match, incentive compensation, profit-sharing contributions to retirement 401K plans). Also earlier: flexible work options, competitive pay and great benefits, strong sense of community, chance to build meaningful long-term career.
We need to include all that.
We should not include boilerplate like EEO, AI tools, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the EEO statement, the AI tools paragraph, the "Click Here: A Great Place To Work Learn more about Stanley Consultants in this short video: Working at Stanley Consultants", the unsolicited resumes statement, the Equal Opportunity Employer paragraph, the AI tools paragraph, the final paragraph about salary range (though we might keep some of it? It says we should not create Pay section unless posting actually states them. The posting states that salary is competitive and will be determined, but no numbers. So we can maybe include a short p about pay being competitive? But the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It didn't say we cannot mention pay in a paragraph elsewhere. However, the "Pay" section is a heading we should not create. But we could include a short paragraph about pay being competitive within About the role or Benefits? Probably better to not include any pay details because they are vague and could be considered filler. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should avoid mentioning pay if it's not specific. So we can omit the pay paragraph.
Similarly, schedule: hybrid is mentioned; we could include schedule info in a short p under About the role or maybe a separate Schedule section? But we should not create Schedule section unless posting actually states them. It does state hybrid work options, which is a schedule type. However, the instruction says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid work options, which is schedule. So we could create a Schedule section with that info. But we need to see if we have enough content for a Schedule section: just "Hybrid". That might be thin but it's real specific content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should not create a Schedule section for just hybrid; we could fold that into About the role or a short p.
Similarly, Benefits: we have substantive content, so we create Benefits section.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't miss any substantive info.
Let's draft:
About the role
Stanley Consultants is an award-winning and industry-leading global consulting engineering firm, with an unmatched commitment to culture, values, and ethics. We are dedicated to client experience and solve the most complex challenges to create a sustainable, connected, and enriched world for all. As the world changes, Stanley strategically evolves with it, integrating the latest technology, innovation, and resiliency practices. With over a century of experience serving the energy, federal government, transportation, and water sectors, we have helped improve lives and shape the infrastructure systems that connect us. As an employee-owned organization with a People First approach, we stand apart from other engineering consulting and services firms. At Stanley, your voice counts, your growth matters, and your success is our success. Stanley Consultants offers flexible work options, competitive pay and great benefits, a strong sense of community, and the chance to build a meaningful, long-term career! We are currently looking for a Water Resources Engineer for our Chicago or Minneapolis office. We are a team of water resource, geotechnical, structural, and civil engineers that deliver water resource engineering
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. So we can include a short p with location and job type: e.g.,
Locations: Chicago, IL | Minneapolis, MN • Job type: Hybrid
. Also maybe include the requisition ID? Could fold into same p or drop. Probably include as minor metadata:Requisition ID: 11263
but maybe drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it. So we can include a short p with that info. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting. Let's extract all substantive info: - Company description (Stanley Consultants is award-winning... etc). That's substantive; we can include in About the role or maybe a separate "About the company" but not in allowed headings. Could put in About the role as part of description. - Job title: Water Resources Engineer (not heading). - Locations: Chicago, IL | Minneapolis, MN. - Job type: Hybrid. - Requisition ID: 11263. - The team description: "We are team of water resource, geotechnical, structural, and civil engineers that deliver water resource engineering projects focused on hydraulic and hydrologic systems, navigation, flood risk reduction, and site improvement projects for clients nationally and globally. We are seeking motivated candidates that enjoy working in a team environment on challenging projects to join our team." - Requirement: "You are a licensed Civil Engineer (4+ years experience) holding a Bachelor’s Degree in Civil Engineering related field." - Responsibilities: leading a team of engineers in technical analysis, design, preparation of construction documents, reports, cost estimates for water resources, infrastructure, environmental, structural, and energy projects. Project development including hydrologic and hydraulic analysis, ponding and detention area sizing and design, streambank stabilization, civil design layout, surface modeling, grading and drainage, utility layout and design, and low impact development feature layout and design. Project management skills and ability to work directly with clients desirable. Some field work and travel may be required. Be comfortable with leading and mentoring a team of younger engineers and technical staff. Opportunity to work on wide range of water resources and civil engineering projects and develop career towards more project management or team managerial responsibilities. - Required Qualifications list (as above). - Skills: maybe we can extract from qualifications: software experience (HEC RAS, XPSWMM, HydroCAD, etc), ACAD Civil 3D or Microstation, site grading design, surface runoff management, detention design, conveyance, strong oral communication and technical writing, ability to work in team environment. - Benefits: Member-Owned, Paid Time Away (paid holidays, generous PTO, parental leave, professional development leave), Health Insurance (medical, dental, vision, FSA, HSA, Doctor On Demand, wellness reimbursement, mental health resources), Financial Health (life insurance, short- and long-term disability insurance, identity theft protection, many other benefits), Professional Growth (tuition assistance, professional society membership, more), Financial Rewards (company stock ownership, generous 401K match, incentive compensation, profit-sharing contributions to retirement 401K plans). Also earlier: flexible work options, competitive pay and great benefits, strong sense of community, chance to build meaningful long-term career. We need to include all that. We should not include boilerplate like EEO, AI tools, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must cut out the EEO statement, the AI tools paragraph, the "Click Here: A Great Place To Work Learn more about Stanley Consultants in this short video: Working at Stanley Consultants", the unsolicited resumes statement, the Equal Opportunity Employer paragraph, the AI tools paragraph, the final paragraph about salary range (though we might keep some of it? It says we should not create Pay section unless posting actually states them. The posting states that salary is competitive and will be determined, but no numbers. So we can maybe include a short p about pay being competitive? But the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It didn't say we cannot mention pay in a paragraph elsewhere. However, the "Pay" section is a heading we should not create. But we could include a short paragraph about pay being competitive within About the role or Benefits? Probably better to not include any pay details because they are vague and could be considered filler. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should avoid mentioning pay if it's not specific. So we can omit the pay paragraph. Similarly, schedule: hybrid is mentioned; we could include schedule info in a short p under About the role or maybe a separate Schedule section? But we should not create Schedule section unless posting actually states them. It does state hybrid work options, which is a schedule type. However, the instruction says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state hybrid work options, which is schedule. So we could create a Schedule section with that info. But we need to see if we have enough content for a Schedule section: just "Hybrid". That might be thin but it's real specific content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should not create a Schedule section for just hybrid; we could fold that into About the role or a short p. Similarly, Benefits: we have substantive content, so we create Benefits section. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to ensure we don't miss any substantive info. Let's draft:
About the role
Stanley Consultants is an award-winning and industry-leading global consulting engineering firm, with an unmatched commitment to culture, values, and ethics. We are dedicated to client experience and solve the most complex challenges to create a sustainable, connected, and enriched world for all. As the world changes, Stanley strategically evolves with it, integrating the latest technology, innovation, and resiliency practices. With over a century of experience serving the energy, federal government, transportation, and water sectors, we have helped improve lives and shape the infrastructure systems that connect us. As an employee-owned organization with a People First approach, we stand apart from other engineering consulting and services firms. At Stanley, your voice counts, your growth matters, and your success is our success. Stanley Consultants offers flexible work options, competitive pay and great benefits, a strong sense of community, and the chance to build a meaningful, long-term career! We are currently looking for a Water Resources Engineer for our Chicago or Minneapolis office. We are a team of water resource, geotechnical, structural, and civil engineers that deliver water resource engineering