Structural Engineering Intern

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have: - About the role: description of role day to day, what you will create, success look like. Could be under "About the role". We'll put prose. - Responsibilities: list of responsibilities (bulleted). We have a list: Develop calculations..., Build understanding..., Work with engineering..., Complete twelve weekly modules..., Collaborate..., Attend site visits..., Gain exposure... - Requirements/Qualifications: There's "Required Qualifications" and "Preferred Qualifications". Could combine into "Qualifications" section with required and preferred? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "Requirements" for required qualifications, and maybe "Preferred Qualifications" as a subsection? But we only have allowed headings list; we could use "Qualifications" to cover both required and preferred, maybe separate with

or

. Probably better: "Requirements" for required qualifications, and "Preferred Qualifications" maybe not a standard heading but we could still use

Preferred Qualifications? The list includes "Qualifications" as an example; we could use that heading for both required and preferred. But we also have "Skills" heading; we could put skills there. However the posting includes "Basic knowledge of AutoCAD or Revit", "Basic knowledge of Adobe Suite...", "Strong problem-solving skills", etc. Those are skills/qualifications. Could put under "Skills". But also there are "Preferred Qualifications" like exposure to lateral systems, etc. Might be better to have two sections: "Required Qualifications" and "Preferred Qualifications". However the instruction says use headings like those examples; not strictly limited to those, but we should follow examples. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; we could also use others if needed but better to stick to those. So we need to map content to those headings. We have Pay: wage range $21.00 to $26.00 per hour. Also note actual pay determined based on factors, annual performance bonus. That's pay info. So we can have

Pay

with that info. Schedule: Not mentioned besides in-person internship. No schedule details. So we should not create Schedule section. Benefits: The posting mentions "We offer a competitive benefits package, work opportunities in a variety of locations and markets, and a company culture that celebrates all the unique viewpoints..." That's benefits info. So we can have

Benefits

with that prose. Skills: Could list skills like AutoCAD/Revit, Adobe Suite, Microsoft Office, Outlook, Bluebeam, problem-solving, collaboration, communication. Could be under Skills. Requirements: Could list required qualifications (completion of 3+ years, basic knowledge of software, problem-solving, collaboration, communication). Could be under Requirements. Qualifications: Could list preferred qualifications (exposure to lateral systems, structural analysis software, interest in seismic engineering, familiarity with mass timber etc). Could be under Qualifications. About the role: Could be introductory paragraph describing role. Responsibilities: list as above. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, contact, agency note, etc. Also remove "Did you know that some people hold back..." etc. Also remove "Things to Note" about pay determination? Actually pay determination is relevant to Pay section; we can include that. But "Things to Note" includes pay determination, annual bonus, work authorization, etc. Some of that is relevant to Pay and maybe other sections. We'll incorporate pay determination and annual bonus into Pay section. Work authorization and visa sponsorship maybe not needed; could be omitted as not required? It's substantive but not under headings; we could maybe put in a

under Pay or a separate "Eligibility" but not in list. Since we only have allowed headings, we could incorporate work authorization into Pay or Benefits? Probably better to include a short

under Pay about eligibility? But the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. If we don't have a heading for it, we could put it in a

after the sections, not as a heading. That's allowed: we can have prose outside headings. The instruction says use headings for sections; we can still have

elements not under headings. So we can add a

for work authorization etc after sections. We must not include duplicated lines, cookie/navigation/legal/EEO etc. Remove EEO statement, contact, agency note. Now craft HTML. Structure:

About the role

...

Responsibilities

• ...
...

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

Proficiency with AutoCAD or Revit, Adobe Suite, Microsoft Office, Outlook, Bluebeam; strong problem‑solving, collaboration, and communication abilities.

But we already listed many skills in Requirements; maybe Skills section could summarize. However we might be duplicating. The instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one "Qualifications" section with required and preferred subheadings? But we only allowed headings list; we could still use

Qualifications

and inside have

for required and

for preferred? Might be messy. Better to have: About the role, Responsibilities, Qualifications (covering both required and preferred), Benefits, Pay. Skills maybe not needed if covered in Qualifications. But we have a separate Skills heading in examples; we could use it to list skills like software proficiency etc. However the required qualifications already list those skills; we could move them to Skills and keep Qualifications for preferred only. Let's think. We need to preserve all substantive info. If we put required qualifications under Skills, we still preserve. But the heading "Skills" is appropriate for those skill-based items. Then "Qualifications" can hold preferred qualifications (exposure etc). That seems reasonable. Thus:

About the role

...

Responsibilities

...

Skills

• 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

Benefits

We offer a competitive benefits package, work opportunities in a variety of locations and markets, and a company culture that celebrates all the unique viewpoints and personalities that make up our talented team.

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.

After that, we need to include work authorization info: "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." Also maybe mention "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." That's substantive; we could put in a

after Pay. We must not include EEO etc. Thus final HTML fragment:

About the role

This is an in-person internship supporting our Structural Engineering team on real client projects. You will build a base foundation of engineering principles and code requirements, working with engineering teams on active projects and assignments, 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 building types including education, commercial, and healthcare. Success looks like completing twelve weekly modules taught by structural engineers throughout the company, 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

Skills

• 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

Benefits

We offer a competitive benefits package, work