Engineering Intern - Highway/Roadway Transportation

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Company description: not needed? It's part of description but we can include maybe as "About the role"? Actually "About the role" is a heading we can use for description of role. The posting includes "Job Description AECOM is seeking an Engineering Intern to be based in Saint Louis, MO. This position is expected to begin in May 2027." That's about the role. Also "Internships are designed to introduce..." etc. So we can put that under About the role. Responsibilities: The posting says "The responsibilities of this position include, but are not limited to:" then a paragraph about internships. It doesn't list bullet duties. So we have a paragraph describing responsibilities. Could be placed under Responsibilities as

. No list. Qualifications: There's a "Qualifications" heading in posting with Minimum Requirements and Preferred Qualifications. So we can have a Qualifications section with subheadings? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put Minimum Requirements and Preferred Qualifications under Qualifications as

• . Also we could separate Requirements vs Qualifications? The posting has "Minimum Requirements:" and "Preferred Qualifications:" So we could put Requirements section for minimum requirements, and Qualifications section for preferred? But guidelines: Use headings as given. We can decide to put minimum requirements under Requirements, and preferred qualifications under Qualifications. Or combine both under Qualifications. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings as appropriate. We need to include a section only when posting has real specific content for it. We have content for About the role (description). Responsibilities (description). Requirements (minimum requirements). Qualifications (preferred qualifications). Skills maybe could be derived from preferred qualifications (proficiency with MS Office, CADD, organizational, technical, communication skills). Could put under Skills. Benefits: posting mentions "About AECOM AECOM is proud to offer comprehensive benefits..." then lists many benefits. So we have benefits content. Pay: posting includes "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." Also later "Compensation: USD 20.31 - USD 27.92 - hourly". So we have pay. Schedule: Not mentioned explicitly. There's "Work Location Model: Hybrid". No schedule. So we should not include Schedule section. We must not include boilerplate like EEO, etc. Remove duplicated lines, navigation, cookie, legal, etc. Also remove "ReqID: J10159787 Business Line: Transportation Business Group: DCS Strategic Business Unit: West Career Area: Engineering Work Location Model: Hybrid Compensation: USD 20.31 - USD 27.92 - hourly". That's metadata; we can fold minor metadata into a short

  or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a short paragraph at top maybe with location and start date? But we already have that in About the role. The metadata like ReqID etc can be dropped. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: location Saint Louis, MO; start May 2027; responsibilities paragraph; minimum requirements: pursuing Bachelor's in Civil Engineering with roadway design focus, completed at least two years; recent graduates with Bachelor's planning to continue Master's eligible; recent graduates must have been enrolled in most previous school term with interest in pursuing advanced degree; US Citizenship required. Preferred qualifications: proficiency with MS Office Suite (Word, Excel, PowerPoint); basic knowledge of CADD and industry standard computer software (AutoCAD or MicroStation); strong organizational, technical and communication skills; ability to work independently or within a team environment. Benefits: list: 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. Pay: range $20.31 to $27.92 hourly. We should not include "About AECOM" description that repeats company description? The posting includes "About AECOM AECOM is proud to offer comprehensive benefits..." then later "About AECOM AECOM is the global infrastructure leader..." That's some duplication. We need to preserve substantive info but not repeat duplicated lines. We can combine benefits description and company overview maybe under Benefits and maybe a brief About AECOM? But we don't have a heading for "About the company". Not required. We could include a short paragraph under Benefits that includes the benefits list. The company description about being global infrastructure leader maybe not needed for any section; but it's substantive. Could we put it under About the role? That section is about the role, not company. Might be better to include a separate section? Not in allowed headings. Could we put it under About the role as additional context? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings? It says use those for section headings. Likely we should only use those headings. So we should not add other headings. So we need to fit company description somewhere maybe under About the role? But About the role is for role description. Could we incorporate company description into About the role as a brief intro? Might be okay but risk of not being specific to role. However we must preserve all substantive information; we could include it as a

  under About the role before role specifics. That would preserve it. Alternatively we could put company description under Benefits? No. Better: we could treat "About AECOM" as part of Benefits? Not really. Given instruction to preserve all substantive information, we need to include it somewhere. Since we cannot add extra headings, we can put it as a

  before the first heading or after. The instruction says output ONLY the HTML fragment; we can have multiple sections; we can also have stray

  not under a heading? It didn't forbid. It said use

  for section headings,

  • for any list,

    for prose. So we can have

    elements anywhere. So we can include a

    with company overview before the headings. Thus structure:

    Company description paragraph(s)

    About the role

    AECOM is seeking an Engineering Intern to be based in Saint Louis, MO. This position is expected to begin in May 2027. 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.

    Responsibilities

    The responsibilities of this position include, but are not limited to: Interns will gain hands-on experience, assist with roadway design tasks, support project teams, etc? Wait the posting didn't list specific duties beyond the generic description. It only said "The responsibilities of this position include, but are not limited to:" then the paragraph about internships. So we should keep that exact sentence? The paragraph after colon is the same as earlier? Actually the posting: "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." So we can put that as a

    under Responsibilities.

    Requirements

    • Must be pursuing a Bachelor’s degree in Civil Engineering with roadway design focus
    • Must have completed at least two years of study
    • Recent graduates with a Bachelor’s degree who plan to continue with a Master’s degree are eligible
    • 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
    • US Citizenship is required

    Qualifications

    • Proficiency with Microsoft Office Suite, including Word, Excel, and PowerPoint
    • Basic knowledge of CADD and industry standard computer software for the position (examples include software such as AutoCAD or MicroStation)
    • Strong organizational, technical and communication skills
    • Ability to work independently or within a team environment

    Skills

    We could also list skills but they overlap with Qualifications. Perhaps we could put the technical skills under Skills: proficiency with MS Office, CADD, organizational, technical, communication skills. But we already have them under Qualifications. To avoid duplication, maybe we combine Qualifications and Skills? But we need to follow instruction: use headings only when posting has real specific content. The posting has "Preferred Qualifications:" which includes those items. So we can treat that as Qualifications. Skills could be omitted if no separate skills section. However we might still include Skills if we want to separate out soft skills? But risk of duplication. Better to not include Skills section if no distinct skills beyond those already captured. The instruction: "Prefer a few substantive sections over many thin ones." So we can skip Skills.

    Benefits

    • 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

    Pay

    The 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 per hour.

    We should also include location and start date maybe in About the role. Already there. We need to ensure we didn't include any boilerplate like EEO, etc. We removed. Check for duplicated lines: we have not repeated the company description about being global infrastructure leader etc. We omitted that. Is that substantive? It's about AECOM being global infrastructure leader, revenue, etc. That is substantive but not covered in any section. Should we include it? The instruction says preserve ALL substantive information. So we need to include that info somewhere. Could we add a

    after Benefits maybe under a heading like "About AECOM"? Not allowed heading. Could we add a

    without heading? Yes we can have stray

    . So we can add a

    with that info after Benefits or before Pay. That would preserve it. Thus after Benefits, add a

    with: "AECOM is the global infrastructure leader, committed to delivering a better world. As a trusted professional services firm powered by deep technical abilities, we solve our clients’ complex challenges in water, environment, energy