Lead Certified Welding Inspector (CWI)

We need to output only HTML fragment, with headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Keep substantive info. We need to parse the posting: It includes sections: "What You'll Do" with subsections: Quality Control Leadership, Welding & Inspection Program, ASME & Code Compliance, Quality Systems & Documentation. Then "What We're Looking For" with Required Qualifications and Preferred Qualifications. Then "Why Join Hohl Industrial Services?" (maybe Benefits? Actually it's about why join). Then "Physical & Work Environment". Then company description maybe not needed? It's substantive but maybe part of About the role? The instruction: include a section only when posting has real, specific content for it. So we need to decide which sections to include: About the role (maybe from first paragraph?), Responsibilities (What You'll Do), Requirements/Qualifications (Required Qualifications), Skills (maybe from required qualifications?), Benefits (Why Join?), Pay (none), Schedule (none). We should not create Pay or Schedule sections if not present. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive information, not invent or summarize away detail. So we need to include details like responsibilities bullet points, qualifications bullet points, etc. We need to remove boilerplate: EEO statement, "Job Posted by ApplicantPro", maybe the company description at end? It's substantive but maybe not needed? It says "Hohl Industrial Services, Inc. established in 1950..." That's about the company; could be considered part of About the role? But we have no explicit About the role section; we could create an About the role section using the introductory paragraph before "What You'll Do". That paragraph: "Hohl Industrial Services, Inc. is seeking an experienced and highly skilled Lead Certified Welding Inspector (CWI) to lead the technical Quality Control function across our shop and field operations. This is a critical leadership position for an individual who takes pride in precision, technical excellence, and ensuring that every project meets the highest standards of quality, safety, and compliance. As our Lead CWI, you will serve as the Company's senior technical quality resource, providing direction to QC Inspectors and working closely with Operations, project teams, customers, and quality representatives. You will play a key role in overseeing welding, fabrication, inspection, testing, and code compliance across a variety of industrial projects. If you are a knowledgeable welding and quality professional who enjoys solving technical challenges, mentoring others, and making a direct impact on project success, we want to hear from you!" That's good for About the role. Then Responsibilities: we can combine the "What You'll Do" sections into a list. Could break into subheadings? But we only allowed

  for section headings; we could have subheadings as

  ? Not allowed? The instruction only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use

  for main sections and use

  or

  inside. Thus we will have:

  About the role

  ... (the intro paragraph)

  Responsibilities

  • Lead and provide technical direction to QC Inspectors.
  • Develop and implement inspection plans, inspection methods, hold points, and acceptance criteria for shop and field activities.
  ... etc. We need to include all bullet points from the sections under What You'll Do. Let's extract them: Quality Control Leadership: - Lead and provide technical direction to QC Inspectors. - Develop and implement inspection plans, inspection methods, hold points, and acceptance criteria for shop and field activities. - Review inspection results, NDE reports, non-conformance documentation, work releases, and final release documentation for technical completeness and acceptability. - Ensure inspection activities are performed by properly qualified personnel and maintain inspection independence. - Serve as the primary technical Quality Control contact for customers, customer QA/QC representatives, certifying agencies, Authorized Inspectors, and third-party inspectors. - Provide technical input for Project Specific Quality Plans and Inspection and Test Plans. - Coordinate outside NDE and third-party inspection services. - Lead technical investigations and disposition of non-conformances, including root-cause determinations and corrective actions. - Identify recurring quality issues and trends and communicate findings to Operations and Senior Management. - Participate in internal audits, management reviews, supplier evaluations, and customer quality investigations. Welding & Inspection Program: - Provide technical oversight of the Company's welding quality program. - Review and maintain technical compliance of Welding Procedure Specifications (WPS), Procedure Qualification Records (PQR), and Welder Performance Qualifications (WPQ). - Oversee or witness PQR testing and welder qualification testing as appropriate. - Ensure welder qualification and continuity requirements are met. - Oversee visual welding inspection and applicable NDE activities, including MT, PT, UT, and other methods. - Ensure material identification, traceability, and Material Test Report (MTR) review requirements are satisfied. - Oversee inspection activities involving dimensional verification, bolting, coatings, hydrostatic testing, heat forming, hardness testing, and other applicable fabrication processes. ASME & Code Compliance: - Serve in the technical Quality Control role designated by the Company's ASME Quality Control Manual. - Administer the technical implementation of the ASME Quality Control system for applicable shop and field activities. - Ensure compliance with applicable ASME Code, NBIC, jurisdictional, and Authorized Inspector requirements. - Develop, review, and approve the technical content of the ASME Quality Control Manual and revisions. - Review applicable code changes and determine required updates to Company procedures and inspection practices. - Coordinate technical access, reviews, inspections, and audits with Authorized Inspectors. - Review and approve applicable MTRs, receiving inspections, inspection travelers, hold points, examinations, and testing. - Ensure WPS, PQR, and WPQ documentation complies with applicable ASME Section IX requirements. - Oversee technical requirements associated with R-Stamp, U-Stamp, S-Stamp, and PP-Stamp activities, as applicable. - Prepare, review, and/or certify Manufacturer's Data Reports when authorized and required. - Ensure ASME job files and code-required documentation are complete and ready for final records retention. Quality Systems & Documentation: - Partner with the Compliance & Quality Systems Administrator to ensure the technical requirements of the Company's Quality Management System are properly implemented and maintained. - Ensure technical quality records are complete, accurate, legible, and traceable. - Support document control and records control requirements within QA/QC processes. - Establish technical calibration and measuring-equipment requirements. - Review out-of-tolerance conditions that may affect product acceptance. - Determine technical qualification and competency requirements for QC personnel. - Provide, coordinate, or approve technical training for QC Inspectors and other personnel as appropriate. - Ensure annual visual acuity testing is completed for applicable inspection personnel. - Oversee the collection, technical review, and completion of Work Release documentation. Now Requirements/Qualifications: Required Qualifications bullet list: - High School diploma or equivalent required; technical or engineering degree preferred. - 5 or more years of progressively responsible experience in quality control, welding inspection, steel fabrication, or related industrial work. - Demonstrated experience providing technical direction, leadership, or supervision to inspectors or other quality personnel. - Significant welding and steel fabrication experience. - Strong working knowledge of Quality Control systems applicable to structural steel, welding, fabrication, and code work. - Experience reading layouts, prints, schematics, and engineering drawings. - Current AWS Certified Welding Inspector (CWI) certification required. - Current or previous NDE Level II qualifications in applicable methods such as MT, PT, VT, and UT. - Ability to read and interpret applicable codes, standards, and specifications, including ASME, AISC, and AWS. - Strong communication, leadership, coaching, and conflict resolution skills. - Ability to make independent technical quality decisions within established authority. - Strong organizational skills and attention to detail. - Proficiency with Microsoft Office Suite and applicable quality, fabrication, and electronic reporting systems. Preferred Qualifications: - Technical or engineering degree. - Experience with boilers, pressure vessels, piping, or ASME-code fabrication and repair. - Structural bolting inspection training or certification. We could combine Required and Preferred under a Requirements section, maybe separate subheadings? But we only have h3 for sections; we could have

  Requirements

  and then separate

  for required and preferred? Or we could have

  Required Qualifications

  and

  Preferred Qualifications

  but those are not in the allowed list; but the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those exact headings. It might be okay to also use other headings like "Required Qualifications" but safer to stick to the given list. So we need to map content to those headings. We have About the role (intro). Responsibilities (duties). Requirements (maybe combine required and preferred). Qualifications (maybe we could split required vs preferred? But we have both Requirements and Qualifications as separate headings; we could put required under Requirements and preferred under Qualifications. Skills could be separate but we might not have a distinct skills section; we could put skills under Qualifications or Requirements. Benefits: we have "Why Join Hohl Industrial Services?" which is basically benefits/value proposition. So we can put that under Benefits. Pay and Schedule: not present, so we omit those sections. Thus structure:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ... required qualifications ...

  Qualifications

  ... preferred qualifications ...

  Benefits

  ... why join ...

  We might also include Physical & Work Environment? Not in allowed headings; but could be part of Benefits? Probably not. The instruction says include a section only when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Physical & Work Environment is substantive; but we don't have a heading for it in allowed list. Could we add a custom heading? The examples are not exclusive but they said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect us to use those headings only. So we should not create a Physical & Work Environment section. We could incorporate that info into Benefits or About the role? But it's about physical demands; maybe we could put it under Benefits? Not ideal but maybe acceptable. However the instruction says "Prefer a few substantive sections over many thin ones." So we could omit Physical & Work Environment if not fitting. But we might lose substantive info. However we could incorporate it into Benefits as a paragraph about work environment. But the Benefits section is about why join; we could add a sentence about work environment there. But that might be mixing. Alternatively, we could create a section "Skills" and put physical work environment there? Not appropriate. Given the instruction to preserve ALL substantive information, we need to include physical work environment somewhere. Perhaps we can add a

  Skills

  and include physical demands as a skill? Not great. Better to