Structural Engineer II Dulut

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. The posting includes: About the role (intro paragraph). Responsibilities list. Requirements (position requirements). Qualifications maybe same as requirements? The posting includes "Position Requirements:" and also "Preferred experience..." etc. Also "Physical Requirements and Demands:" maybe part of Requirements. There's also "Be Part of Something Bigger" which is more about company culture; could be part of About the role? Might be separate but not a required heading. The instructions: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only if posting has real specific content. We have: - About the role: we have introductory paragraph(s) describing role. We'll put that in

About the role

then

...

. - Responsibilities: list of duties. We'll put

Responsibilities

then

• ...

. - Requirements: includes Bachelor's degree, 2+ years experience, EIT required, ability to obtain in 6 months, track record, ability to work independently, preferred experience with software, understand 2D/3D drafting, firm knowledge of design codes. Also physical requirements? Might be separate but we can include under Requirements or maybe a separate "Physical Requirements" but not in list of allowed headings. Since only allowed headings are those given, we could incorporate physical requirements into Requirements section as part of content. Or we could omit if not fitting. Better to include them in Requirements. - Qualifications: maybe not distinct; but we could treat "Position Requirements" as Qualifications? However we already have Requirements. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to include Qualifications if there is distinct content. The posting includes "Preferred experience with engineering/design software such as..." and "Understand 2-D and 3-D drafting techniques" and "Firm knowledge of design codes". Those could be Qualifications or Skills. Could split: Requirements = education, experience, EIT. Qualifications = technical knowledge, software, codes. Skills = maybe software proficiency? But we have limited time. Better to follow typical: Requirements = education/experience; Qualifications = technical knowledge/skills; Skills = software proficiency. However we need to avoid thin sections. Let's see content: Education: Bachelor's Degree in Civil or Structural Engineering from an ABET accredited university. Experience: 2+ years’ experience as a structural engineer. EIT required, or ability to obtain in 6 months. Track record of successful completion of projects. Ability to work independently and in close collaboration with others. Preferred experience with engineering/design software such as AutoCAD Civil 3D, RISA 3D, Navisworks, Bluebeam REVU, etc. Understand 2-D and 3-D drafting techniques. Firm knowledge of design codes including: ASCE 7, AISC 360, ACI 318, etc. Physical Requirements and Demands: Frequent sitting for long periods. Occasional lifting in up to 50lbs. Ability to work extra hours and possible overtime when projects demand. Thus we could have: - Requirements: education, experience, EIT, track record, ability to work independently/collaboratively. - Qualifications: knowledge of design codes, understanding of 2D/3D drafting. - Skills: proficiency with software (AutoCAD Civil 3D, RISA 3D, Navisworks, Bluebeam REVU, etc.) maybe also physical demands? But physical demands could be under Requirements or separate but not a heading. Given the instruction to prefer few substantive sections over many thin ones, maybe combine Qualifications and Skills into one section called "Qualifications & Skills". But headings list includes both; we could include both if they have content. However we risk thin sections. Let's see if we can make each substantive. Qualifications: knowledge of design codes (ASCE 7, AISC 360, ACI 318), understanding of 2D/3D drafting techniques. Skills: proficiency with AutoCAD Civil 3D, RISA 3D, Navisworks, Bluebeam REVU, etc. That seems substantive enough. Benefits: list provided. Pay: salary range $78,000 – $94,000 per year. Schedule: not explicitly mentioned; there is mention of ability to work extra hours and possible overtime, but not a defined schedule. So we should not create Schedule section because no specific schedule content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, Bias-Free Hiring Practices, etc. Also remove "Be Part of Something Bigger – Join the Team at Lake Superior Consulting!" maybe considered marketing but could be part of About the role? It's not boilerplate but it's promotional; we could keep as part of About the role? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Be Part of Something Bigger..." is not boilerplate but could be considered marketing fluff; but it's substantive about company culture. Might keep as part of About the role. However we already have an intro paragraph; we could combine. Let's extract the About the role content: "Lake Superior Consulting is seeking a Structural Engineer II Dulut to join our team. Lake Superior Consulting is seeking a skilled Structural Engineer to join our Facilities Engineering group. This mid‑level role is responsible for project engineering tasks that require sound judgment and independent decision-making. The Structural Engineer II plans and executes engineering work involving the evaluation, selection, application, and adaptation of established structural engineering techniques and criteria. The successful candidate will develop practical solutions to design challenges, prepare and revise drawings, specifications, and calculations, and oversee work to ensure compliance with applicable codes, standards, and accepted engineering practices." There's duplication: first two sentences repeat. We should deduplicate. We'll combine into a concise paragraph preserving all substantive info: Lake Superior Consulting is seeking a Structural Engineer II to join our Facilities Engineering group. This mid‑level role is responsible for project engineering tasks that require sound judgment and independent decision‑making. The Structural Engineer II plans and executes engineering work involving the evaluation, selection, application, and adaptation of established structural engineering techniques and criteria. The successful candidate will develop practical solutions to design challenges, prepare and revise drawings, specifications, and calculations, and oversee work to ensure compliance with applicable codes, standards, and accepted engineering practices. Now Responsibilities list: we need to extract each bullet. List from posting: - Perform structural design and analysis calculations using governing codes and standards, engineering formulas, skills, and experience. - Layout and detail entire or portions of projects under the supervision of the Engineer of Record - Provide CAD drawings or sketches to incorporate in drawings by Designers/Drafters - Research design options and document findings for Engineer of Record - Review shop drawings - Assume the lead engineer’s role on assigned projects - Direct and supervise other Engineer’s activities as needed - Work with, and direct, Designers/Drafters to create project drawings - Attend and participate in Client meetings - Perform field activities such as observing and recording existing field conditions; taking and verifying measurements within project area - Organize, draft, and coordinate technical documents - Serve as the project engineer by leading design and engineering effort - Work either independently or closely with others in a team environment on construction plans with clients, architects, and other professionals - Shows engineering judgement to determine adaptations in methods for non-routine aspects of assignments. We'll put each as

