Welding Foreman

We need to output HTML fragment with sections: About the role? Actually "About Loenbro" is company description, not necessarily a section heading? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About Loenbro (company description) could be "About the role"? Actually "About the role" is not present; we have "Position Summary". Could map to "About the role". But they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use those headings if content exists. We have: Position Summary: a paragraph describing role. Essential Responsibilities: list of duties. Required Qualifications: list. Preferred Qualifications: list (could be under Qualifications? Might combine? But we can have Qualifications section containing both required and preferred? The instruction: use headings for sections; we can have Qualifications (maybe split into Required and Preferred?). But they said prefer a few substantive sections over many thin ones. Could combine Required and Preferred into Qualifications section with sub-lists? But we need to follow instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (position summary), Responsibilities, Qualifications (maybe combine required and preferred), Skills (knowledge, skills, abilities), Benefits. No Pay or Schedule as not specified. We must not repeat job title as heading. Also not include Job ID etc. We must remove boilerplate: EEO, etc. At end there is "Loenbro is an Equal Opportunity Employer" - remove. Also remove "Guided By Core Values..." maybe not boilerplate? It's somewhat fluff but could be considered part of company description; but it's not essential? It's not a list; we could keep as part of About Loenbro paragraph? It's not required but we can keep as part of About Loenbro description. However it's somewhat generic; but it's not boilerplate like EEO. Might keep. We need to preserve all substantive information; do not invent or summarize away detail. Thus we will output:

About the role

Position Summary: The Welding Foreman is responsible for supervising and coordinating welding crews engaged in the fabrication, installation, maintenance, and repair of structural steel, piping, utility, industrial, and construction projects. This role ensures all welding activities are performed safely, efficiently, and in compliance with project specifications, quality standards, welding procedures, and applicable codes. The Welding Foreman provides leadership in the field while serving as the primary point of contact between craft personnel, inspectors, and project management.

But we also have About Loenbro paragraph earlier; maybe we include that under About the role? Actually About Loenbro is company description; could be part of About the role? Might be better to have a separate "About Loenbro" but not in allowed headings. Could incorporate into About the role paragraph? Might be okay to include as part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use

for section headings (e.g. About the role...). Likely they expect only those headings. So we should map company description to About the role? Might be odd but okay. Alternatively we could have a section "About Loenbro" as

but not in list; risk of being considered not following instruction. Safer to stick to given headings. Thus we will put company description inside About the role paragraph. Now Responsibilities: list of essential responsibilities. We'll output

Responsibilities

• ... each item. We need to preserve all items exactly as given. List items from Essential Responsibilities: - Lead and supervise welding crews to ensure safe, productive, and high-quality work. - Plan and coordinate daily welding activities, manpower, equipment, and material requirements. - Review project drawings, welding procedures, specifications, and schedules to ensure proper execution of work. - Ensure compliance with all company safety policies, OSHA regulations, and client requirements. - Conduct daily safety meetings and reinforce safe work practices. - Verify that all welding is performed according to approved Welding Procedure Specifications (WPS) and applicable codes. - Coordinate fit-up, welding, grinding, fabrication, and installation activities. - Monitor weld quality and productivity to ensure project schedules and quality standards are achieved. - Work closely with quality control personnel, inspectors, and project management to address welding-related issues. - Ensure proper maintenance and operation of welding equipment, tools, and support equipment. - Maintain accurate daily reports, production tracking, labor hours, and project documentation. - Assist with weld testing, inspections, and corrective actions when required. - Train, mentor, and develop welders and helpers to improve skill levels and performance. - Identify and resolve field issues that could impact safety, quality, or project timelines. - Coordinate material deliveries and ensure welding consumables are properly stored and controlled. Now Qualifications: we have Required Qualifications and Preferred Qualifications. Could combine into one Qualifications section with two subheadings? But we cannot add extra headings beyond

  . Could just list all qualifications (required and preferred) as list items, maybe marking preferred? But we need to preserve distinction? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we combine required and preferred without labeling, we lose distinction. Could we include a note inside list items like "(Preferred)"? That would be adding info not present. Better to keep two sub-sections under Qualifications using

  ? Not allowed. Could we have two separate Qualifications sections? That would be repetitive heading. Might be okay to have two

  Qualifications

  sections? That would be duplicate headings; not ideal. Alternative: Use "Requirements" heading for required qualifications, and "Skills" heading for knowledge, skills, abilities, and maybe preferred qualifications could go under Skills? But preferred qualifications include certifications and experience; those are more like qualifications. We could use headings: Requirements (for required qualifications), Skills (for knowledge, skills, and abilities), and maybe Qualifications (for preferred). But the instruction list includes Requirements, Qualifications, Skills as possible headings. So we can map: - Requirements: Required Qualifications - Qualifications: Preferred Qualifications - Skills: Knowledge, Skills, And Abilities That seems reasonable and uses allowed headings. Thus:

  Requirements

  list of required qualifications.

  Qualifications

  list of preferred qualifications.

  Skills

  list of knowledge, skills, and abilities. Now Benefits: we have benefits list.

  Benefits

  list. Now we need to ensure we don't include Pay or Schedule sections as not specified. We also need to include location etc? The posting includes Location: Andrews, TX / On-site, Reports to: Site Superintendent, Employment Type: Full-Time FLSA Classification: Non-Exempt. This is metadata; we can fold into a short

  or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph with location, reports to, employment type, FLSA classification. That's minor metadata; we can include as a

  after About the role maybe. We should not repeat job title as heading. Thus final HTML:

  About the role

  Position Summary: The Welding Foreman is responsible for supervising and coordinating welding crews engaged in the fabrication, installation, maintenance, and repair of structural steel, piping, utility, industrial, and construction projects. This role ensures all welding activities are performed safely, efficiently, and in compliance with project specifications, quality standards, welding procedures, and applicable codes. The Welding Foreman provides leadership in the field while serving as the primary point of contact between craft personnel, inspectors, and project management.

  Location: Andrews, TX / On-site. Reports to: Site Superintendent. Employment Type: Full-Time. FLSA Classification: Non-Exempt.

  Then sections. Make sure to not include any extra text outside HTML fragment. Let's craft. Check for any boilerplate removal: At end there is "Guided By Core Values (LEAD), Grounded In Grit And a Commitment To Excellence, Loenbro Betters Our Families, Customers, And Local Communities. If You’re Ready To Be Part Of a Company That LEADS By Living with Integrity Exceeding Expectations Acting with Urgency Delivering Excellence …we want to hear from you." This is somewhat fluff but maybe considered motivational; could be considered part of About Loenbro? It's not a list; we could include it in About the role paragraph? It's not essential but it's substantive? It's more marketing fluff; but it's not boilerplate like EEO. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. Could keep but it's vague. Might be okay to include as part of About Loenbro description. However we already used About the role for position summary; we could add another paragraph after that with that fluff. But it's not required; we could drop it as it's not essential detail about role. The instruction says preserve ALL substantive information; is that substantive? It's more about company values; could be considered substantive but not critical. Safer to keep it as part of About Loenbro description. But we already used About the role for position summary; we could add a second paragraph under About the role containing that values statement. However that might be considered filler? It's not placeholder like "commensurate with experience". It's actual content. I'd include it. Thus About the role section will have two paragraphs: position summary and company values/description. Now we need to ensure we don't duplicate lines. Now produce final HTML. Let's draft:

  About the role

  Position Summary: The Welding Foreman is responsible for supervising and coordinating welding crews engaged in the fabrication, installation, maintenance, and repair of structural steel, piping, utility, industrial, and construction projects. This role ensures all welding activities are performed safely, efficiently, and in compliance with project specifications, quality standards, welding procedures, and applicable codes. The Welding Foreman provides leadership in the field while serving as the primary point of contact between craft personnel, inspectors, and project management.

  Loenbro is a trusted, long-term construction lifecycle partner to thousands of customers across the U.S. Our market spans all industries and our service offerings include Critical Electrical, Mechanical & Structural, Soft Crafts, Inspection, Underground Maintenance and Installation, and Fabrication. Our expertise lies in simplifying the complex and establishing long-standing relationships with our partners. We have a national presence but a local approach—every customer benefits from our capabilities and our care. At Loenbro, we don’t just offer jobs—we build careers grounded in integrity, teamwork, excellence, and purpose. Join a team where your expertise is valued, your growth is supported, and your work helps maintain and enhance the critical infrastructure that powers communities across the nation. Guided By Core Values (LEAD), Grounded In Grit And a Commitment To Excellence, Loenbro Betters Our Families, Customers, And Local Communities. If You’re Ready To Be Part Of a Company That LEADS By Living with Integrity Exceeding Expectations Acting with Urgency Delivering Excellence …we want to hear from you.

  Location: Andrews, TX / On-site. Reports to: Site Superintendent. Employment Type: Full-Time. FLSA Classification: Non-Exempt.

  Then Responsibilities, Requirements, Qualifications, Skills,