Intern Engineer - Summer 2027

We need to output HTML fragment with sections only where there is real specific content. The posting includes: - Intro paragraph: "What We're Looking For At HNTB..." includes description. Could be considered "About the role" or maybe not a heading. We can treat as a

after maybe a heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to decide which sections to include based on content. We have: - "What We're Looking For" could map to "About the role". It contains description of company and role. - "What You’ll Do" -> Responsibilities. - "What You’ll Need" -> Requirements (or Qualifications). It lists High School Diploma/GED plus current enrollment. - "What You’ll Bring" -> Skills? It lists abilities. - "What We Prefer" -> Preferred Qualifications (maybe Skills or Qualifications). Could be under "Qualifications" or "Preferred Qualifications". Since we have limited headings, we could combine Requirements and Qualifications? But we need to follow instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple. We have no explicit Benefits, Pay, Schedule content. There's a link "Click here for benefits information: HNTB Total Rewards" but that is not specific benefit details; it's a link. According to instruction: never create Benefits section unless posting actually states them. It only says "Click here for benefits information". That's not stating benefits; it's a link. So we should not include Benefits section. Similarly no Pay or Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills? Might be overlapping. We could map: - About the role: intro paragraph. - Responsibilities: "What You’ll Do" bullet list. - Requirements: "What You’ll Need" (high school diploma/GED + enrollment). - Qualifications: maybe "What You’ll Bring" (skills/abilities). Or we could treat "What You’ll Bring" as Skills. - Preferred: "What We Prefer" could be under Qualifications as preferred qualifications. But we need to avoid duplicate or thin sections. Perhaps combine Requirements and Qualifications into one "Requirements" section that includes both required and preferred? But instruction says prefer a few substantive sections over many thin ones. So we could have: - About the role (intro) - Responsibilities - Requirements (includes required qualifications, preferred qualifications, skills) But we also have separate list of skills under "What You’ll Bring". Could be included in Requirements. Thus we can have three sections: About the role, Responsibilities, Requirements. Let's extract content precisely, preserving all substantive information, no boilerplate. We need to remove cookie/navigation/legal/EEO etc. So we strip everything after "Additional Information" etc. Also remove lines like "Click here for benefits information: HNTB Total Rewards", "Click here to learn more about Equal Opportunity Employer/Disability/Veteran Visa sponsorship is not available for this position." etc. Also remove hashtags, locations? Locations might be considered substantive? It lists locations: Harrisburg, PA, King of Prussia, PA (Norristown), Philadelphia, PA (Pennsylvania), Pittsburgh, PA. That is substantive info about where the job is. Should we include? Possibly under About the role or a separate section? There's no heading for Locations in allowed list. Could we include as a paragraph under About the role? The instruction says we can only use those headings; we cannot create a Locations heading. So we need to fold location info into a paragraph, maybe under About the role or Responsibilities? Probably About the role. Also we have "Relocation and housing are NOT provided for these positions." That's substantive; should be kept. We also have "Job Type: Intern Full/Part Time: Full time Job Category: Engineering Group ReqID: R-31649 #college". We should drop Job ID/requisition numbers as headings; fold minor metadata into a short

or drop it. So we could include a short paragraph with Job Type, Full/Part Time, Job Category maybe. But those are metadata; we could drop them as per 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, but maybe better to drop as it's minor. However we need to preserve ALL substantive information; is job type substantive? It says Intern, Full time. That's substantive. So we should keep it but maybe as a short paragraph. We also have "#MD #Bridges, #ConstructionManagement, #Highways, #ProjectControls, #Traffic, #TransitAndRail" hashtags; those are likely tags, not substantive; could drop. We need to preserve all substantive information: description, responsibilities, requirements, skills, preferred, relocation note, locations, job type, full/part time, job category. Let's structure:

About the role

At HNTB, you can create a career that is meaningful to you while building communities that matter to all of us. For more than a century, we have been delivering solutions for some of the largest, most complex infrastructure projects across the country. With our historic growth, it is an exciting time to join our team of employee-owners. This opportunity entails being responsible for assisting assigned department(s) and/or project(s) by performing basic engineering related tasks which may reflect elements of standard post-secondary engineering curriculum. Our Philadelphia, King of Prussia, Harrisburg, and Pittsburgh, PA offices are seeking Intern Engineers for Summer 2027 in the following areas: Structures, Roadway, Traffic, Track, Rotational (Structures/Track/Transportation), Construction Management, and Project Controls. Relocation and housing are NOT provided for these positions. Locations: Harrisburg, PA; King of Prussia, PA (Norristown); Philadelphia, PA (Pennsylvania); Pittsburgh, PA.

