Entry-Level Civil Engineer - Aviation - Hiring Event with AECOM - Boston
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. We need to preserve all substantive information. Let's parse the posting: Company Description: "Work with Us. Change the World..." This is generic description; maybe we can include as About AECOM? But we have a section "About AECOM" later. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not "About AECOM". But we could treat "About the role" as a heading for role description. The company description may be considered "About the role"? Actually "About the role" is typical heading for role overview. We could put company description under "About the role"? Might be okay. However we need to preserve all substantive info; we can include company description as a paragraph under maybe "About the role" or maybe we can create a heading "About AECOM"? Not in allowed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. So we should only use those headings. So we need to map content to those sections.
We have:
- About the role: could include overview of the hiring event, position description, location, start date, etc.
- Responsibilities: list of duties.
- Requirements: maybe minimum requirements.
- Qualifications: maybe preferred qualifications? Actually they have "Qualifications" section with Minimum Requirements and Preferred Qualifications. Could treat that as Qualifications.
- Skills: maybe specific skills like software, communication.
- Benefits: they have benefits description.
- Pay: they have compensation range.
- Schedule: maybe work schedule? Not explicitly given; they mention hybrid work model. Could be schedule? Not given. Might not include Schedule if no specific content.
We must not create sections with filler like "not specified". So if schedule not given, omit Schedule section.
We need to preserve all substantive info: include details about hiring event, date, location, networking mixer, interviews, etc. Also include that it's invitation-only hiring event in Boston Oct 21-22, 2026, for career opportunities starting Spring/Summer 2027. Also mention networking mixer Wednesday evening, interviews Thursday at Boston office. Also mention position: Entry-Level Civil Engineer - Aviation based in Rocky Hill, Connecticut, open to recent and Spring 2027 graduates, start as soon as available in Transportation Aviation Business Line. Also mention work involves planning, design, engineering, construction for airport projects etc. Also list responsibilities (the bullet list). Also qualifications: Minimum Requirements: Bachelor's degree in Civil Engineering or related field or demonstrated equivalency; US Citizenship required; Valid US Driver's License required; must pass Motor Vehicle Records review. Preferred Qualifications: Experience with Microsoft Office; Experience using AutoCAD/Civil 3D; Experience performing construction administration and inspection; Strong written and verbal communication skills; Ability to work in both office and field environment.
Additional Information: Relocation assistance not available; Sponsorship for US employment authorization not available; Day 1 onboarding in-person required; Offered rate based on education, qualifications, experience, work location; range $75,000 to $90,000.
Benefits: comprehensive benefits list.
Also "About AECOM" description: we could include under About the role? Or maybe we could treat as a separate section but not in allowed headings. Could we include it as a paragraph under About the role? Probably yes.
We must not include boilerplate like EEO, equal opportunity, scam-warning, etc. Also remove duplicated lines, navigation, cookie/legal. Also remove "ReqID: J10159601 Business Line: Transportation Business Group: DCS Strategic Business Unit: East Career Area: Engineering Work Location Model: Hybrid Compensation: USD 75000 - USD 90000 - yearly". This is metadata; we can fold minor metadata into short
or drop it. The compensation we already have in Pay section. Work location model hybrid could be mentioned maybe in About the role or Responsibilities? Could be a short paragraph. 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 event offers networking opportunities and interviews for career opportunities starting Spring/Summer 2027. The position is an Entry-Level Civil Engineer - Aviation based in Rocky Hill, Connecticut, open to recent and Spring 2027 graduates, with a start date as soon as available in the Transportation Aviation Business Line. The role involves planning, design, engineering, and construction for airport projects, including airfield safety, standards, improvement, and expansion programs. Work location model is hybrid.
Maybe also include company description? Could add a paragraph about AECOM's mission: "At AECOM, we're delivering a better world..." but that's generic; maybe we can include under About the role as well. But we must preserve all substantive info; the company description is substantive but maybe not required? It's part of posting. We'll include it.Responsibilities
- Conducts civil engineering design for airport projects.
- Completes designs, calculations, sketches, diagrams, schematics, and final working drawings for preparation of construction plans related to airport development projects including runways, taxiways, aprons, hangars, terminals, and other airport facilities.
- Prepares construction specifications for airport development projects per FAA Advisory Circular 150/5370-10 and State requirements.
- Prepares design reports, schedules, quantity takeoffs, and cost estimates.
- Collects and analyzes data to support design and construction phases of projects.
- Uses various computer software for design development and prepares plans in Civil 3D.
- Coordinates and collaborates with other airport/civil engineering, architectural, and engineering disciplines, sub-consultants, utility companies, permitting agencies, contractors, government and regulatory agencies, and clients.
- Performs construction administration and construction inspection.
- Performs work in accordance with agreed-upon budget and schedule.
Requirements
Minimum Requirements: Bachelor’s Degree in Civil Engineering, or related field or demonstrated equivalency of experience and/or education. Due to the nature of work, U.S. Citizenship is required for this role. Valid US Driver’s License required to visit project sites, clients, and other AECOM offices. As a condition of employment, selected candidate must pass a Motor Vehicle Records review.
Qualifications
Preferred Qualifications: Experience with Microsoft Office Software. Experience using AutoCAD/Civil 3D design software. Experience in performing construction administration and inspection. Strong written and verbal communication skills. Ability to work in both an office and field (construction) environment.
Maybe we could combine Requirements and Qualifications? But we have both sections.Skills
We could list specific skills: Microsoft Office, AutoCAD/Civil 3D, construction administration/inspection, communication, office/field work. But those are already in Qualifications. Might be redundant. Perhaps we can omit Skills section if content overlaps. But we need to include all substantive info; we could put skills under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one Qualifications section. But we already have Requirements separate. Let's think: The posting has "Qualifications" heading with Minimum Requirements and Preferred Qualifications. So we could treat that as Qualifications section, and not have separate Requirements. But we also need to include the minimum requirements (citizenship, driver's license, MVR). Those are part of Qualifications. So we can have a single Qualifications section containing both minimum and preferred. That would be more concise. Thus we could have:About the role
(overview)Responsibilities
Qualifications
(includes minimum and preferred)Benefits
Pay
We need to ensure we include all substantive info: hiring event details, position details, responsibilities, qualifications (min & pref), additional info (relocation not available, sponsorship not available, day 1 onboarding, compensation range), benefits description. We also need to include work location model hybrid maybe in About the role. We must not include sections like Schedule if not specified. Now craft HTML. Check for any duplicated lines: we should avoid repeating same sentences. Let's write:About the role
AECOM is hosting an exclusive, invitation-only hiring event in Boston on October 21‑22, 2026, offering networking mixers and interviews for career opportunities beginning Spring/Summer 2027. The role is an Entry‑Level Civil Engineer – Aviation based in Rocky Hill, Connecticut, open to recent and Spring 2027 graduates, with a start date as soon as available in the Transportation Aviation Business Line. The position involves planning, design, engineering, and construction for airport projects (airfield safety, standards, improvement, and expansion programs) and follows a hybrid work model.
Maybe also include AECOM's mission? Could add a sentence: "At AECOM, we're delivering a better world..." but that's generic; still substantive. Let's add a short sentence: "AECOM is the world's trusted infrastructure consulting firm, partnering with clients to solve complex challenges and build legacies for future generations." That's from company description. We'll include. Thus About the role paragraph could be two sentences. Now Responsibilities: we have list as above. Qualifications: combine minimum and preferred. We'll write:Qualifications
Minimum requirements: Bachelor’s degree in Civil Engineering or a related field (or demonstrated equivalency); U.S. citizenship required; valid U.S. driver’s license required; must pass a Motor Vehicle Records review.
Preferred qualifications: Experience with Microsoft Office; experience using AutoCAD/Civil 3D; experience performing construction administration and inspection; strong written and verbal communication skills; ability to work in both office and field environments.
We need to preserve all info: also mention that relocation assistance not available, sponsorship not available, Day 1 onboarding required. Where to put? Could be under Additional Information but we don't have a heading for that. Could add a paragraph under Qualifications or maybe under About the role? Better to add a separate section? Not in allowed headings. Could add a paragraph under Qualifications after preferred qualifications: "Additional information: Relocation assistance is not available for this position. Sponsorship for US employment authorization is not available now or in the future. All newly hired employees must attend an in‑person Day 1 onboarding at an AECOM office as a condition of employment." That seems fine. Now Benefits: we have a list of benefits. We'll output as- ...