Structural Engineering Intern

We need to output HTML fragment with sections: About the role? The description includes "Position Description Structural Engineering Intern at Cushing Terrell." We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have Pay: wage range $21-26 per hour. Also mention "Actual pay will be determined based on ..." but that's more detail; we can include Pay section with that info. Benefits: they mention "We offer a competitive benefits package" but not specifics; that's vague; we should not create Benefits unless specific. They also mention "work opportunities in a variety of locations and markets, and a company culture..." but not specific benefits like health, 401k. So we should not create Benefits section. Schedule: not mentioned; it's in-person internship but no schedule details. So omit Schedule. We need About the role: we can summarize day-to-day involvement, what you will create, success looks like. That's substantive. Responsibilities: list bullet points from "Position Responsibilities***" section. Requirements/Qualifications/Skills: The posting has Required Qualifications** and Preferred Qualifications**. Also includes skills like problem solving, communication, AutoCAD/Revit, Adobe Suite, etc. We need to decide how to split. The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Likely: Requirements = required qualifications; Qualifications = preferred qualifications? Skills = maybe technical skills like AutoCAD, Revit, Adobe Suite, Microsoft Office, Outlook, Bluebeam, problem solving, communication. But we have overlapping. We need to avoid duplication. Perhaps combine required and preferred into Qualifications? But we have separate headings. Let's think: The posting includes "Required Qualifications**" and "Preferred Qualifications**". Also includes skills like problem-solving, communication, etc. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and Skills as maybe the technical tools (AutoCAD, Revit, Adobe Suite, Microsoft Office, Outlook, Bluebeam). However problem-solving and communication are also skills. Might be okay to put them under Skills. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. Let's extract substantive content: - Position Description: Structural Engineering Intern at Cushing Terrell. In-person internship supporting Structural Engineering team on real client projects. - Day-to-day: build base foundation of engineering principles and code requirements, working with engineering teams on active projects and assignments, including lateral systems and load path work. - What will I create? help develop calculations, plans, and details for an example building, gaining exposure to structural design across building types including education, commercial, and healthcare. - Success: complete twelve weekly modules taught by structural engineers throughout the company, participate in site visits with project leads, leave with clear picture of what it means to work in the AEC industry. - Wage range: $21.00 to $26.00 per hour. - Required Qualifications: * Completion of 3+ years of a structural or civil engineering related undergraduate program * Basic knowledge of AutoCAD or Revit * Basic knowledge of Adobe Suite, Microsoft Office Suite, Outlook, and Bluebeam * Strong problem-solving skills and the ability to learn and adapt * Ability to effectively collaborate and communicate with team members across disciplines * Strong written and verbal communication skills - Preferred Qualifications: * Exposure to lateral systems or load path analysis * Exposure to structural analysis software such as RISA, RAM Structural System, ETABS, SAP2000, Enercalc, or TEDDS * Interest in seismic engineering or historic retrofits * Familiarity with mass timber, tilt-up concrete, or material handling and racking projects - Responsibilities: * Develop calculations, plans, and details for an example building under the guidance of structural engineers * Build understanding of lateral systems and load paths through weekly learning modules * Work with engineering teams on active projects and assignments * Complete twelve weekly modules taught by structural engineers throughout the company * Collaborate with interns and engineers across the company * Attend site visits with project leads when opportunities allow * Gain exposure to the variety of project types and teams across the firm - About company: Cushing Terrell is a multidisciplinary design firm with 16 offices and more than 500 team members... (we can include as About the role? maybe separate but we have only About the role heading; we could include company description there.) - Additional notes: Actual pay determined based on years of experience, licensure status, location, proficiency, other factors; eligible for annual performance bonus; must be authorized to work in US full-time; no visa sponsorship; mostly sitting office with limited physical requirements; may require bending, stretching, twisting, reaching. - EEO statement etc are boilerplate to remove. - Contact phone etc maybe not needed; it's not boilerplate? It's contact for assistance; could be considered minor metadata; we could fold into a short p. - Agency note etc boilerplate to remove. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove EEO statement, contact phone? The instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Contact phone is minor metadata; we could include a short p at end maybe. But we also must not include application instructions. The posting includes "Did you know that some people hold back..." that's encouragement to apply; that's basically application instruction? It's not exactly instruction to apply but encouraging. Might be considered boilerplate? It's not navigation/legal/EEO. It's more motivational. Might be okay to keep? The instruction says remove application instructions. That paragraph is encouraging to apply; could be considered application instruction. Safer to remove. Also remove "Things to Note" about actual pay etc? That's relevant to Pay section; we can incorporate into Pay. We must preserve all substantive information; we need to include the pay details and note about actual pay determination, performance bonus, work authorization, no visa sponsorship, physical requirements. We can include those in Pay section or maybe a separate "Notes" but we don't have a heading for Notes; we could fold into Pay section as a