Then responsibilities:

Responsibilities

• Assists engineer teams in various tasks and duties.
• Assists Engineer with research, development and design of projects.
• Assists Engineer with the preparation of engineering drawings and documents as assigned.
• Performs other duties as assigned.

Then Requirements (including required qualifications, skills, preferred): We could split into Requirements and Qualifications but to keep few sections, maybe Requirements includes required qualifications, skills, and preferred. But we have separate "What You’ll Need" (required) and "What You’ll Bring" (skills) and "What We Prefer" (preferred). We could make three sub-sections but headings limited. Could we use

for Requirements and then inside have

for required,

for skills,

for preferred? That's okay. Thus:

Requirements

Required: High School Diploma/GED or equivalent plus current enrollment in an accredited post-secondary engineering program.

Skills you’ll bring: Understands engineering, geometric, and algebraic principles at a basic level; shows proficiency with Microsoft Office Suite; accepts and applies direction from peers and supervisors; obtains an understanding of introductory shop drawing and submittal procedures and requirements; ability to perform basic engineering calculations; ability to organize information for use in drawings or other documents.

Preferred: Completion of 2 years of post-secondary civil engineering program; knowledgeable in MicroStation and/or AutoCAD; strong interest in transportation and infrastructure.

We could also include job type etc as a short paragraph after Requirements maybe under a heading? Not allowed. Could add a short paragraph after Requirements without heading? The instruction says output ONLY the HTML fragment; we can have multiple

elements not under headings? It didn't forbid stray paragraphs, but they said use

for section headings and

• for any list, and

  for prose. So we can have

  for prose anywhere. So we could add a

  for job metadata after Requirements. Thus:

  Job Type: Intern; Full/Part Time: Full time; Job Category: Engineering Group.

  We should also keep the note about visa sponsorship not available? That is under Additional Information; it's a statement: "Visa sponsorship is not available for this position." That's substantive. Should we keep? It's under Additional Information block. It's a specific statement. We should preserve it. It's not boilerplate; it's a condition. So we need to include it. Where to put? Could be under Requirements as a note, or a separate short paragraph. Since we don't have a heading for "Additional Information", we can add a

  after Requirements: "Visa sponsorship is not available for this position." Also we have "#MD #Bridges, #ConstructionManagement, #Highways, #ProjectControls, #Traffic, #TransitAndRail" maybe not needed. We also have "Click here for benefits information: HNTB Total Rewards" - we decided not to include Benefits section because not specific. But the sentence itself is a link; maybe we could drop as it's just a referral. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This line is not exactly boilerplate but it's a link to benefits info; could be considered navigation? It's a call to action. Probably we should drop it as it's not substantive detail about benefits. Similarly "Click here to learn more about Equal Opportunity Employer/Disability/Veteran" is EEO boilerplate; drop. Thus final HTML:

  About the role

  At HNTB, you can create a career that is meaningful to you while building communities that matter to all of us. For more than a century, we have been delivering solutions for some of the largest, most complex infrastructure projects across the country. With our historic growth, it is an exciting time to join our team of employee-owners. This opportunity entails being responsible for assisting assigned department(s) and/or project(s) by performing basic engineering related tasks which may reflect elements of standard post-secondary engineering curriculum. Our Philadelphia, King of Prussia, Harrisburg, and Pittsburgh, PA offices are seeking Intern Engineers for Summer 2027 in the following areas: Structures, Roadway, Traffic, Track, Rotational (Structures/Track/Transportation), Construction Management, and Project Controls. Relocation and housing are NOT provided for these positions. Locations: Harrisburg, PA; King of Prussia, PA (Norristown); Philadelphia, PA (Pennsylvania); Pittsburgh, PA.

  Responsibilities

  • Assists engineer teams in various tasks and duties.
  • Assists Engineer with research, development and design of projects.
  • Assists Engineer with the preparation of engineering drawings and documents as assigned.
  • Performs other duties as assigned.

  Requirements

  Required: High School Diploma/GED or equivalent plus current enrollment in an accredited post-secondary engineering program.

  Skills you’ll bring: Understands engineering, geometric, and algebraic principles at a basic level; shows proficiency with Microsoft Office Suite; accepts and applies direction from peers and supervisors; obtains an understanding of introductory shop drawing and submittal procedures and requirements; ability to perform basic engineering calculations; ability to organize information for use in drawings or other documents.

  Preferred: Completion of 2 years of post-secondary civil engineering program; knowledgeable in MicroStation and/or AutoCAD; strong interest in transportation and infrastructure.

  Visa sponsorship is not available for this position.

  Job Type: Intern; Full/Part