. Now Requirements: we need to list: - Bachelor’s Degree in Civil or Structural Engineering from an ABET accredited university - 2+ years’ experience as a structural engineer - EIT required, or ability to obtain in 6 months - Track record of successful completion of projects - Ability to work independently and in close collaboration with others - Physical Requirements and Demands: Frequent sitting for long periods. Occasional lifting in up to 50lbs. Ability to work extra hours and possible overtime when projects demand. We could incorporate physical demands as part of Requirements. Now Qualifications: - Firm knowledge of design codes including: ASCE 7, AISC 360, ACI 318, etc. - Understand 2-D and 3-D drafting techniques Now Skills: - Preferred experience with engineering/design software such as AutoCAD Civil 3D, RISA 3D, Navisworks, Bluebeam REVU, etc. Now Benefits list: - Medical, Dental, Vision Insurance - Flexible work options - 401K (6% company match) - Company paid life, AD&D, and short/long term disability - Paid time off (PTO) - Paid holidays (twelve per year) - Tuition reimbursement Now Pay: - The anticipated salary range for this position is $78,000 – $94,000 per year. We'll put that in a

under Pay heading. Now ensure we don't include any boilerplate like "Bias-Free Hiring Practices: Lake Superior Consulting is proud to be an Equal Employment employer..." Remove. Also remove "If you’re driven, curious, and ready to grow your career while making a difference, we want to hear from you." That's application encouragement; maybe considered application instructions? It's not exactly instruction to apply but could be considered promotional; but we can keep as part of About the role? It's not substantive about role; it's a call to action. Safer to remove. Also remove "At LSC, you’ll have the opportunity to collaborate with top-tier talent and take on meaningful projects in industries including Liquids and Natural Gas, Power, Mining, Water and Wastewater, Renewables, and Manufacturing." That's also promotional but could be part of About the role? It's about company and projects; maybe keep as part of About the role? It's not boilerplate but it's about company culture; could be considered part of About the role. However we already have About the role describing role; adding this may be okay. But to keep sections thin, maybe we incorporate into About the role as extra sentence. But the instruction: "Prefer a few substantive sections over many thin ones." Adding that sentence to About the role makes it more substantive. Let's include it. Thus About the role paragraph: combine the earlier paragraph plus the opportunity sentence. Let's craft: "Lake Superior Consulting is seeking a Structural Engineer II to join our Facilities Engineering group. This mid‑level role is responsible for project engineering tasks that require sound judgment and independent decision‑making. The Structural Engineer II plans and executes engineering work involving the evaluation, selection, application, and adaptation of established structural engineering techniques and criteria. The successful candidate will develop practical solutions to design challenges, prepare and revise drawings, specifications, and calculations, and oversee work to ensure compliance with applicable codes, standards, and accepted engineering practices. At LSC, you’ll have the opportunity to collaborate with top-tier talent and take on meaningful projects in industries including Liquids and Natural Gas, Power, Mining, Water and Wastewater, Renewables, and Manufacturing." Now we have all. Now produce HTML fragment:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...