after wage range. We must not create Benefits section unless specific; we have only generic "competitive benefits package" not specific; so omit Benefits. Schedule: not specified; omit. Now craft HTML:

About the role

Structural Engineering Intern at Cushing Terrell – an in‑person internship supporting the Structural Engineering team on real client projects. You will build a foundation of engineering principles and code requirements while working with engineering teams on active projects, including lateral systems and load path work. You will help develop calculations, plans, and details for an example building, gaining exposure to structural design across education, commercial, and healthcare projects. Success in the internship means completing twelve weekly modules taught by structural engineers, participating in site visits with project leads, and leaving with a clear picture of what it means to work in the AEC industry.

Responsibilities

• Develop calculations, plans, and details for an example building under the guidance of structural engineers
• Build understanding of lateral systems and load paths through weekly learning modules
• Work with engineering teams on active projects and assignments
• Complete twelve weekly modules taught by structural engineers throughout the company
• Collaborate with interns and engineers across the company
• Attend site visits with project leads when opportunities allow
• Gain exposure to the variety of project types and teams across the firm

Requirements

• Completion of 3+ years of a structural or civil engineering related undergraduate program
• Basic knowledge of AutoCAD or Revit
• Basic knowledge of Adobe Suite, Microsoft Office Suite, Outlook, and Bluebeam
• Strong problem‑solving skills and the ability to learn and adapt
• Ability to effectively collaborate and communicate with team members across disciplines
• Strong written and verbal communication skills

Qualifications

• Exposure to lateral systems or load path analysis
• Exposure to structural analysis software such as RISA, RAM Structural System, ETABS, SAP2000, Enercalc, or TEDDS
• Interest in seismic engineering or historic retrofits
• Familiarity with mass timber, tilt‑up concrete, or material handling and racking projects

Skills

• Problem‑solving and adaptability
• Collaboration and communication across disciplines
• Proficiency with AutoCAD or Revit
• Basic Adobe Suite, Microsoft Office, Outlook, Bluebeam
• Written and verbal communication

But we have duplicated skills; maybe we should not duplicate. The Skills heading could contain the technical tools and soft skills not already covered. However we already listed problem-solving etc in Requirements. To avoid duplication, we could move those to Skills and keep Requirements focused on education/experience. Let's restructure: Requirements: education completion, basic knowledge of AutoCAD/Revit, basic knowledge of Adobe Suite etc? Actually those are skills. Hmm. Better: Requirements = education and experience (completion of 3+ years). Qualifications = preferred qualifications. Skills = technical and soft skills (AutoCAD/Revit, Adobe Suite, problem solving, communication, collaboration). Let's do that. Thus: Requirements: - Completion of 3+ years of a structural or civil engineering related undergraduate program Qualifications (Preferred): - Exposure to lateral systems or load path analysis - Exposure to structural analysis software such as RISA, RAM Structural System, ETABS, SAP2000, Enercalc, or TEDDS - Interest in seismic engineering or historic retrofits - Familiarity with mass timber, tilt‑up concrete, or material handling and racking projects Skills: - Basic knowledge of AutoCAD or Revit - Basic knowledge of Adobe Suite, Microsoft Office Suite, Outlook, and Bluebeam - Strong problem‑solving skills and the ability to learn and adapt - Ability to effectively collaborate and communicate with team members across disciplines - Strong written and verbal communication skills Now Pay section:

Pay

The expected wage range for this position is $21.00 to $26.00 per hour. Actual pay will be determined based on the candidate's years of experience, licensure status, location, level of proficiency, and other job‑related factors (as permitted by law). This position is also eligible for an annual performance bonus.

We might also include work authorization note etc. Could add a short p after Pay: "Applicants must be currently authorized to work in the United States on a full‑time basis. Cushing Terrell will not sponsor applicants for work visas. The majority of the time, a person in this role will be sitting in an office with limited physical requirements; this may require individuals to bend, stretch, twist, and reach." But that's not Pay; maybe we could add a separate section? There's no heading for "Notes". Could fold into Pay as additional paragraphs. We must not create Schedule or Benefits. Now About the role: include company description? Could add a short paragraph about Cushing Terrell after the role description. That is substantive. Let's craft About the role:

Structural Engineering Intern at Cushing Terrell – an in‑person internship supporting the Structural Engineering team on real client projects. You will build a