Civil Engineering Internship

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. Content: - Career Area: Engineering - Civil (metadata) - What We're Looking For: paragraph about hard-working college student, gain experience, mentors, intern next summer. - Location: Birmingham, AL - Number of positions available: 1 - Schedule: Summer 2027 - You Will Gain Experience In: list items: - Collaborating with team members on new ideas/innovations - Supporting Engineers in completing project deliverables - AutoCAD Civil 3D or Microstation - Preparation of construction documents - Education & Experience Qualifications: - Must be pursuing a Bachelor’s degree or Master’s degree from an accredited university - Major: Civil Engineering - Current GPA of 3.0 or higher - You must be at least 18 years of age. - Additional Details: - This is a paid internship working full-time hours (40) per week. - This is an in-person work opportunity. - Interns are not eligible for company benefits. - Housing assistance is not provided. - Why join us? paragraph about company. - Core values etc. - EEO boilerplate (remove). We need sections: About the role (maybe the "What We're Looking For" paragraph). Responsibilities (maybe the "You Will Gain Experience In" list). Requirements (maybe the education/experience qualifications). Qualifications (maybe overlapping? Could combine but we need separate sections only if content). Skills (maybe AutoCAD etc). Benefits (maybe mention paid internship, full-time hours, but note interns not eligible for company benefits, housing assistance not provided). Pay (maybe mention paid internship but no amount). Schedule (Summer 2027, full-time 40 hrs/week). We must not create sections with filler like "not specified". If we have content, we can include. Let's decide: - About the role: paragraph from "What We're Looking For". That's substantive. - Responsibilities: list of "You Will Gain Experience In". Those are duties/experience gained, could be responsibilities. - Requirements: maybe the education/experience qualifications (degree, GPA, age). Could also include major. - Qualifications: maybe same as Requirements? Might be redundant. Could combine but we need to avoid thin sections. Perhaps we can put education/experience under Requirements and skip Qualifications. - Skills: maybe AutoCAD Civil 3D or Microstation (specific skill). Could also include collaboration etc but that's more responsibility. We'll list skill. - Benefits: mention paid internship, full-time hours (40) per week, in-person work opportunity. Also note interns not eligible for company benefits, housing assistance not provided. That's still benefits info (though negative). We'll include. - Pay: we have "paid internship" but no amount. The rule says do NOT create Pay section unless posting actually states them. It states it's paid but no amount. Is that enough? It says "paid internship". That is stating it's paid, but not amount. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state it's paid, so we can include Pay section with that statement. However we must avoid filler like "commensurate with experience". "Paid internship" is specific enough. So we can include Pay:

Paid internship.

- Schedule: we have "Summer 2027" and "full-time hours (40) per week". That's specific. So Schedule section. Now we need to output HTML fragment with headings

for each section. Use

