Transit Systems Intern

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

for 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: EEO, legal, etc. Also remove duplicate lines, navigation, cookie, etc. Keep substantive info. Let's parse the posting. Content: Intro paragraph about HDR culture, mission, etc. That's about the role? Could be "About the role" or maybe "About HDR". But we have heading "About the role". Use that for descriptive paragraph(s) about the role and company. Then "As part of HDR’s Transportation Business Group..." etc. That's also about role. Then "We are all employee-owners at HDR..." etc. Then "In the role of Transit Systems Intern, we'll count on you to:" then 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 That's responsibilities. Then "Preferred Qualifications" heading: content: Prefer 2 years completed toward degree. Knowledge of CAD. Interest or completed course work in: Circuits Systems Engineering Preference given to local candidates Then "Required Qualifications": content: 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" etc. That's more about culture; could be part of About the role or maybe separate but we can include in About the role. Then "Our Commitment" about Employee Network Groups etc. That's also culture/benefits? Could be part of Benefits? But it's about inclusion groups. Might be considered part of About the role or maybe a separate section like "Culture". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put culture info under About the role. Then "We provide a comprehensive benefits package..." that's Benefits. 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.) Minnesota: $25 - $30" That's Pay. Then "Primary Location:United States-Minnesota-Saint Louis Park Other Locations:United States-Minnesota-Minneapolis Industry:Transit Schedule:Full-time Employee Status:Temporary BusinessClass:Rail and Transit Systems Job Posting:Sep 11, 2026" That's Schedule and maybe location. We have Schedule heading; we can put Schedule: Full-time. Also maybe location could be in About the role? But we shouldn't invent headings. We could include location in a short paragraph under About the role or maybe not include because not required? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep location info. Where to put? Could be part of About the role as a short paragraph. Or we could add a

after About the role before other sections. Since we cannot create new headings, we can just include a paragraph. Similarly, "Industry:Transit" maybe not needed but it's substantive. Could be included in About the role. "Employee Status:Temporary" maybe part of Schedule? Could be included in Schedule paragraph. "BusinessClass:Rail and Transit Systems" maybe not needed but could be included. "Job Posting:Sep 11, 2026" maybe metadata; we could drop as minor metadata? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can fold minor metadata into a short

or drop it. So we could include a short paragraph with location, schedule, etc. Or we could drop it? But we must preserve ALL substantive information. Location, schedule, employee status are substantive. So we should keep them. Thus after the sections, we can add a

containing: Primary Location: United States-Minnesota-Saint Louis Park; Other Locations: United States-Minnesota-Minneapolis; Industry: Transit; Schedule: Full-time; Employee Status: Temporary; Business Class: Rail and Transit Systems; Job Posting: Sep 11, 2026. But we already have a Schedule section; we could put schedule details there. However schedule section should only be emitted if posting actually states them. It does state Schedule:Full-time. So we can have a

Schedule

with

Full-time

. Also we could include employee status maybe there. But we also have location and industry etc. Could be in About the role. Let's structure:

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 transportation is more than movement, it’s the foundation of connected, thriving communities. As part of HDR’s Transportation Business Group, you’ll help shape the systems that move people and goods safely, efficiently, and sustainably. From designing resilient highways and iconic bridges to advancing transit, passenger and freight rail, aviation, federal transportation ports and marine infrastructure, your work will directly support economic vitality, public safety, sustainable and resilient communities and quality of life. We bring together planners, engineers, architects, construction management staff, environmental, strategic communications, economists, management consultants and specialists across disciplines to solve complex mobility challenges with innovation, technical excellence, and a deep understanding of community needs. Whether you're modernizing aging infrastructure or pioneering next-generation transportation solutions, your contributions will help define the future of mobility. This isn’t just a job, it’s a chance to lead progress, drive meaningful impact, and leave a legacy of smarter, more connected transportation networks. We are all employee-owners at HDR, which is the foundation of our collaborative culture that connects employees around the world. What We Believe HDR is our company. Together, we build on each other's life experiences and perspectives to make great things possible every day. This shapes our collaborative culture, encourages organizational trust and connects us closer to the clients and communities we serve. Our Commitment As employee owners, we all have a role in creating an inclusive environment where each of us is welcomed, valued, respected and empowered to bring our authentic selves to work every day. Our eight Employee Network Groups (Asian Pacific, Black, Hispanic/Latino(a), LGBTQ+, People with Disabilities, Veterans, Women, Young Professionals) help create a sense of belonging and foster a supportive environment where everyone is empowered to engage and contribute. Each group has an executive sponsor and is open to all employees.

That covers a lot. Then

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

Then

Preferred Qualifications

• Prefer 2 years completed toward degree
• Knowledge of CAD
• Interest or completed course work in:
  • Circuits
  • Systems Engineering
• Preference given to local candidates

But we need to keep the nested list? The original had "Interest or completed course work in:CircuitsSystems Engineering". Could be two items. We'll just list them as separate

. 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

Skills

maybe? The posting didn't have a separate skills section; but we have some skills like CAD, Microsoft Office, problem-solving, communication. Could be placed under Skills. However we should only create a section if posting has real, specific content for it. The posting does mention skills implicitly in qualifications. But we could combine skills into Qualifications. The instruction: Prefer a few substantive sections over many thin ones. So maybe we don't need a separate Skills section; we can incorporate skills into Qualifications or Responsibilities. But we already have Required Qualifications and Preferred Qualifications. That covers skills. So we can skip Skills. Then

Benefits

We provide a 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. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.)

Then

Pay

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

Then

Schedule

Full-time

Then after that, we may add a short paragraph for location etc. But we already included location in About the role? Not yet. We could add a short paragraph after Schedule:

Primary Location: United States-Minnesota-Saint Louis Park; Other Locations: United States-Minnesota-Minneapolis; Industry: Transit; Employee Status: Temporary; Business Class: Rail and Transit Systems; Job Posting: Sep 11, 2026

But we need to ensure we are not duplicating info. The location hasn't been mentioned elsewhere. So we need to include it. Thus final HTML fragment:

About the role

... (long paragraph) ...

Responsibilities

...

Preferred Qualifications

...

Required Qualifications

...

Benefits

...

Pay

...

Schedule

Full-time

Primary Location: United States-Minnesota-Saint Louis Park; Other Locations: United States-Minnesota-Minneapolis; Industry: Transit; Employee Status: Temporary; Business Class: Rail and Transit Systems; Job Posting: Sep 11, 2026

Check for any boilerplate removed: We removed EEO, legal, navigation, cookie, duplicated lines, application instructions. We kept the "Watch Our Story:" link; that's okay. We kept the "What We Believe" and "Our Commitment" paragraphs inside About the role. We kept the benefits note about temporary/part-time limited benefits. We kept the pay note. We kept schedule. We kept location etc. We didn't invent any sections. Check for any heading with