Internships: Summer 2027 - Beaverton, OR
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must output only HTML fragment, no /, no markdown.
Let's structure:
About the role
Internships: Summer 2027 At David Evans and Associates (DEA), we're passionate about creating transportation systems, communities, infrastructure, and environments that improve quality of life. Every day, our teams collaborate on projects that connect people, support communities, and help shape the future. Looking for a meaningful summer internship where you can apply classroom knowledge to real-world projects? We’d love to hear from you. This posting is an opportunity to express your interest in Summer 2027 internships across DEA. By applying, you'll introduce yourself to our recruiting team and be considered as internship opportunities become available throughout our offices and business units. Check our Careers Website throughout recruiting season for new discipline-specific internship postings, updated regularly.
But we might want to trim some fluff? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that paragraph as is? It's somewhat generic but it's substantive. We'll keep.
Then Responsibilities:
Responsibilities
- Support planning, design, and technical project work
- Collaborate with multidisciplinary teams
- Participate in field work, site visits, and project meetings
- Learn industry tools, technologies, and best practices
- Develop professional skills through mentorship and real-world experience
- Make meaningful contributions to projects that impact communities directly
Then maybe "Internship Areas Of Opportunity" could be under a heading like "Areas of Opportunity" but not in allowed list. Could be under "About the role" or maybe "Qualifications"? Not exactly. The allowed headings are limited; we could embed that list under About the role as prose? But it's a list; we could still use under About the role? The rule: Use - for any list of duties/requirements/benefits. It doesn't restrict to those headings only; we can have lists anywhere. So we can add a list for Areas of Opportunity under About the role or maybe a separate heading not in list? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should only use those headings for sections. So we should not create other headings like "Internship Areas Of Opportunity". We could incorporate that list under About the role as a . That's okay.
Similarly "What We Are Looking For" could be Qualifications.
"Benefits" we have.
"Pay" we have.
"Schedule" we have.
We also have "Potential office locations include: ..." maybe could be under About the role as a paragraph.
We must not include application instructions like "Tell Us About You", "Why apply now?" etc. So we will omit those sections.
We also need to remove boilerplate like EEO etc. Not present.
Now craft final HTML.
Check for any duplicated lines: we should avoid repeating same content.
Let's write:
About the role
Internships: Summer 2027 At David Evans and Associates (DEA), we're passionate about creating transportation systems, communities, infrastructure, and environments that improve quality of life. Every day, our teams collaborate on projects that connect people, support communities, and help shape the future. Looking for a meaningful summer internship where you can apply classroom knowledge to real-world projects? We’d love to hear from you. This posting is an opportunity to express your interest in Summer 2027 internships across DEA. By applying, you'll introduce yourself to our recruiting team and be considered as internship opportunities become available throughout our offices and business units. Check our Careers Website throughout recruiting season for new discipline-specific internship postings, updated regularly.
Potential office locations include: Denver, CO; Boise, ID; Coeur d'Alene, ID; Pocatello, ID; Beaverton, OR; Corvallis, OR; Portland, OR; Salem, OR; Salt Lake City, UT; Bellevue, WA; Bellingham, WA; Everett, WA; Olympia, WA; Seattle, WA; Spokane, WA; Tacoma, WA; Tri-Cities, WA; Tukwila, WA; Woodinville, WA.
- Support planning, design, and technical project work
- Collaborate with multidisciplinary teams
- Participate in field work, site visits, and project meetings
- Learn industry tools, technologies, and best practices
- Develop professional skills through mentorship and real-world experience
- Make meaningful contributions to projects that impact communities directly
Internship Areas Of Opportunity
??? Not allowed. So we need to embed that list somewhere. Perhaps we can add another under About the role after responsibilities? But we already used a for responsibilities. We could combine responsibilities and areas? Better to keep responsibilities separate and then add another for areas of opportunity under About the role? But we already closed About the role with a for locations. We could add another
after that but still within About the role? However HTML doesn't allow nesting sections; we can just put another after the but before closing About the role? There's no explicit container; we just output elements sequentially. The rule about headings: we should not create extra headings. So we can just output another
after the location paragraph, still considered part of About the role? It's ambiguous but likely acceptable as long as we don't add a heading. We'll do that.
Thus after location paragraph, we add:
- Transportation: Roads & Highways, Smart Mobility (Traffic), Transit & Rail, Bridges & Structures
- Water & Environment: Water/Wastewater Infrastructure, Water Resources, and Environmental Planning & Compliance
- Land Development & Civil Engineering
- Energy: Electrical Engineering
- Surveying & Geomatics
- Construction Engineering & Inspection
- Marine Services
But note each item contains commas and colon; it's okay.
Now Qualifications:
Qualifications
- Currently enrolled in an accredited associate degree, bachelor’s degree, master’s degree, or certificate program
- Interested in gaining hands-on experience related to their field of study
- Curious, collaborative, and eager to learn
- Excited about making an impact through engineering, planning, design, technology, or professional services
Now Benefits:
Benefits
- Work Schedule: Flexible work schedules including a 9/80 schedule—every other Friday off!
- Sick Time: Accrual at 4% of eligible gross pay
- Retirement: 401k plan with employer match program
- Wellbeing focus: Holistic Wellbeing Program centered on physical, emotional, financial, career, and community health
- Growth opportunities: Access to mentorship, professional support, and pathways for career advancement
Now Pay:
Pay
Potential salary range: $20.00/hour - $30.00/hour (Dependent on Skills, Experience, and Geographic Location)
Now Schedule:
We already have schedule in Benefits; but we could also have a separate Schedule heading if we want to highlight. The Benefits already includes Work Schedule line. But we could still create a Schedule section with that detail. However we must not create sections with filler; we have actual schedule info. It's okay to have Schedule section with that detail. But we already included schedule in Benefits; duplicating might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we keep schedule inside Benefits and not create separate Schedule heading. However they listed Schedule as a possible heading; we can omit if we already covered it. Let's keep Benefits as is and not add Schedule.
Thus final HTML includes headings: About the role, Responsibilities, Qualifications, Benefits, Pay.
We also need to ensure we didn't miss any substantive info like "Interns are valued members of our teams, and many launch full-time careers with DEA after graduation." That's substantive; we should include it somewhere, maybe in About the role paragraph. We can add a sentence.
Add after first paragraph: "Interns are valued members of our teams, and many launch full-time careers with DEA after graduation."
Let's incorporate.
Now ensure we didn't include any boilerplate like "The posted salary range reflects the typical range for this position and is provided in accordance with applicable state and local pay transparency laws. Actual compensation will be based on experience, qualifications, and geographic location." That's substantive about pay; we should include it. Add to Pay paragraph.
Also "If you are a recruiter, search agency, or otherwise wish to refer a candidate to DEA, you will not be compensated in any way for your referral of a candidate to DEA without an active and signed written agreement in place in advance with DEA Human Resources. Any resume submitted to any DEA employee by an external recruiter without a written agreement in place at the time of submission will be considered the property of DEA and DEA will not be liable for the payment of a placement fee. If you would like to notify DEA of your interest in initiating a written agreement for services, please e-mail careers@deainc.com." That's boilerplate/legal; should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we drop that.
Now final HTML.
Check for any duplicated lines: we have responsibilities list, areas of opportunity list, qualifications list, benefits list, pay paragraph.
We must not include any markdown fences.
Let's craft final output.
for prose. We must output only HTML fragment, no /, no markdown. Let's structure:
About the role
Internships: Summer 2027 At David Evans and Associates (DEA), we're passionate about creating transportation systems, communities, infrastructure, and environments that improve quality of life. Every day, our teams collaborate on projects that connect people, support communities, and help shape the future. Looking for a meaningful summer internship where you can apply classroom knowledge to real-world projects? We’d love to hear from you. This posting is an opportunity to express your interest in Summer 2027 internships across DEA. By applying, you'll introduce yourself to our recruiting team and be considered as internship opportunities become available throughout our offices and business units. Check our Careers Website throughout recruiting season for new discipline-specific internship postings, updated regularly.
But we might want to trim some fluff? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that paragraph as is? It's somewhat generic but it's substantive. We'll keep. Then Responsibilities:Responsibilities
- Support planning, design, and technical project work
- Collaborate with multidisciplinary teams
- Participate in field work, site visits, and project meetings
- Learn industry tools, technologies, and best practices
- Develop professional skills through mentorship and real-world experience
- Make meaningful contributions to projects that impact communities directly
- under About the role? The rule: Use
- for any list of duties/requirements/benefits. It doesn't restrict to those headings only; we can have lists anywhere. So we can add a list for Areas of Opportunity under About the role or maybe a separate heading not in list? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should only use those headings for sections. So we should not create other headings like "Internship Areas Of Opportunity". We could incorporate that list under About the role as a
- . That's okay.
Similarly "What We Are Looking For" could be Qualifications.
"Benefits" we have.
"Pay" we have.
"Schedule" we have.
We also have "Potential office locations include: ..." maybe could be under About the role as a paragraph.
We must not include application instructions like "Tell Us About You", "Why apply now?" etc. So we will omit those sections.
We also need to remove boilerplate like EEO etc. Not present.
Now craft final HTML.
Check for any duplicated lines: we should avoid repeating same content.
Let's write:
- Support planning, design, and technical project work
- Collaborate with multidisciplinary teams
- Participate in field work, site visits, and project meetings
- Learn industry tools, technologies, and best practices
- Develop professional skills through mentorship and real-world experience
- Make meaningful contributions to projects that impact communities directly
- Transportation: Roads & Highways, Smart Mobility (Traffic), Transit & Rail, Bridges & Structures
- Water & Environment: Water/Wastewater Infrastructure, Water Resources, and Environmental Planning & Compliance
- Land Development & Civil Engineering
- Energy: Electrical Engineering
- Surveying & Geomatics
- Construction Engineering & Inspection
- Marine Services
- Currently enrolled in an accredited associate degree, bachelor’s degree, master’s degree, or certificate program
- Interested in gaining hands-on experience related to their field of study
- Curious, collaborative, and eager to learn
- Excited about making an impact through engineering, planning, design, technology, or professional services
- Work Schedule: Flexible work schedules including a 9/80 schedule—every other Friday off!
- Sick Time: Accrual at 4% of eligible gross pay
- Retirement: 401k plan with employer match program
- Wellbeing focus: Holistic Wellbeing Program centered on physical, emotional, financial, career, and community health
- Growth opportunities: Access to mentorship, professional support, and pathways for career advancement
About the role
Internships: Summer 2027 At David Evans and Associates (DEA), we're passionate about creating transportation systems, communities, infrastructure, and environments that improve quality of life. Every day, our teams collaborate on projects that connect people, support communities, and help shape the future. Looking for a meaningful summer internship where you can apply classroom knowledge to real-world projects? We’d love to hear from you. This posting is an opportunity to express your interest in Summer 2027 internships across DEA. By applying, you'll introduce yourself to our recruiting team and be considered as internship opportunities become available throughout our offices and business units. Check our Careers Website throughout recruiting season for new discipline-specific internship postings, updated regularly.
Potential office locations include: Denver, CO; Boise, ID; Coeur d'Alene, ID; Pocatello, ID; Beaverton, OR; Corvallis, OR; Portland, OR; Salem, OR; Salt Lake City, UT; Bellevue, WA; Bellingham, WA; Everett, WA; Olympia, WA; Seattle, WA; Spokane, WA; Tacoma, WA; Tri-Cities, WA; Tukwila, WA; Woodinville, WA.
Internship Areas Of Opportunity
??? Not allowed. So we need to embed that list somewhere. Perhaps we can add another- under About the role after responsibilities? But we already used a
- for responsibilities. We could combine responsibilities and areas? Better to keep responsibilities separate and then add another
- for areas of opportunity under About the role? But we already closed About the role with a
for locations. We could add another
- after that but still within About the role? However HTML doesn't allow nesting sections; we can just put another
- after the
but before closing About the role? There's no explicit container; we just output elements sequentially. The rule about headings: we should not create extra headings. So we can just output another
- after the location paragraph, still considered part of About the role? It's ambiguous but likely acceptable as long as we don't add a heading. We'll do that.
Thus after location paragraph, we add:
Qualifications
Benefits
Pay
Potential salary range: $20.00/hour - $30.00/hour (Dependent on Skills, Experience, and Geographic Location)
Now Schedule: We already have schedule in Benefits; but we could also have a separate Schedule heading if we want to highlight. The Benefits already includes Work Schedule line. But we could still create a Schedule section with that detail. However we must not create sections with filler; we have actual schedule info. It's okay to have Schedule section with that detail. But we already included schedule in Benefits; duplicating might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we keep schedule inside Benefits and not create separate Schedule heading. However they listed Schedule as a possible heading; we can omit if we already covered it. Let's keep Benefits as is and not add Schedule. Thus final HTML includes headings: About the role, Responsibilities, Qualifications, Benefits, Pay. We also need to ensure we didn't miss any substantive info like "Interns are valued members of our teams, and many launch full-time careers with DEA after graduation." That's substantive; we should include it somewhere, maybe in About the role paragraph. We can add a sentence. Add after first paragraph: "Interns are valued members of our teams, and many launch full-time careers with DEA after graduation." Let's incorporate. Now ensure we didn't include any boilerplate like "The posted salary range reflects the typical range for this position and is provided in accordance with applicable state and local pay transparency laws. Actual compensation will be based on experience, qualifications, and geographic location." That's substantive about pay; we should include it. Add to Pay paragraph. Also "If you are a recruiter, search agency, or otherwise wish to refer a candidate to DEA, you will not be compensated in any way for your referral of a candidate to DEA without an active and signed written agreement in place in advance with DEA Human Resources. Any resume submitted to any DEA employee by an external recruiter without a written agreement in place at the time of submission will be considered the property of DEA and DEA will not be liable for the payment of a placement fee. If you would like to notify DEA of your interest in initiating a written agreement for services, please e-mail careers@deainc.com." That's boilerplate/legal; should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we drop that. Now final HTML. Check for any duplicated lines: we have responsibilities list, areas of opportunity list, qualifications list, benefits list, pay paragraph. We must not include any markdown fences. Let's craft final output.