Mechanical Engineering Intern (Summer 2027)

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Content: - Intro about HDR culture, mission, etc. Could be "About the role" or maybe "About the role" includes description of role and company. The posting includes description: "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure..." etc. That's about the role. - Then "In the role of Mechanical Engineering Intern, we'll count on you to:" followed by bullet list: Gain real-world experience on exciting projects; Connect with recent college graduates and our company leaders through mentoring and young professionals' programs; Apply standard engineering techniques and procedures; Perform assignments under the direct supervision of a professional or Project Manager; Perform other duties as needed. - Then note about relocation: "**Please note that HDR does not provide financial assistance for relocation or housing expenses related to this position**" - this is a note; could be included maybe in Responsibilities or a note. Not a heading. - Then "Preferred Qualifications" with bullet: Prefer 2 years completed toward degree with 3.0+ GPA; Demonstrated knowledge of software packages related to field of study/industry; Local candidates preferred. - Then "Required Qualifications": Currently enrolled in an undergraduate or graduate Engineering program; Attention to detail; Possess strong problem-solving and communication skills; Basic Microsoft Office skills; An attitude and commitment to being an active participant of our employee-owned culture is a must. - Then "What We Believe" paragraph about HDR culture. - Then "Our Commitment" paragraph about inclusive environment, Employee Network Groups, benefits list: comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes medical, dental, vision, short and long-term disability, life insurance, an employee assistance program, paid time away, parental leave, paid holidays, a retirement savings plan with employer match, employee referral bonus and tuition reimbursement. - Then "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) Arlington, VA: $21 - $25." - Then "Primary Location: United States-Virginia-Arlington Industry: Building Engineering Schedule: Full-time Employee Status: Temporary BusinessClass: Building Mechanical Job Posting: Sep 17, 2026" - Then EEO boilerplate to remove. We need to decide sections. We have: - About the role: could include the introductory paragraphs describing role and mission. - Responsibilities: the bullet list under "In the role of Mechanical Engineering Intern, we'll count on you to:" plus maybe the note about relocation? Probably include as part of responsibilities. - Requirements: maybe combine Required Qualifications? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use headings for those categories if content exists. We need to decide what goes where. We have "Preferred Qualifications" and "Required Qualifications". Could map Required Qualifications to "Requirements" heading, and Preferred Qualifications to "Qualifications" heading? Or "Skills" heading for skills like Microsoft Office, problem-solving, communication. Better to follow typical structure: Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Skills (specific skills like Microsoft Office, problem-solving, communication), Benefits, Pay, Schedule. We need to avoid empty sections. Let's extract: About the role: The introductory paragraphs before responsibilities: "At HDR, our employee-owners are fully engaged...". That's about company and role. We'll put that under About the role. Responsibilities: bullet list: - Gain real-world experience on exciting projects - Connect with recent college graduates and our company leaders through mentoring and young professionals' programs - Apply standard engineering techniques and procedures - Perform assignments under the direct supervision of a professional or Project Manager - Perform other duties as needed Also note about relocation: could be included as a paragraph after list. Requirements (Required Qualifications): - Currently enrolled in an undergraduate or graduate Engineering program - Attention to detail - Possess strong problem-solving and communication skills - Basic Microsoft Office skills - An attitude and commitment to being an active participant of our employee-owned culture is a must Qualifications (Preferred Qualifications): - Prefer 2 years completed toward degree with 3.0+ GPA - Demonstrated knowledge of software packages related to field of study/industry - Local candidates preferred Skills: maybe we could separate out specific skills like Microsoft Office, problem-solving, communication, attention to detail? But those are already in Required Qualifications. Could also put them under Skills. However we already used them in Requirements. To avoid duplication, we could move those to Skills and keep Requirements more about enrollment etc. But instruction: preserve all substantive information; we can categorize as we like as long as we don't lose info. Let's think: We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to fill each with content if exists. We have Benefits: list from "Our Commitment": medical, dental, vision, short and long-term disability, life insurance, employee assistance program, paid time away, parental leave, paid holidays, retirement savings plan with employer match, employee referral bonus, tuition reimbursement. Also mention that benefits are for full-time regular positions; temporary/part-time limited benefits. That's substantive. Pay: we have compensation range: Arlington, VA: $21 - $25. Also note that expected compensation range depends upon skills, experience, education and geographical location. So we can include that. Schedule: we have Schedule: Full-time; Employee Status: Temporary. Also Primary Location: Arlington, VA; Industry: Building Engineering; BusinessClass: Building Mechanical; Job Posting date. But schedule heading should contain schedule info: Full-time, Temporary status maybe. We'll include Schedule: Full-time; Employee Status: Temporary. We should not include Job ID/requisition numbers as headings; we can drop them or put in a short p. We need to remove boilerplate: EEO, equal opportunity, etc. Now construct HTML. We'll output:

