Engineering Intern - AECOM Hiring Event - Arlington, VA

We need to output HTML fragment with sections: About the role? Actually we have job description content. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have: - About the role: Could be description of the event and internship. The posting includes description of event and internship. We can put that under About the role. - Responsibilities: list of duties. - Requirements: Minimum Requirements. - Qualifications: Preferred Qualifications? Actually they have Minimum Requirements and Preferred Qualifications. Could combine into Requirements and Qualifications sections. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map. - Skills: maybe from Preferred Qualifications: willingness to learn software, basic knowledge, communication skills. - Benefits: they talk about AECOM benefits comprehensive list. So include Benefits. - Pay: they have "Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $18 to $25." Also later "Compensation: USD 18 - USD 25 - hourly". So we have pay range. - Schedule: Not explicitly given. There's event dates but not schedule for internship. No schedule info. So we should not include Schedule section. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, legal, etc. Also remove navigation, cookie, duplicated lines, application instructions. Also remove "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process..." etc. Also remove "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's part of pay but we can keep the range. However that sentence is generic; we can keep the range but maybe drop the sentence if it's filler? It says "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's somewhat generic but still part of compensation description. Might keep but it's not specific. The instruction: 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. The sentence is not filler but it's generic. Might be okay to keep but we could just include the range. The range is specific: $18 to $25. So we can put that in Pay section. Benefits: they list many benefits. That's specific enough. Now we need to format:

About the role

... prose ...

Then

Responsibilities

• ... each duty

Then

Requirements

• ... minimum requirements

Then

Qualifications

• ... preferred qualifications

Then

Skills

• ... maybe communication skills etc

but we already have skills in preferred qualifications. Could combine? But we need separate sections if content exists. We have skills: willingness to learn industry-standard software, basic knowledge of industry-standard software (MS Excel, MS Word, Civil 3D/AutoCAD/MicroStation), strong written and verbal communication skills. That's skills. Then

Benefits

• ... list benefits

Then

Pay

The range for this position is $18 to $25 hourly.

maybe. We must not include schedule. We must preserve all substantive information. Let's extract details. Company description: Not needed? It's part of job posting but could be considered "About the role"? Might be okay to include in About the role paragraph. Job description: AECOM hosting exclusive invitation-only hiring event in Arlington on Nov 18-19, 2026. Opportunity to learn and connect for career opportunities starting Spring/Summer 2027. Event kicks off Wednesday evening with networking mixer 6-8 pm, hear from AECOM staff about projects, career paths, company. Meet other students, recent graduates, AECOM professionals. On Thursday, interviews at Arlington office. Fantastic opportunity to learn about and connect with AECOM for early career opportunities. AECOM seeking Engineering Intern based in Baltimore, MD. Position expected to begin Spring/Summer 2027. Internships offer students in undergrad and grad programs opportunity to gain valuable hands-on experience in engineering, design, infrastructure projects that make real-world impact. Interns work with cutting-edge technology, learn industry best practices, collaborate with experienced professionals in globally recognized firm. Program fosters technical and professional skill development while providing networking opportunities that can enhance future career prospects. Additionally, AECOM’s dedication to innovation and sustainability enables interns to contribute to meaningful projects that help shape communities and built environment. That's a lot of prose. We'll put in About the role. Responsibilities: list: - Perform assignments requiring the application of standard techniques, procedures and criteria to carry out engineering and/or management support tasks. - Assignments are designed to further develop judgement and understanding of professional and ethical responsibilities. - Work on a wide range tasks and assist with field research, data collection, data analysis, graphics, maps, and data presentation, and report development. - Assist in the design reviews of transportation roadway and infrastructure projects. - Provide basic support in the areas of design review and construction management for road and infrastructure construction. We need to keep each as

