Construction Intern – AECOM Hunt

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Company description: not needed? It's not a heading; we can include as

maybe under About the role? Actually "About the role" is a heading we can use for description of role. The posting includes "Job Description" with details about the intern role. So we can put that under

About the role

with paragraphs. Responsibilities: there is a list of responsibilities after "The responsibilities of this position include, but are not limited to:" then bullet list. So we can create

Responsibilities

with

• each. Requirements: there is "Qualifications Minimum Requirements:" and "Preferred Qualifications:" So we can combine under

  Requirements

  maybe with subheadings? But we only allowed headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for minimum requirements, Qualifications for preferred? Or we could put both under Qualifications. The instruction: Use headings for those categories. We need to decide mapping. We have "Qualifications Minimum Requirements:" and "Preferred Qualifications:" So we can have

  Qualifications

  with two subsections? But we cannot add extra headings beyond those listed? It didn't forbid extra headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed headings. So we should stick to those. We can put minimum requirements under Requirements heading, and preferred qualifications under Qualifications heading. Or we could combine both under Qualifications and omit Requirements. But we have both minimum and preferred; better to split: Requirements for minimum, Qualifications for preferred. Skills: there is "Microsoft Office proficiency (Word, Excel, and Outlook), as well as exposure to other construction-based computer programs." Also "Experience working for a general contractor. Previous relevant internship experience. Exposure to other construction-based computer programs." Those could be skills. We'll put under Skills. Benefits: there is a paragraph about AECOM benefits: medical, dental, vision, etc. So we can include Benefits. Pay: not mentioned. So omit. Schedule: not mentioned (just start Summer 2027, but not schedule details). So omit. We also need to include location? Not a heading; we can include in About the role paragraph. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement etc. Remove that. Also remove "ReqID: J10160588 Business Line: ..." maybe minor metadata; we can fold 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 can include a short paragraph with that info. We must not repeat the job title as a heading. The job title is Construction Intern; we should not have a heading for it. We need to output only HTML fragment. Let's craft:

  About the role

  AECOM Hunt is seeking a Construction Intern to be based in Cleveland, OH working on the Cleveland Browns project. The position is expected to begin in Summer 2027.

  ReqID: J10160588; Business Line: CM Construction Management; Business Group: CM Strategic Business Unit: CM; Career Area: Construction; Work Location Model: On-Site.

  Then Responsibilities. We need to list each responsibility as
