New Grad Engineer I - Summer 2027

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, no boilerplate. Let's parse the posting. Content: - Intro paragraph: "What We're Looking For 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 in the production and modification of design calculations, technical reports, engineering plans and specifications for assigned projects. This position performs research, development, calculations, design and delivery in partnership with the project team. Applies engineering techniques, procedures and design criteria for projects ranging in size and complexity. Leverages technical knowledge to assist in the execution and evaluation of project designs. Develops conceptual and detailed designs and calculations to support the project execution using current drawing and technical tools, programs and software. As a member of the team, you will contribute to the successful project delivery for a diverse range of projects for HNTB’s clients. Our Philadelphia, King of Prussia, and Harrisburg, PA offices are seeking New Grad Engineers within the Traffic, Highway, Structures, Track, Construction Management, Overhead Contact Systems, and Electrical groups for Summer 2027." That's about the role. - "What You'll Do" bullet list: Completes assigned work within the schedule and number of hours provided. Supports the preparation and modification of project reports, plans, designs, and calculations. Assists in the preparation of project quantity and cost estimates. Assists engineering teams with organization and administrative support of design files. Supports engineering teams with various tasks and duties including but not limited to research, data collection, field investigations, development, and design of projects. Performs other duties as assigned - "What You'll Need": Bachelor's degree in Engineering - "What You'll Bring": Exhibits an understanding of engineering principles relevant to the discipline. Attains knowledge of the Microsoft Office Suite, and familiarity with MicroStation and/or AutoCad or other software. - "What We Prefer": Master's degree in Engineering, Engineer in Training (EIT) certification, Knowledgeable in MicroStation and/or AutoCAD, Strong interest in transportation and infrastructure - Additional Information: Click here for benefits information: HNTB Total Rewards (link). Click here to learn more about Equal Opportunity Employer/Disability/Veteran Visa sponsorship is not available for this position. #MD #Bridges, #ConstructionManagement, #Highways, #Traffic, #TransitAndRail Locations: Harrisburg, PA, King of Prussia, PA (Norristown), Philadelphia, PA (Pennsylvania) Notice To Third-party Agencies ... (boilerplate). Job Type: Regular Full/Part Time: Full time Job Category: Engineering Group ReqID: R-31656 #college ... EEO statement etc. We need to remove boilerplate: EEO, legal, navigation, cookie, scam-warning, duplicated lines, application instructions. Also remove "Click here for benefits information: HNTB Total Rewards" maybe we can keep benefits? The instruction: "Prefer a few substantive sections over many thin ones." Benefits: we have a link to benefits info but no actual benefits listed. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It only says "Click here for benefits information: HNTB Total Rewards" which is a link, not actual benefits. So we should NOT create a Benefits section because no specific benefits listed. Similarly Pay and Schedule: not stated (except maybe "Full time" under Job Type). The posting says "Job Type: Regular Full/Part Time: Full time". That indicates schedule: Full time. Is that considered specific content for Schedule? It says "Full time". That's a schedule detail. The rule: include a section ONLY when posting has real, specific content for it — 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. It does state Full time, so we could include a Schedule section with that info. However "Full time" is somewhat generic but it's stated. I'd include Schedule section with

Full time

