Structural Engineer III

We need to output only HTML fragment, using

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must include sections only when posting has real, specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove things like "Job Summary" maybe considered heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. We have sections: Job Summary (maybe "About the role"?), Job Duties And Responsibilities (Responsibilities), Qualifications (Knowledge, Skills And Abilities) (Qualifications), Work Environment (maybe Benefits? but not exactly), Physical Requirements (maybe Requirements?), Other sections like Drug Free Workplace, Equal Opportunity Employer (boilerplate to remove). Also there is "Industry *Industrial Services Position Structural Engineer III Req Code 3032 General Location Columbus" etc. We should not repeat job title. Also we should not include Job ID/requisition numbers as headings; fold minor metadata into a short

or drop it. So we can include a short paragraph with location, industry, etc. We need to include only sections with real specific content. Let's identify content: - About the role: could be Job Summary paragraph. - Responsibilities: Job Duties And Responsibilities (multiple bullet points). We'll need to convert to

• . - Requirements: maybe Physical Requirements? Also maybe "Required Qualifications" is more qualifications. But we have Qualifications section separate. The instruction lists Requirements as a possible heading. Could use for "Physical Requirements" or "Eligibility"? We have "Physical Requirements (With or Without Reasonable Accommodations):" list. That seems like requirements. Also "Eligible for US Work Authorization Sponsorship: No" etc are metadata; we can drop or put in short p. - Qualifications: we have "Qualifications (Knowledge, Skills And Abilities)" with Required Qualifications and Preferred Qualifications. That's a good section. - Skills: maybe we can extract from Qualifications? But we already have Qualifications covering skills. Could we create a Skills section? The instruction says use headings like Skills if there is content. We could put technical skills list there. But we must not create thin sections. Better to keep Qualifications as one section covering required and preferred qualifications, which includes skills. So we may not need separate Skills. - Benefits: we have Work Environment description: "Private / Semi-private office in a fun, relaxed work environment with option for hybrid remote schedule Interaction with other team members as well as supervisors and clientpersonnel Healthy work-life balance with a variety of social activities as well as regular staff breakfasts and lunches May be required to travel out of town on a periodic basis to obtain project field data or attend project meetings Occasional presence on construction sites with applicable safety requirements". That's more about work environment, not benefits like health insurance etc. Could treat as Benefits? The instruction says include Benefits section only if posting actually states them. It does mention work environment, hybrid remote schedule, social activities, staff breakfasts/lunches. That could be considered benefits. We'll include a Benefits section with that content. - Pay: not mentioned. So omit. - Schedule: not explicitly mentioned; there is hybrid remote schedule but not schedule details. Could be considered schedule? The posting says "option for hybrid remote schedule". That's schedule info. Could include Schedule section with that detail. But we already have hybrid remote schedule in Benefits. Might be redundant. Better to put schedule info under Benefits or Schedule? Since we have no explicit schedule like "Full-time, 40 hrs/week", we could omit Schedule. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "option for hybrid remote schedule" which is schedule info. So we could create a Schedule section with that. However we also have work environment details. Might be better to have Benefits for work environment and social activities, and Schedule for hybrid remote schedule. Let's see. We need to avoid filler placeholder text. All content we include must be substantive. Let's extract specifics: Job Summary paragraph: "The Structural Engineer is responsible for the analysis, design, and detailing of structural systems supporting industrial facilities and infrastructure projects within the power generation, power transmission & distribution, bulk material handling, and oil & gas industries. The position will support the development of structural engineering deliverables from conceptual design through construction while working under the guidance of senior engineers and project managers. The Structural Engineer will perform design and analysis of steel and concrete structures, foundations, equipment support systems, pipe racks, conveyor support structures, substations, and other industrial facilities. This role requires strong technical skills, attention to detail, and the ability to work effectively within multidisciplinary project teams. The successful candidate will contribute to project execution, field investigations, engineering studies, construction support, and the continued growth of EDG's structural engineering services in the Columbus office." That's substantive. Responsibilities: list under "Job Duties And Responsibilities". We have subheadings: Structural Engineering and Design, Design Production and Coordination, Quality and Project Support, Professional Development. Each has bullet-like sentences. We'll need to convert each sentence into
• maybe grouping under subheadings? But instruction only says use
  • for any list of duties/requirements/benefits. It doesn't forbid headings inside list? Probably we can keep subheadings as

    ? But only allowed headings are

    for section headings. We could keep subheadings as plain text or . Safer to just make a flat list of all duties. But we might lose some grouping. However we must preserve ALL substantive information; we can keep the subheadings as part of

    text. That's fine. Let's extract each duty sentence: From Structural Engineering and Design: - Prepare structural engineering calculations, analyses, and design documents for industrial and infrastructure projects. - Design steel and reinforced concrete structures utilizing applicable industry codes and client standards. - Assist in the design of: structural steel buildings, equipment support structures, pipe racks, conveyor galleries and transfer towers, foundations, retaining walls, platforms and access structures, substation support structures, industrial structures associated with power generation and oil & gas facilities. - Develop structural loading criteria including dead, live, wind, seismic, equipment, and operational loads. - Perform foundation analysis and design using geotechnical information and project requirements. - Prepare engineering calculations, technical reports, and design narratives. - Support structural condition assessments and evaluations of existing facilities. - Participate in field investigations and site visits to collect information necessary for engineering design. Design Production and Coordination: - Develop and review construction drawings, plans, details, and specifications. - Coordinate with structural designers and drafters in the development of engineering drawings and 3D models. - Utilize structural analysis software to model and analyze structures and foundations. - Participate in interdisciplinary coordination with mechanical, civil, process, electrical, and instrumentation engineers. - Assist in resolving design-related issues that arise during project execution and construction. Quality and Project Support: - Support internal quality control reviews and design checks. - Verify compliance with applicable building codes, industry standards, project specifications, and client requirements. - Maintain organized project files, calculations, and documentation. - Assist project managers with scope development, schedule tracking, and engineering progress reporting. - Review vendor drawings and supplier documentation for compliance with project requirements. - Support construction activities through engineering responses, field observations, and site support as required. Professional Development: - Work under the mentorship of senior structural engineers and discipline leads both locally and across EDG’s global footprint. - Pursue increasing responsibility in project execution and technical leadership. - Participate in training and continuing education activities. - Develop knowledge of industry best practices and emerging design technologies. - Progress toward Professional Engineer (PE) licensure, if not already licensed. Now Qualifications (Knowledge, Skills And Abilities): Required Qualifications: - Bachelor of Science degree in Civil Engineering with a Structural emphasis or Structural Engineering. - Five (5) with less than ten (10) years of structural engineering experience. (Seems typo: "Five (5) with less than ten (10) years". We'll keep as is.) - Engineer-in-Training (EIT) certification required. - Working knowledge of structural engineering design principles for steel and concrete structures. - Experience applying structural design codes and standards including: AISC, ACI, ASCE 7, International Building Code (IBC) - Proficiency with structural analysis software such as: RISA-3D, STAAD.Pro, RAM Structural System - Working knowledge of: Autodesk Revit and AdvancedSteel, AutoCAD, Navisworks - Strong analytical and problem-solving abilities. - Strong written and verbal communication skills. - Ability to manage multiple assignments simultaneously. - Ability to travel periodically to client facilities and project sites. Preferred Qualifications: - Experience in one or more of the following industries: Power Generation, Electric Transmission & Distribution, Bulk Material Handling and/or Oil & Gas. - Progress toward Professional Engineer (PE) registration. - Experience supporting multidiscipline engineering projects. - Familiarity with industrial facility design and construction practices. - Experience using BIM and 3D coordination platforms. Work Environment (maybe Benefits): - Private / Semi-private office in a fun, relaxed work environment with option for hybrid remote schedule - Interaction with other team members as well as supervisors and clientpersonnel - Healthy work-life balance with a variety of social activities as well as regular staff breakfasts and lunches - May be required to travel out of town on a periodic basis to obtain project field data or attend project meetings - Occasional presence on construction sites with applicable safety requirements Physical Requirements (maybe Requirements): - Ability to perform light to moderate lifting - Clarity of speech and hearing or other communication capabilities, which permits employee to communicateeffectively - Sufficient vision or other powers of observation, to use a computer as well as conduct analysis andinvestigations - Sufficient personal mobility, physical reflexes, and manual dexterity, to perform office duties and travel when necessary to off-sitelocations We also have some metadata: Industry *Industrial Services Position Structural Engineer III Req Code 3032 General Location Columbus, etc. We can include a short paragraph at top: maybe

    Industrial Services, Structural Engineer III, Columbus.

    but we must not repeat job title as heading. It's okay to include in paragraph. We must remove boilerplate: Drug Free Workplace, Equal Opportunity Employer, etc. Now decide sections: - About the role: Job Summary paragraph. - Responsibilities: list of duties (maybe grouped under subheadings but we can just list). - Requirements: Could include Physical Requirements. Also maybe "Ability to travel periodically" is already in qualifications. But we can keep Physical Requirements as Requirements. - Qualifications: Required and Preferred Qualifications. - Benefits: Work Environment details. - Schedule: maybe hybrid remote schedule is already in Benefits; but we could put schedule info there. Since we already have hybrid remote schedule in Benefits, we could omit separate Schedule. We need to avoid thin sections. Benefits section has multiple items, good. Now produce HTML fragment:

    About the role

    ...Job Summary...

    Responsibilities

    • ... each duty ...
    ...

    Requirements

    • Ability to perform light to moderate lifting
    • Clarity of speech and hearing or other communication capabilities, which permits employee to communicate effectively
    • Sufficient vision or other powers of observation, to use a computer as well as conduct analysis and investigations
    • Sufficient personal mobility, physical reflexes, and manual dexterity, to perform office duties and travel when necessary to off-site locations

    Qualifications

    • <