Traffic Engineering Intern
About the role
with paragraphs. Next: "In the role of Traffic Engineering Intern, we'll count on you to: Gain real-world experience on exciting projectsConnect with recent college graduates and our company leaders through mentoring and young professionals programsApply standard engineering techniques and proceduresPerform assignments under the direct supervision of a professional or Project ManagerPerform other duties as needed" That's responsibilities. SoResponsibilities
with- items.
Then "Preferred Qualifications Prefer 2 years completed toward degree with 3.0+ GPADemonstrated knowledge of software packages related to field of study/industryPreference given to local candidates"
That's preferred qualifications. Could go under Qualifications or maybe separate Preferred Qualifications but we only have headings: Qualifications, Skills, Requirements. We could combine Preferred and Required under Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications (maybe includes both required and preferred). Or we could have Requirements for required qualifications, Qualifications for preferred? But they said "e.g." not strict. We need to decide.
We have Required Qualifications: "Currently enrolled in an undergraduate or graduate Engineering program Attention to detailPossess 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"
We have Preferred Qualifications: "Prefer 2 years completed toward degree with 3.0+ GPADemonstrated knowledge of software packages related to field of study/industryPreference given to local candidates"
We could put Required under Requirements heading, Preferred under Qualifications heading. Or combine both under Qualifications. Let's follow typical: Requirements = required qualifications; Qualifications = preferred qualifications. That seems logical.
Thus:
Requirements
with- items.
Qualifications
with- items for preferred.
Skills: maybe we can extract skills from responsibilities? But we have "Basic Microsoft Office skills" already in requirements. Could also list "Attention to detail", "problem-solving", "communication". Those are skills. Could put under Skills heading. But we already have them in Requirements. Might duplicate. Better to keep them under Requirements and not create Skills unless there is distinct skill content not covered. The posting mentions "standard engineering techniques and procedures", "software packages related to field of study/industry". Those could be skills. But we could put them under Skills.
We need to avoid thin sections. Let's see what we have:
- About the role: substantive paragraph(s).
- Responsibilities: list of duties.
- Requirements: required qualifications (list).
- Qualifications: preferred qualifications (list).
- Skills: maybe we can list "standard engineering techniques and procedures", "software packages related to field of study/industry", "Microsoft Office". But those are somewhat overlapping with qualifications. Could combine.
Better to not create Skills if it would be thin. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if not enough distinct content.
Benefits: The posting includes: "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.)"
Thus we have benefits content. So include Benefits heading.
Pay: "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"
Thus we have pay range: Minnesota: $25 - $30. So include Pay heading.
Schedule: "Industry:Highway + Road Schedule:Full-time Employee Status:Temporary". So schedule: Full-time. Also Employee Status: Temporary. So we can include Schedule heading with Full-time (maybe also note Temporary). The instruction: include section only when posting has real, specific content. So we have schedule: Full-time. So include.
We must not include duplicated lines, boilerplate like EEO etc. Remove those.
Now construct HTML.
We need to wrap each section:
Heading
then content: eitherfor prose or
- for list.
For About the role: we have multiple sentences; we can put in
maybe multiple paragraphs but we can combine into one
with line breaks? Better to keep as one
with the content. Responsibilities: list items. Requirements: list items. Qualifications: list items. Benefits: list items (maybe
- ).
Pay: maybe
with the range. Schedule:
with Full-time (maybe also Temporary). Could combine. Let's extract exact text. About the role paragraph: Let's copy the big paragraph but ensure we keep all info. Might be long but okay. We need to preserve all substantive information; do not invent or summarize away detail. So we must include all sentences. Let's copy the paragraph exactly as in posting (excluding the link maybe? The link is part of content: "Watch Our Story:' https://www.hdrinc.com/our-story'". Should we keep the URL? It's substantive? It's a link; we can keep as plain text. We'll keep it. Thus About the role content: "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. This position will work with traffic engineering and transportation planning professionals to support a range of transportation projects. Assignments will vary based on project needs and may include traffic studies, traffic design, data analysis, transportation planning, and technical document preparation." Now Responsibilities list items: - 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 Note the original had no punctuation between items; we will split. Now Requirements list items: - 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) list items: - Prefer 2 years completed toward degree with 3.0+ GPA - Demonstrated knowledge of software packages related to field of study/industry - Preference given to local candidates Now Benefits list items: - 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 - tuition reimbursement Also note the note about temporary/part-time limited benefits; we could include as a sentence after list maybe in
. But we can incorporate as a note. We could add a
after list: "(Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.)" Now Pay: "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" We need to avoid duplicating the benefits note; but it's okay to repeat? Might be considered duplicated lines. The benefits note appears also in benefits section. To avoid duplication, we could keep the note only in benefits section and not repeat in pay. However the pay sentence includes that note as part of original text; but we can omit if it's duplicate. The instruction: remove duplicated lines. So we should not repeat the same sentence. So for Pay we can just include: "The expected compensation range for this position depends
- ).
Pay: maybe
- for list.
For About the role: we have multiple sentences; we can put in
- items for preferred.
Skills: maybe we can extract skills from responsibilities? But we have "Basic Microsoft Office skills" already in requirements. Could also list "Attention to detail", "problem-solving", "communication". Those are skills. Could put under Skills heading. But we already have them in Requirements. Might duplicate. Better to keep them under Requirements and not create Skills unless there is distinct skill content not covered. The posting mentions "standard engineering techniques and procedures", "software packages related to field of study/industry". Those could be skills. But we could put them under Skills.
We need to avoid thin sections. Let's see what we have:
- About the role: substantive paragraph(s).
- Responsibilities: list of duties.
- Requirements: required qualifications (list).
- Qualifications: preferred qualifications (list).
- Skills: maybe we can list "standard engineering techniques and procedures", "software packages related to field of study/industry", "Microsoft Office". But those are somewhat overlapping with qualifications. Could combine.
Better to not create Skills if it would be thin. The instruction: Prefer a few substantive sections over many thin ones. So we could omit Skills if not enough distinct content.
Benefits: The posting includes: "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.)"
Thus we have benefits content. So include Benefits heading.
Pay: "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"
Thus we have pay range: Minnesota: $25 - $30. So include Pay heading.
Schedule: "Industry:Highway + Road Schedule:Full-time Employee Status:Temporary". So schedule: Full-time. Also Employee Status: Temporary. So we can include Schedule heading with Full-time (maybe also note Temporary). The instruction: include section only when posting has real, specific content. So we have schedule: Full-time. So include.
We must not include duplicated lines, boilerplate like EEO etc. Remove those.
Now construct HTML.
We need to wrap each section:
- items.