Entry-Level Engineer - Water - Hiring Event with AECOM – Boston, MA
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse the posting.
Company description: not needed? It's part of job description but we can include as "About the role"? Probably "About the role" could contain description of role and event. The posting includes: "AECOM is hosting an exclusive, invitation-only hiring event in Boston on October 21-22, 2026. This is a great opportunity to learn and connect with AECOM for career opportunities starting Spring/Summer 2026. The event kicks off on Wednesday evening with a networking mixer, where you can hear from AECOM staff about various projects, career paths, and the company itself. You’ll also have the chance to meet other students, recent graduates, and AECOM professionals from across our business lines. On Thursday, interviews will take place at our Boston office. This is a fantastic opportunity to learn about and connect with AECOM for early career opportunities. AECOM’s Water Business Line is seeking a talented Entry-Level Engineer to support water, water resources, and wastewater treatment and distribution projects. We are hiring in our offices throughout the Northeast including Boston, Chelmsford, and Cape Cod, MA; Rocky Hill, CT; Buffalo, NY; Philadelphia and Conshohocken, PA; and Newark, DE. This position offers a unique opportunity to work within an established and successful regional and national group that offers a diverse range of technical challenges and career development opportunities. Join our team while we continue to deliver innovative and successful projects and help the communities in which we live and work."
That's about the role. So we can put that in About the role
with paragraphs.
Responsibilities: list bullet points after "The responsibilities of this position include, but are not limited to:" then bullet list.
Qualifications: there is a "Qualifications" heading with Minimum Requirements and Preferred Qualifications. We can treat that as Requirements? Actually we have separate sections: Requirements, Qualifications, Skills. The posting includes Minimum Requirements and Preferred Qualifications. We could map Minimum Requirements to Requirements, Preferred Qualifications to Qualifications, and maybe Skills from bullet list of abilities.
But we need to follow instruction: Use headings for those specific names if content exists. We have content for Responsibilities, Requirements (minimum), Qualifications (preferred), Skills (maybe from preferred qualifications list includes skills). Benefits: there is a paragraph about benefits under "About AECOM" and "What makes AECOM a great place to work". That includes benefits description. Pay: there is compensation range "$76000 to $90000". Also later "Compensation: USD 76000 - USD 90000 - yearly". So we have pay info. Schedule: not mentioned explicitly; maybe hybrid work model mentioned: "Work Location Model: Hybrid". That's not schedule but location model. No schedule info like full-time, part-time. So we should not create Schedule section.
We must not include boilerplate like EEO, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "ReqID: J10159566 Business Line: Water Business Group: DCS Strategic Business Unit: East Career Area: Engineering Work Location Model: Hybrid Compensation: USD 76000 - USD 90000 - yearly". But we need to keep compensation info; we can extract that into Pay section. The work location model maybe not needed.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like locations list, responsibilities list, qualifications, etc.
We must not repeat the job title as a heading (the page already shows it). So no heading for job title.
We must not put Job ID/requisition numbers as headings; fold minor metadata into a short
or drop it. So we can drop ReqID etc. We need to output only HTML fragment, no /, no markdown fences. Let's structure:
About the role
AECOM is hosting an exclusive, invitation-only hiring event in Boston on October 21-22, 2026. This is a great opportunity to learn and connect with AECOM for career opportunities starting Spring/Summer 2026. The event kicks off on Wednesday evening with a networking mixer, where you can hear from AECOM staff about various projects, career paths, and the company itself. You’ll also have the chance to meet other students, recent graduates, and AECOM professionals from across our business lines. On Thursday, interviews will take place at our Boston office. This is a fantastic opportunity to learn about and connect with AECOM for early career opportunities. AECOM’s Water Business Line is seeking a talented Entry-Level Engineer to support water, water resources, and wastewater treatment and distribution projects. We are hiring in our offices throughout the Northeast including Boston, Chelmsford, and Cape Cod, MA; Rocky Hill, CT; Buffalo, NY; Philadelphia and Conshohocken, PA; and Newark, DE. This position offers a unique opportunity to work within an established and successful regional and national group that offers a diverse range of technical challenges and career development opportunities. Join our team while we continue to deliver innovative and successful projects and help the communities in which we live and work.
Responsibilities
- Perform assignments requiring the application of standard techniques, procedures, and criteria to carry out engineering tasks.
- Assignments are designed to further develop judgment and understanding of professional and ethical responsibilities.
- Exercise judgment limited to developing details of work in making preliminary selections and adaptations of engineering alternatives.
- Prepare engineering-related calculations and develop drawings and visual aids.
- Prepare design drawings, plans, sections, details, and profiles/sections within the Autodesk Civil 3D and AutoCAD MEP, Revit.
- Work under the supervision of a project manager or senior-level team member.
- Water and/or Wastewater treatment evaluation and design.
- Pump station evaluation and design.
- Water distribution system hydraulic modeling, analysis, and design.
- Sewer collection system evaluation and design.
- Stormwater modeling, analysis, and design.
- Willingness and ability to occasionally travel to sites in the northeastern US and offices throughout the Northeast.
Requirements
Minimum Requirements: Bachelor’s degree in Civil Engineering, Environmental Engineering, Construction Management, or a related field. Must have a valid U.S. driver’s license and as a condition of employment, must be able to pass AECOM’s Motor Vehicle Records review. Basic knowledge of industry-standard computer software for the position. (examples include software such as CADD, HCS, AutoCAD, MicroStation, GIS, and Hydrologic/Hydraulic modeling).
Qualifications
Preferred Qualifications: Engineer-in-Training (EIT) or Fundamentals of Engineering (FE). GIS and CAD skills. Capable of using spreadsheet, word processing, and standard office software. Detail-oriented while still able to understand/comply with the big picture/goals of a project. Ability to multi-task. Strong logic and writing skills. Documents time and effort accurately. Ability to work productively in a team environment. Good verbal and written communication skills. Flexible – can adapt to shifting priorities/work schedules. Able to work independently. Self-learner. Can take directions from others and in turn can guide others.
We could also have a Skills section but the preferred qualifications already cover skills. The instruction says use headings for Skills if posting has real specific content. We could extract skills from preferred qualifications: GIS and CAD skills, spreadsheet, word processing, standard office software, detail-oriented, multi-task, strong logic and writing skills, documents time and effort, teamwork, communication, flexible, independent work, self-learner, taking direction, guiding others. But that's essentially same as qualifications. To avoid duplication, maybe we combine them into Qualifications and not create Skills. But we need to decide if we should create Skills section. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to decide if there is specific content for Skills beyond what's in Qualifications. The posting includes "Preferred Qualifications" which includes many skill-like items. Could treat that as Skills section. But we already have Qualifications heading for preferred qualifications. The Minimum Requirements could be Requirements. So we have both Requirements and Qualifications. Skills could be redundant. However, we could still create a Skills section pulling out the skill-related items from Preferred Qualifications, but that would duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicating is not inventing but repeating; is that allowed? It might be okay but could be considered redundant. Better to not duplicate; we can treat the Preferred Qualifications as Qualifications and not create Skills. Since we already have Qualifications section, we can skip Skills.
Benefits: There is a paragraph under "About AECOM" describing benefits: "AECOM is proud to offer comprehensive benefits to meet the diverse needs of our employees. Depending on your employment status, AECOM benefits may include medical, dental, vision, life, AD&D, disability benefits, paid time off, leaves of absences, voluntary benefits, perks, flexible work options, well-being resources, employee assistance program, business travel insurance, service recognition awards, retirement savings plan, and employee stock purchase plan." Also later "What makes AECOM a great place to work" includes more about growth, training, etc. That's also benefits-ish but we can include the benefits paragraph.
Thus we add:
Benefits
AECOM is proud to offer comprehensive benefits to meet the diverse needs of our employees. Depending on your employment status, AECOM benefits may include medical, dental, vision, life, AD&D, disability benefits, paid time off, leaves of absences, voluntary benefits, perks, flexible work options, well-being resources, employee assistance program, business travel insurance, service recognition awards, retirement savings plan, and employee stock purchase plan.
Pay: we have compensation range.Pay
The range for this position is $76,000 to $90,000 per year.
We should keep the exact phrasing: "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $76000 to $90000." Also later "Compensation: USD 76000 - USD 90000 - yearly". We'll combine. We need to preserve all substantive information; we can include both sentences. Thus:Pay
Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $76000 to $90000.
We could also mention yearly but it's implied. Schedule: not present, so omit. Now ensure we didn't include boilerplate: we removed EEO, etc. Also removed "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process..." that's boilerplate? It's about fraudulent hiring activity; could be considered boilerplate but maybe it's substantive? It's about recruitment process; but it's likely boilerplate. Safer to remove. Also removed "All newly hired employees are required to attend an in-person Day 1 onboarding at an AECOM office location as a condition of employment."