Bridge Engineering Intern II

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. We need to parse the job posting. Company description: not needed? It's part of description but maybe we can include as About the role? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can create sections accordingly. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to include sections only when posting has real specific content. Let's extract content: - Job Description: AECOM is seeking a Bridge Engineering Intern to join our team in Louisville, KY. This position is expected to begin in May 2027. The responsibilities of this position include, but are not limited to: Internships are designed to introduce and build essential, hands on skills that differ from those attained in the academic arena and help to enhance the transition from student to professional. Interns are assigned duties that will provide a broad, well-rounded learning experience within their field of study Intern 2 – completion of second year of qualified study So responsibilities: basically description of internship purpose. Could list bullet points? Not explicit list. Might treat as prose. - Qualifications Minimum Requirements: Candidate must be currently pursuing a Bachelor’s degree in Civil Engineering and must have completed at least two years 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. Valid U.S. 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. - Preferred Qualifications: Familiarity with the basics of engineering Familiarity with engineering software such as AutoCAD and/or Bentley MicroStation Strong communication skills - Additional Information: Sponsorship for U.S. employment authorization is not available for this position. Relocation assistance is not available for this role. At AECOM, we are committed to maintaining a secure and trustworthy recruitment process and take any fraudulent hiring activity seriously. To support this commitment, all newly hired employees are required to attend an in-person Day 1 onboarding at an AECOM office location as a condition of employment. - Offered rate of compensation will be based on individual education, qualifications, experience, and work location. The range for this position is $20.31 to $27.92. - About AECOM: description of company, benefits, etc. - Benefits: AECOM is proud to offer comprehensive benefits... list many. - What makes AECOM a great place to work: description. - ReqID etc: drop. - Compensation line at bottom: USD 20.31 - USD 27.92 - hourly (duplicate). We need sections: About the role (maybe job description), Responsibilities, Requirements (maybe Minimum Requirements), Qualifications (maybe Preferred Qualifications), Skills (maybe from preferred?), Benefits, Pay, Schedule (if any schedule info? Not present). So we may omit Schedule. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's craft sections:

About the role

AECOM is seeking a Bridge Engineering Intern to join our team in Louisville, KY. This position is expected to begin in May 2027.

Responsibilities

Internships are designed to introduce and build essential, hands‑on skills that differ from those attained in the academic arena and help to enhance the transition from student to professional. Interns are assigned duties that will provide a broad, well‑rounded learning experience within their field of study. (Intern 2 – completion of second year of qualified study)

Maybe we could also include that responsibilities include but not limited to: but we already captured.

Requirements

Candidate must be currently pursuing a Bachelor’s degree in Civil Engineering and must have completed at least two years of study. Candidates who have recently graduated with a Bachelor’s degree and plan to continue with a Master’s degree are eligible to apply. Recent graduates must have been enrolled in their bachelor’s degree in the most recent school term with an interest in pursuing an advanced degree in the same or similar discipline at the conclusion of the internship. A valid U.S. Driver’s License is required to visit project sites, clients, and other AECOM offices. As a condition of employment, the selected candidate must pass a Motor Vehicle Records review.

Qualifications

Preferred qualifications include familiarity with the basics of engineering, experience with engineering software such as AutoCAD and/or Bentley MicroStation, and strong communication skills.

Maybe Skills section could be same as Qualifications? But we can keep Qualifications as preferred qualifications and maybe Skills separate? The instruction list includes Skills as possible heading. We could put the preferred qualifications under Skills. But we already have Qualifications for minimum requirements; we could rename sections: Requirements = Minimum Requirements, Qualifications = Preferred Qualifications, Skills maybe not needed. However we need to avoid thin sections. Could combine Qualifications and Skills? But we need to follow instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to include only those with content. We have content for About the role, Responsibilities, Requirements (minimum), Qualifications (preferred), Benefits, Pay. No Schedule. We could also include Skills as separate if we want to list specific skills like AutoCAD, MicroStation, communication. But that's already in Qualifications. Might be redundant. Better to put those under Skills and keep Qualifications for education? But we already used Requirements for education. Let's think: - Requirements: Minimum requirements (education, driver's license, MVR). - Qualifications: Preferred qualifications (familiarity with basics of engineering, software, communication). - Skills: maybe we could list specific technical skills: AutoCAD, Bentley MicroStation, communication. But that duplicates. Given instruction to prefer few substantive sections over many thin ones, we could combine Qualifications and Skills into one section called Qualifications (or Skills). But we need to follow heading examples; not mandatory to use all. So we can have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That seems fine. Now Benefits: need to list benefits from AECOM description: 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, employee stock purchase plan. We should put as

• each. Pay: The range $20.31 to $27.92 hourly. Also mention based on education etc. We'll include that. We must not include duplicated lines like compensation line at bottom. Now ensure we removed boilerplate: EEO, etc. Also removed "About AECOM" description that is more company overview; we might incorporate into Benefits? Actually "About AECOM" includes description of company and benefits. We already captured benefits. The rest of About AECOM is generic company description; could be considered boilerplate? It's not exactly boilerplate but it's company overview. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview may be considered not boilerplate but maybe not needed for job posting? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep substantive info about AECOM? The "About AECOM" paragraph includes info about being global infrastructure leader, revenue, etc. That's substantive. Should we include? Possibly under About the role or a separate section like "About the company". But we only have headings list; we could add a section "About the company" but not in list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could add other headings if needed. However they said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we could also add other headings if needed but better to stick to those. Thus we could incorporate company overview into About the role? Might be okay. But About the role currently just short description. Could expand to include company overview: "AECOM is the world's trusted infrastructure consulting firm..." etc. That would be substantive. Thus About the role section can contain both role description and company overview. Let's craft About the role:

  AECOM is seeking a Bridge Engineering Intern to join our team in Louisville, KY. This position is expected to begin in May 2027. AECOM is the world's trusted infrastructure consulting firm, delivering a better world through projects in transportation, water, environment, energy, and buildings. With over 50,000 professionals worldwide and revenue of $16.1 billion in FY 2025, AECOM offers a global team driven by a common purpose to deliver a better world.

  That preserves company description. Now Responsibilities as earlier. Requirements as earlier. Qualifications (preferred) as earlier. Benefits as list. Pay as paragraph. Now ensure no duplicated content: we included compensation range only once. Check for any leftover boilerplate: we removed EEO, sponsorship, relocation assistance, Day 1 onboarding, fraudulent hiring activity, etc. Those are considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Sponsorship, relocation assistance, Day 1 onboarding are not exactly those categories but could be considered "Additional Information". Are they substantive? They are specific to the role: no sponsorship, no relocation assistance, required Day 1 onboarding. Should we keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep those details unless they are considered boilerplate. They are not EEO or legal; they are specific to the role. So we should keep them. However they might be considered "Additional Information". We could add a section "Additional Information" but not in the list. Could we incorporate into Requirements or Qualifications? Probably better to add a separate section "Additional Information". But the instruction only gave examples; not strict. However to be safe, we could add a section with heading

  Additional Information

  . The instruction didn't forbid other headings; it just gave examples. It said "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use h3 for any section headings, and the examples are typical. So we can add Additional Information. Thus we need to include that info: Sponsorship for U.S. employment authorization is not available. Relocation assistance is not available. All newly hired employees required to attend an in-person Day 1 onboarding at an AECOM office location as a condition of employment. Also maybe mention "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process and take any fraudulent hiring activity seriously." That could be considered boilerplate? It's a statement about recruitment process; maybe not needed but it's substantive? It's a generic statement; could be considered boilerplate. I'd lean to remove as it's generic.