. Requirements (Minimum Requirements): - Candidates must be pursuing a Bachelor's Degree in Civil Engineering, Structural Engineering, Construction Management, Project Management or in another related field and must have completed at least 1 year of study. - Candidates who have recently graduated with a Bachelor's Degree and plan to continue with the Master's Degree are eligible to apply for these positions. - Recent graduates must have been enrolled in their Bachelor's Degree in the most previous school term with an interest in pursuing an advanced degree in the same or similar discipline at the conclusion of the internship. Qualifications (Preferred Qualifications): - Willingness and ability to learn industry-standard software pertinent to the position. - Basic knowledge of industry-standard software for the position (examples include software such as MS Excel, MS Word, Civil 3D/AutoCAD/MicroStation). - Strong written and verbal communication skills. Skills: Could be same as above? But we already used them. Perhaps we can treat "Skills" as the same list; but we need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put the same items under both Qualifications and Skills, we duplicate. Better to split: Qualifications could be the minimum requirements? Actually they have Minimum Requirements and Preferred Qualifications. So we could map Minimum Requirements to Requirements, Preferred Qualifications to Qualifications, and then Skills could be something else like "Strong written and verbal communication skills" but that's already in Preferred Qualifications. Could treat Skills as the communication skills and software knowledge? But that duplicates. Maybe we can combine: Use Requirements for Minimum Requirements, Qualifications for Preferred Qualifications, and skip Skills section (since no distinct skills beyond those). But we need to include Skills only if posting has real specific content for it. The posting does mention "Strong written and verbal communication skills" and "Willingness and ability to learn industry-standard software" and "Basic knowledge of industry-standard software". Those could be considered skills. So we could put those under Skills, and keep Qualifications for something else like "Minimum Requirements"? But they already have Minimum Requirements labeled as Minimum Requirements. The heading "Qualifications" could be used for Minimum Requirements? Actually typical job postings: Qualifications section includes both minimum and preferred. But we have separate headings: Requirements and Qualifications. We could put Minimum Requirements under Requirements, and Preferred Qualifications under Qualifications, and then Skills could be something else like "Strong written and verbal communication skills" but that's already in Preferred Qualifications. To avoid duplication, we could treat Skills as the communication skills only, and keep software knowledge under Qualifications. But that seems arbitrary. Better: Follow the instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. Let's map: - About the role: description of event and internship. - Responsibilities: list of duties. - Requirements: Minimum Requirements. - Qualifications: Preferred Qualifications (willingness to learn software, basic knowledge, communication skills). - Skills: maybe we could list specific software knowledge as skills? But that's already in Qualifications. Could we split: Qualifications: education-related? Actually they have Minimum Requirements (education) and Preferred Qualifications (software, communication). So we could put Minimum Requirements under Requirements, and Preferred Qualifications under Qualifications, and then Skills could be something like "Strong written and verbal communication skills" but that's already in Preferred Qualifications. Hmm. Maybe we can treat Qualifications as the education requirements (Minimum Requirements) and Skills as the software/communication preferences. That would avoid duplication. Let's see: Minimum Requirements are about degree and year of study. That's more like qualifications. Preferred Qualifications are about software and communication, which are skills. So we could assign: - Requirements: Minimum Requirements (education). - Qualifications: maybe we could leave empty? But we need to include only if posting has real specific content. The posting does have "Preferred Qualifications" which is specific content. So we need a section for that. Could call it Qualifications (as per heading) and put the Preferred Qualifications there. Then Skills could be something else like "Strong written and verbal communication skills" but that's already there. Could we split the Preferred Qualifications into two: software knowledge (skills) and communication skills (skills)? Actually both are skills. So maybe we put all Preferred Qualifications under Skills, and leave Qualifications empty (omit). But then we lose the heading "Qualifications" which is okay if no content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can omit Qualifications if we don't have distinct content for it beyond what we put elsewhere. However the posting explicitly labels "Preferred Qualifications". That is specific content. So we should include a section for it. The heading "Qualifications" matches that. So we put Preferred Qualifications under Qualifications. Then Skills: we could list specific technical skills like "MS Excel, MS Word, Civil 3D/AutoCAD/MicroStation". But that's already in Preferred Qualifications. However we could extract those as skills. But that would duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited explicitly, but it's redundant. Might be okay but better to avoid duplication. We could treat Skills as the software knowledge, and Qualifications as the willingness to learn and communication skills. But again duplication. Maybe we can combine: Under Qualifications we list both willingness to learn software, basic knowledge, communication skills. Then we omit Skills section because no additional distinct skills beyond those. That seems reasonable: we have captured all substantive info under Qualifications. The heading Skills would be empty, so we omit it. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check Benefits: they list many benefits. We'll put as

• ... each benefit

. Pay: we have range $18 to $25 hourly. We'll put in

The pay range for this position is $18 to $25 per hour.

Now we need to ensure we don't include boilerplate: EEO, legal, etc. Also remove "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process..." etc. Also remove "Offered rate of compensation will be based on individual education, qualifications, experience, and work location." That's generic; we can drop it because we already