. Pay: not stated, so omit. Benefits: only a link, not actual benefits, so omit. Now sections we have: About the role (intro), Responsibilities (What You'll Do), Requirements (What You'll Need), Qualifications (What You'll Bring + What We Prefer maybe combine?), Skills (maybe from What You'll Bring and What We Prefer). But we need to decide which headings to use. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose among those. We need to avoid thin sections. Let's see content: - About the role: we have a paragraph describing role and offices seeking New Grad Engineers for Summer 2027. That's substantive. - Responsibilities: the bullet list under What You'll Do. - Requirements: Bachelor's degree in Engineering (maybe also location? but location is not a requirement). Could also include "New Grad Engineers" but that's more about target. We'll keep Requirements as Bachelor's degree in Engineering. - Qualifications: Could combine What You'll Bring and What We Prefer? But Qualifications heading is for qualifications like degree, certifications, etc. Could put Bachelor's degree as Requirement, and Qualifications as understanding of engineering principles, knowledge of MS Office, familiarity with MicroStation/AutoCAD, etc. Also Master's degree preferred, EIT certification, strong interest in transportation/infrastructure. - Skills: Could be specific software skills: Microsoft Office Suite, MicroStation, AutoCAD. But we already have those in Qualifications. Might be thin. Better to have: About the role, Responsibilities, Requirements, Qualifications. Possibly Schedule. We should not create Skills if it's thin. Let's see if we have enough for Skills: "Exhibits an understanding of engineering principles relevant to the discipline." That's more knowledge than skill. "Attains knowledge of the Microsoft Office Suite, and familiarity with MicroStation and/or AutoCad or other software." That's skill. "Master's degree in Engineering" is qualification. "Engineer in Training (EIT) certification" is qualification. "Strong interest in transportation and infrastructure" is interest. Thus we could have Skills section with Microsoft Office Suite, MicroStation, AutoCAD. But that's similar to Qualifications. Might be okay but risk of thin. Given instruction to prefer few substantive sections over many thin ones, we could combine Qualifications and Skills into one Qualifications section that includes both knowledge and skills. Then we have About the role, Responsibilities, Requirements, Qualifications, Schedule. Check if Schedule is substantive: "Job Type: Regular Full/Part Time: Full time". That's specific. So we can include Schedule. Now we must not repeat job title as heading. Not include Job ID etc. We need to preserve all substantive information: offices locations, groups, Summer 2027, etc. Must keep that in About the role. Also need to keep bullet list exactly as given (maybe rephrase? Must preserve all substantive information, not invent or summarize away detail. We can keep the bullet points as

• ...
. Should we keep the exact phrasing? Yes. Now we need to strip boilerplate: EEO statements, legal, navigation, "Click here for benefits information: HNTB Total Rewards" (we are omitting benefits section, but we might still need to mention that benefits info exists? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the benefits section, are we losing substantive info? The posting includes a link to benefits information but no actual benefits details. That's arguably not substantive detail about the job; it's a pointer. The instruction says never create Benefits section unless posting actually states them. It does not state benefits, just a link. So we can omit that link entirely? That would be removing a piece of info (the link). Is that considered substantive? It's a reference to benefits info; but the actual benefits are not stated. The rule says preserve ALL substantive information; do NOT invent or summarize away detail. The link is not substantive detail about the job; it's a navigation/link. Probably safe to omit. Similarly, we should remove the hashtags, locations list? Locations are substantive: "Our Philadelphia, King of Prussia, and Harrisburg, PA offices are seeking New Grad Engineers...". That's location info. We should keep that in About the role. We should also keep the groups: Traffic, Highway, Structures, Track, Construction Management, Overhead Contact Systems, and Electrical groups. We should keep "Summer 2027". Now we need to format. Let's draft 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 in the production and modification of design calculations, technical reports, engineering plans and specifications for assigned projects. This position performs research, development, calculations, design and delivery in partnership with the project team. Applies engineering techniques, procedures and design criteria for projects ranging in size and complexity. Leverages technical knowledge to assist in the execution and evaluation of project designs. Develops conceptual and detailed designs and calculations to support the project execution using current drawing and technical tools, programs and software. As a member of the team, you will contribute to the successful project delivery for a diverse range of projects for HNTB’s clients. Our Philadelphia, King of Prussia, and Harrisburg, PA offices are seeking New Grad Engineers within the Traffic, Highway, Structures, Track, Construction Management, Overhead Contact Systems, and Electrical groups for Summer 2027.

Responsibilities

• Completes assigned work within the schedule and number of hours provided.
• Supports the preparation and modification of project reports, plans, designs, and calculations.
• Assists in the preparation of project quantity and cost estimates.
• Assists engineering teams with organization and administrative support of design files.
• Supports engineering teams with various tasks and duties including but not limited to research, data collection, field investigations, development, and design of projects.
• Performs other duties as assigned

Requirements

Bachelor's degree in Engineering

Qualifications

• Exhibits an understanding of engineering principles relevant to the discipline.
• Attains knowledge of the Microsoft Office Suite, and familiarity with MicroStation and/or AutoCAD or other software.
• Master's degree in Engineering (preferred)
• Engineer in Training (EIT) certification (preferred)
• Strong interest in transportation and infrastructure (preferred)

Schedule

Full time

Check if we missed any substantive info: The posting also mentions "Job Type: Regular". Could include "Regular" but not needed. The schedule is Full time. Could also mention "Regular" but it's okay. We should not include "Job Category: Engineering Group". That's maybe not needed. We should not include "ReqID: R-31656". That's metadata to drop. We should not include "#college" etc. We should not include EEO statements. Now ensure