Summer 2027 Building Engineering Intern

We need to output HTML fragment with sections only when there is real specific content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive information. We need to parse the posting. Content: Intro paragraph: "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? Watch Our Story:' https://www.hdrinc.com/our-story' 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 believe building engineering is more than systems and structures, it’s about powering progress and enabling innovation. 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." That's about the role / company description. Could be "About the role" section. Then "What You'll Do" list: bullet points. Then "Why You'll Love This Internship" paragraph + bullet list. Then "Preferred Qualifications" bullet list. Then "Required Qualifications" bullet list. Then "What We Believe" paragraph. Then "Our Commitment" paragraph. Then metadata: Primary Location: United States-Florida-Orlando; Industry: Building Engineering; Schedule: Full-time; Employee Status: Temporary; BusinessClass: Building Structural; Job Posting: Sep 15, 2026. We need to include sections only if real specific content. We have content for About the role, Responsibilities (What You'll Do), Requirements? Could combine Preferred and Required as Qualifications? The spec says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include. We have: - About the role: intro paragraph(s). Good. - Responsibilities: "What You'll Do" bullet list. - Requirements: maybe "Required Qualifications" bullet list. - Qualifications: maybe "Preferred Qualifications" bullet list? But spec distinguishes Requirements vs Qualifications. Could treat Requirements as required qualifications, Qualifications as preferred qualifications. Or combine. - Skills: maybe list of skills from Preferred Qualifications (communication, organizational, problem-solving, teamwork, software experience). Could be separate Skills section. - Benefits: Not explicitly stated. There's mention of mentorship, exposure, etc. Could be considered benefits but not explicit benefits like health, etc. The instruction: never create Benefits section unless posting actually states them. It does mention "You'll gain exposure to real projects, receive mentorship from experienced professionals, and develop practical skills that will help launch your career". That's more like benefits but not explicit benefits like health insurance. Might be considered benefits? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not explicitly state benefits like health, retirement, etc. So we should not create Benefits section. - Pay: Not stated. So omit. - Schedule: It states "Schedule:Full-time" in metadata. So we can include Schedule section with that content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. We need to ensure we don't create empty sections. Now we need to format:

About the role

...

We need to preserve all substantive information. So we need to include the intro paragraphs (maybe combine into one or multiple

). We'll keep as one paragraph maybe but could split. We'll keep as one

containing the whole intro text (maybe multiple sentences). Ensure we keep the link to Our Story as is. Then Responsibilities:

Responsibilities

• ... each bullet from "What You'll Do".

What You'll Do bullets: - Support multidisciplinary project teams in the planning, design, and delivery of building projects. - Assist with the preparation of drawings, models, renderings, specifications, and construction documents. - Collaborate with architects, mechanical, electrical, structural, plumbing, and other design professionals. - Participate in project meetings, design reviews, and site visits. - Conduct research on building systems, codes, sustainability initiatives, and emerging technologies. - Utilize industry-standard software and digital tools to support project development. Now Requirements: Required Qualifications bullet list: - 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 Now Qualifications: Preferred Qualifications bullet list: - Prefer 2 years completed toward degree with 3.0+ GPA - Currently pursuing a Bachelor's or Master's degree in Architectural Engineering, Mechanical Engineering, Electrical Engineering, Structural Engineering, Industrial Engineering, or a related field. - Passion for building design, innovation, and creating spaces that improve people's lives. - Strong communication, organizational, and problem-solving skills. - Ability to work effectively in a collaborative team environment. - Experience with Revit, AutoCAD, Bluebeam, SketchUp, or other design software is a plus. Now Skills: Could extract skills from Preferred Qualifications: Strong communication, organizational, problem-solving skills; ability to work effectively in collaborative team environment; experience with Revit, AutoCAD, Bluebeam, SketchUp, or other design software. Also maybe attention to detail etc but that's in Requirements. We'll create a Skills section with bullet list of skills. But we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create Skills section, we need to ensure we are not omitting any info from elsewhere. We could move some of the Preferred Qualifications content to Skills, but then we would be removing from Qualifications. Better to keep Qualifications as is and maybe not create Skills section if it would duplicate. However we could create Skills section that lists skills explicitly mentioned, but we would still keep them also in Qualifications? That would duplicate info, which is allowed? The instruction says preserve ALL substantive information; does not forbid duplication, but better to avoid duplication? It didn't say not to duplicate. It says do NOT invent or summarize away detail. Duplication is not summarizing away, it's repeating. Might be okay but could be considered redundant. However they said "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. Creating Skills may be thin if we just list a few items. Might be better to incorporate skills into Qualifications or Responsibilities. Since we already have Qualifications (Preferred) and Requirements (Required). Skills could be considered part of Qualifications. So maybe we omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. Check if we have any content for Benefits? Not explicit. Pay? Not. Thus output HTML with those sections. Now we need to include Schedule section with content: Full-time (maybe also mention Temporary? Actually Employee Status: Temporary, but schedule is Full-time. Could include both? The Schedule heading should contain schedule info. Could also include Employee Status? Might be considered separate but not a heading. We could include schedule line: Full-time. Could also note Temporary as employee status but not required. We'll just put Full-time. Now we need to ensure we don't include any boilerplate like EEO, etc. We removed those. Now produce HTML fragment. Let's craft:

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? Watch Our Story: https://www.hdrinc.com/our-story. 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 believe building engineering is more than systems and structures, it’s about powering progress and enabling innovation. 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.

Responsibilities

• Support multidisciplinary project teams in the planning, design, and delivery of building projects.
• Assist with the preparation of drawings, models, renderings, specifications, and construction documents.
• Collaborate with architects, mechanical, electrical, structural, plumbing, and other design professionals.
• Participate in project meetings, design reviews, and site visits.
• Conduct research on building systems, codes, sustainability initiatives, and emerging technologies.
• Utilize industry-standard software and digital tools to support project development.

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

Qualifications

• Prefer 2 years completed toward degree with 3.0+ GPA
• Currently pursuing a Bachelor's or Master's degree in Architectural Engineering, Mechanical Engineering, Electrical Engineering, Structural Engineering, Industrial Engineering, or a related field.
• Passion for building design, innovation, and creating spaces that improve people's lives.
• Strong communication, organizational, and problem-solving skills.
• Ability to work effectively in a collaborative team environment.
• Experience with Revit, AutoCAD, Bluebeam, SketchUp, or other design software is a plus.

Schedule

Full-time

Check if we need to include location? Not a heading. Could be included in About the role? Not needed. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Location is minor metadata; we could drop it or include in a short p. Since we already have About the role section, we could add a short p after About the role containing location etc. But we must not create extra headings. Could add