About the role

At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? ... (continue until before responsibilities). We need to include the descriptive paragraph about role: "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure that supports the digital age and shapes the spaces where people work, connect, and thrive. From high-performance data centers driving the future of AI to dynamic commercial environments, your work will directly support technological advancement, sustainability, and human experience. We bring together mechanical, electrical, structural, and civil engineering experts to solve complex design challenges with precision, creativity, and collaboration. Whether you're optimizing energy efficiency, integrating resilient systems, or engineering the backbone of next-generation facilities, your contributions will help define the future of the built environment. This isn’t just a job, it’s a chance to lead innovation, engineer impact, and build a legacy of excellence. Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world." We'll combine that into a paragraph. Then Responsibilities:

Responsibilities

• Gain real-world experience on exciting projects
• Connect with recent college graduates and our company leaders through mentoring and young professionals' programs
• Apply standard engineering techniques and procedures
• Perform assignments under the direct supervision of a professional or Project Manager
• Perform other duties as needed

Please note that HDR does not provide financial assistance for relocation or housing expenses related to this position.

Then Requirements:

Requirements

• Currently enrolled in an undergraduate or graduate Engineering program
• Attention to detail
• Possess strong problem-solving and communication skills
• Basic Microsoft Office skills
• An attitude and commitment to being an active participant of our employee-owned culture is a must

Then Qualifications (Preferred):

Qualifications

• Prefer 2 years completed toward degree with 3.0+ GPA
• Demonstrated knowledge of software packages related to field of study/industry
• Local candidates preferred

Then Skills: maybe we could list specific technical skills? Not much left. Could we put something like "Proficiency in standard engineering techniques and procedures" but that's already in responsibilities. Could we leave Skills empty? We must not create a heading without real content. So we should omit Skills section if no specific skills left. However we have "Basic Microsoft Office skills" already in Requirements; we could move that to Skills and keep Requirements more about enrollment etc. But we already used it. Let's think: we could keep Skills empty and omit heading. That's allowed: only include sections when posting has real, specific content. So we can omit Skills. Benefits:

Benefits

• Medical
• Dental
• Vision
• Short and long-term disability
• Life insurance
• Employee assistance program
• Paid time away
• Parental leave
• Paid holidays
• Retirement savings plan with employer match
• Employee referral bonus
• Tuition reimbursement

(Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.)

Pay:

Pay

The expected compensation range for this position depends upon skills, experience, education and geographical location. Arlington, VA: $21 - $25.

Schedule:

Schedule

Full-time; Employee Status: Temporary.

We could also include Primary Location etc but not required; maybe we could add a short p under Schedule or separate? But we have no heading for location; we could incorporate location into About the role or a short p after schedule. However instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. So we could add a short p after schedule for location etc. But we already have location in Pay line; we could keep there. We need to ensure we don't repeat job title as heading. We didn't. Now output only HTML fragment. Check for any leftover boilerplate: we removed EEO lines. Check that we didn't include "What We Believe" or "Our Commitment" paragraphs besides benefits. We used benefits list from that paragraph; we omitted the descriptive sentences about culture etc. Could we include those under About the role? Already we have a long paragraph about culture and mission; we could incorporate the "What We Believe" and "Our Commitment" descriptive sentences there to preserve all substantive information. But we already have a long paragraph about role; we could add more. However we must not invent or summarize away detail. The "What We Believe" and "Our Commitment" paragraphs contain substantive info about culture, employee network groups, benefits. We already captured benefits list; we could also include the descriptive sentences about culture and network groups under About the role or maybe a separate section like "Culture". But we don't have a heading for culture; we could add to About the role. Thus we should incorporate the sentences: "What We Believe HDR is our company. Together, we build on each other's life experiences and perspectives to make