• for lists. Use

  for prose. We must not repeat job title as heading (not present). Do not put Job ID etc. We must remove boilerplate: EEO etc. Let's craft:

  About the role

  Are you a hard-working and dedicated college student who is looking to gain valuable work experience in your field? Do you want to gain experience while learning from great mentors and leaders? Barge Design Solutions is looking for someone like you to intern next summer.

  Responsibilities

  • Collaborating with team members on new ideas/innovations
  • Supporting Engineers in completing project deliverables
  • Using AutoCAD Civil 3D or Microstation
  • Preparing construction documents

  Requirements

  • Pursuing a Bachelor’s degree or Master’s degree from an accredited university
  • Major: Civil Engineering
  • Current GPA of 3.0 or higher
  • Must be at least 18 years of age

  Skills

  • AutoCAD Civil 3D or Microstation

  Benefits

  • Paid internship
  • Full-time hours (40) per week
  • In-person work opportunity

  Pay

  Paid internship (compensation not specified)

  But we must avoid filler like "compensation not specified". That's maybe filler. The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we cannot put "compensation not specified". We need to only include if we have real specific content. The posting says "paid internship". That's specific enough: it's paid. So we can just say

  Paid internship.

  That is not filler. It's a statement. Similarly for Benefits we have "Interns are not eligible for company benefits." and "Housing assistance is not provided." Those are specifics (though negative). We can include them. Let's adjust Benefits list to include those details. Benefits: - Paid internship - Full-time hours (40) per week - In-person work opportunity - Interns are not eligible for company benefits - Housing assistance is not provided That's all specific. Schedule: Summer 2027, full-time hours (40) per week (but we already used full-time hours in Benefits; maybe schedule just Summer 2027). However schedule could be "Summer 2027". Also we could note full-time hours (40) per week under Schedule as well. But we already used that in Benefits; duplication is okay but we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in posting. The posting says both: "This is a paid internship working full-time hours (40) per week." and "Schedule: Summer 2027". So we can include full-time hours under Schedule as well. But we might also keep it under Benefits. It's okay. Let's craft Schedule section:

  Schedule

  Summer 2027, full-time hours (40) per week.

  Now we need to ensure we don't have empty sections. Check each section content: About the role: paragraph. Responsibilities: list. Requirements: list. Skills: list (AutoCAD Civil 3D or Microstation). Could also include collaboration etc but that's covered. Benefits: list. Pay:

  Paid internship.

  Schedule:

  Summer 2027, full-time hours (40) per week.

  We might also include a section "About the company" from Why join us? but that's not in the prescribed headings list. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not add extra headings. The "Why join us?" paragraph could be considered part of About the role? But it's about company. However we must not invent sections. We could incorporate that paragraph into About the role? The About the role currently is the "What We're Looking For" paragraph. We could add the company description there as additional prose. That would preserve all substantive information. Let's do that: combine both paragraphs under About the role. Thus About the role will have two paragraphs: first about looking for student, second about company description and values. We'll keep it as

  ...

  ...

  . Now we need to ensure we didn't include Qualifications section (we omitted). That's okay because we have Requirements covering qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we can skip Qualifications. Now check for any other specifics: Location: Birmingham, AL; Number of positions available: 1. Should we include those? They are metadata but not in headings list. Could we include them in About the role as a short paragraph? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location and number of positions as a short paragraph maybe under About the role or separate? Since we don't have a heading for metadata, we can fold into a short

  . Let's add a paragraph after the About the role paragraphs: "

  Location: Birmingham, AL. Number of positions available: 1.

  " That preserves info. Now check for any other specifics: "You must be at least 18 years of age." included in Requirements. Now ensure we didn't include any boilerplate: EEO etc removed. Now output HTML fragment only. Let's construct:

  About the role

  Are you a hard-working and dedicated college student who is looking to gain valuable work experience in your field? Do you want to gain experience while learning from great mentors and leaders? Barge Design Solutions is looking for someone like you to intern next summer.

  Barge Design Solutions, Inc., is an engineering and architecture firm with diverse in-house multidisciplinary practice areas. The employee-owned company is more than 550+ people strong and serves clients nationwide from multiple U.S. locations. Barge is ranked on Engineering News-Record (ENR)’s Top 500 Design Firms and Architectural Record’s Top 300 Architecture Firms and is a certified Great Place To Work®. Our Primary Purpose For Being In Business Is Ultimately To Create a Better Life By Unleashing The Potential Of Our People, Clients And Communities. This Purpose Is Supported By Our Company’s Core Values Because At The End Of The Day, Barge CARES Collaborate – Help and expect help. Teamwork is essential in what we do. Authentic – Honesty, integrity and trust are at the heart of everything we do. We are who we say we are. Responsible – We are accountable for our work, our attitude, and our actions. We make Barge better. Excellence – We go all in and expect more of ourselves than others expect of us. Service – We are humble. We use our gifts in service of others. We believe that if we are living out our purpose for being in business and integrating our values into everything we do, we will ultimately achieve our vision to be the firm best known for being selected when it matters most.

  Location: Birmingham, AL. Number of positions available: 1.

  Responsibilities

  • Collaborating with team members on new ideas/innovations
  • Supporting Engineers in completing project deliverables
  • Using AutoCAD Civil 3D or Microstation
  • Preparing construction documents

  Requirements

  • Pursuing a Bachelor’s degree or Master’s degree from an accredited university