• . The responsibilities list is long; we need to preserve all. Let's extract them: - Perform a variety of assignments designed to develop professional construction management knowledge and capabilities, applying standard techniques, procedures, and project processes under the direction of experienced project staff. - Support Project Managers, Superintendents, Project Engineers, and other project team members with day-to-day construction management and field activities. - Assist with the planning and coordination of subcontractor activities within an assigned area of responsibility. - Support field teams in monitoring construction activities for conformance with project plans, specifications, schedules, quality standards, and safety requirements. - Assist with reviewing project documentation, including drawings, specifications, RFIs, submittals, project logs, daily reports, and other construction records. - Utilize construction management systems and project technology to support documentation, record keeping, communication, and project tracking. - Assist with monitoring project schedules, work sequences, manpower, material deliveries, equipment requirements, and other project planning activities. - Support coordination and communication between field management, project management, estimating, procurement, subcontractors, suppliers, architects, engineers, and other project stakeholders. - Participate in jobsite meetings, coordination meetings, site walks, inspections, and other project activities as appropriate. - Assist project teams with quality control efforts by observing construction activities and helping verify that work is completed in accordance with project requirements. - Support implementation of project safety programs and become familiar with company policies, procedures, and applicable OSHA requirements. - Assist with preparation of reports, logs, meeting documentation, and other project deliverables while keeping assigned supervisors informed of progress. - When appropriate, interact with owners, architects, design professionals, subcontractors, and other project partners under the guidance of project leadership. - Follow direction from senior staff, manage assigned tasks through completion, and meet required schedules while producing accurate, quality work. - Continuously expand professional knowledge of construction operations, project management, technology, safety, quality, and other areas of the business. - Interns are assigned duties intended to provide a broad, well-rounded learning experience within their field of study. - Responsibilities will vary by project, location, phase of construction, and individual experience level. We need to ensure we don't lose any. Now Requirements (minimum): - Candidates must be pursuing a bachelor’s degree in construction management, civil engineering and/or similar discipline 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. Now Qualifications (preferred): - Experience working for a general contractor. - Previous relevant internship experience. - Exposure to other construction-based computer programs. - Microsoft Office proficiency (Word, Excel, and Outlook), as well as exposure to other construction-based computer programs. Note there is duplication of exposure to other construction-based computer programs; we can keep both but maybe combine? We should preserve all substantive information; duplication is okay but we could deduplicate? The instruction: remove duplicated lines. So we should remove duplicated lines. The line "Exposure to other construction-based computer programs." appears twice (once in Experience working for a general contractor? Actually it's separate bullet: "Experience working for a general contractor." then "Previous relevant internship experience." then "Exposure to other construction-based computer programs." then "Microsoft Office proficiency (Word, Excel, and Outlook), as well as exposure to other construction-based computer programs." So the exposure appears twice; we should keep only one instance. We'll keep the one with Microsoft Office proficiency mention? Actually the second includes Microsoft Office proficiency plus exposure. So we can keep that and drop the standalone exposure line. Thus Qualifications list: - Experience working for a general contractor. - Previous relevant internship experience. - Microsoft Office proficiency (Word, Excel, and Outlook), as well as exposure to other construction-based computer programs. Now Skills: we might not need separate if we already covered skills in Qualifications. But we have a Skills heading possible. However the qualifications already include skills. The instruction: Use headings for those categories; we can still have Skills if there is content distinct from Qualifications. But we might combine. To avoid thin sections, we could omit Skills and put those under Qualifications. However we already used Qualifications for preferred qualifications. The skills are essentially same as preferred qualifications. Might be okay to not have Skills section. But we have Benefits: we need to include. Benefits paragraph: "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." We should keep that. Now we need to ensure we removed boilerplate: EEO statement, etc. Also remove "At AECOM, we are committed to maintaining a secure and trustworthy recruitment process..." etc. Also remove "About AECOM" paragraph? That's company description but not required as heading; we could include as part of About the role? But it's more about company. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company description? It's substantive but not about the role. However we have no heading for company description; we could include as a

  before About the role? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

  for section headings (e.g. ...). It might be okay to include other headings but they'd be non-standard. Safer to stick to those headings and put company description in a

  under About the role or as a separate

  before any heading. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings, but to be safe we can include company description as a

  before the About the role heading. Thus final HTML:

  AECOM, we're delivering a better world. Whether improving your commute, keeping the lights on, providing access to clean water, or transforming skylines, our work helps people and communities thrive. We are the world's trusted infrastructure consulting firm, partnering with clients to solve the world’s most complex challenges and build legacies for future generations. There has never been a better time to be at AECOM. With accelerating infrastructure investment worldwide, our services are in great demand. We invite you to bring your bold ideas and big dreams and become part of a global team of over 50,000 planners, designers, engineers, scientists, digital innovators, program and construction managers and other professionals delivering projects that create a positive and tangible impact around the world. We're one global team driven by our common purpose to deliver a better world. Join us.

  Then About the role heading etc. But that is a lot of text; we need to preserve all substantive information. The company description is substantive. So include. Now after that we have About the role heading with role description and metadata. Now Responsibilities heading with ul. Now Requirements heading with ul. Now Qualifications heading with ul. Now Benefits heading with p. We must not include Pay or Schedule. Now ensure we didn't include any boilerplate like EEO, etc. Let's craft final HTML. Check for any duplicated lines: we removed duplicate exposure line. Check for any remaining boilerplate: The "About Construction Management – AECOM Hunt" section is substantive about the company's hunt division; we should preserve. Where to put? It's about the company division; could be included in About the role or as a separate

  after About the role? It's not a heading but we can include as a <