Internships: Summer 2027 - Salem, OR

We need to produce HTML fragment with sections: About the role? The posting includes intro paragraphs, then "What You’ll Do", "Internship Areas Of Opportunity This Summer", "What We Are Looking For", "Tell Us About You", "Why apply now?" maybe not needed as heading? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. We have: - Intro: "Internships: Summer 2027 At David Evans and Associates (DEA), we're passionate..." This is about the role? Could be "About the role". We'll include an

  About the role

  with paragraphs. - "What You’ll Do": responsibilities. Use

  Responsibilities

  with
  • list. - "Internship Areas Of Opportunity This Summer": list of disciplines. Could be "Qualifications"? Actually it's areas of opportunity. Could be "Qualifications"? Not exactly. Could be "Skills"? Not exactly. Could be "Requirements"? Not exactly. Might be better as "Qualifications"? But we have separate "What We Are Looking For" which is qualifications. The areas of opportunity is more like "Internship Areas". Could be a section "Internship Opportunities" but not in allowed headings list. The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings where appropriate. If a section doesn't fit, maybe we shouldn't create a heading not in list? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings when appropriate. We can also use other headings if needed? The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. Thus we need to map: - About the role: intro paragraph(s). - Responsibilities: "What You’ll Do" list. - Qualifications: "What We Are Looking For" (qualifications vary but successful candidates are generally: ...). Also maybe "Internship Areas Of Opportunity" could be considered "Qualifications"? Not exactly. Could be "Skills"? Not exactly. Could be "Requirements"? Not exactly. Could be "About the role"? Not. Maybe we can include "Internship Areas Of Opportunity" as a

    under Qualifications? Or as a separate section "Qualifications" with sublist? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine areas of opportunity into Qualifications section as a list. - Benefits: The posting includes "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 Potential salary range: $20.00/hour - $30.00/hour (Dependent on Skills, Experience, and Geographic Location)". This includes benefits and pay. So we can have Benefits section with list of benefits, and Pay section maybe separate? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits and pay. So we can have Benefits and Pay sections. Schedule is mentioned: "Flexible work schedules including a 9/80 schedule—every other Friday off!" That's schedule info. Could be part of Benefits or separate Schedule section. Since they said we can create Schedule section if posting actually states them. It does mention schedule. So we could have Schedule section. But we need to avoid filler like "commensurate with experience". The pay range is specific: $20.00/hour - $30.00/hour. Good. We also have "Tell Us About You" which is application instructions (what to submit). According to instruction: remove application instructions. So we should drop that section. "Why apply now?" also application instructions? It's encouraging to apply early. Might be considered application instructions; we should remove. Also "Check our Careers Website throughout recruiting season for new discipline-specific internship postings, updated regularly." That's also application instruction/boilerplate; remove. Also "Potential office locations include: ..." That's location info; could be part of About the role or maybe Benefits? Not exactly. Could be included in About the role as prose. We need to preserve all substantive information; not drop location info. So we should keep location list somewhere. Could be in About the role paragraph. We also have "Interns are valued members of our teams, and many launch full-time careers with DEA after graduation." That's substantive; keep in About the role. Now, we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

    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. Interns are valued members of our teams, and many launch full-time careers with DEA after graduation. DEA offers internships based in our offices throughout Washington, Oregon, California, Idaho, Utah, and Colorado; availability varies by discipline and business need. 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.

    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

    Qualifications

    Qualifications vary by internship, but successful candidates are generally:

    • 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

    Internship areas of opportunity this summer include:

    • 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

    Benefits

    • 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

    Pay

    Potential salary range: $20.00/hour - $30.00/hour (Dependent on Skills, Experience, and Geographic Location)

    We need to ensure we didn't include any application instructions like "Tell Us About You", "Why apply now?" etc. We removed those. Check for any duplicated lines: we have not duplicated. Check for any boilerplate: we removed EEO etc. Check for any placeholder like "commensurate with experience": not present. Check for any mention of schedule: we included flexible work schedule in Benefits; we could also create Schedule section but we already have schedule info in Benefits. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule (flexible work schedules including a 9/80 schedule). So we could have a Schedule section separate. But we already placed schedule under Benefits. That's okay; we didn't create a Schedule section. It's fine to include schedule info within Benefits. However, we might want to separate Schedule as its own section to avoid thin sections? The instruction says prefer a few substantive sections over many thin ones. Having schedule as part of Benefits is fine. Check if we missed any substantive info: The line "As an intern, you will have the opportunity to cultivate and develop your skills, build valuable professional relationships, and work alongside talented colleagues who are committed to improving the quality of life while demonstrating stewardship of the built and natural environments." This is under "What We Offer" before Benefits. We didn't include that. It's substantive. Should we include it? It's about what we offer, similar to benefits. Could be added to Benefits section as a bullet or paragraph. Let's incorporate into Benefits section as a bullet: "Opportunity to cultivate and develop skills, build professional relationships, and work alongside talented colleagues committed to improving quality of life and stewardship of built and natural environments." Also "We foster an environment where talented professionals have the freedom and support to do their most meaningful work. Our values and company culture form the foundation of our success, creating a positive and collaborative work environment. These guiding principles