Code Compliance Building Inspector

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, etc. We need to parse the posting content. Given text: "Perform third party electrical, mechanical, architectural, structural, plumbing, and fire safety building inspections Prepare and submit daily time and Inspection/Field Reports in accordance with ECS Policy Demonstrate extensive knowledge of state and local building code regulations, policies, and procedures This position also involves project management of code compliance projects, including reviewing plans, providing technical support, conducting inspections, monitoring project process for performance and budgetary conditions, proposal preparation, as well as attending project site meetings, and assisting with the resolution of technical and administrative problems In this position you may be expected to mentor and train other building inspectors Responsibilities also include assisting with management of P & L, marketing our services by maintaining and developing client interactions, and participating in marketing and business development functions related to code inspections High School Diploma or GED 5+ years of experience in code compliance inspection of mechanical, electrical, plumbing, and fire protection systems and/or plan review preferred At least one valid ICC certification (B2, M2, P2, E2, Fire Inspector I or Fire Inspector II) is preferred, or the ability to obtain certification within 90 days of hire If driving for, or on behalf of, any ECS subsidiary, a valid driver’s license is required ECS Group of Companies (ECS) was founded in 1988 with the goal to raise the standards of professional engineering consulting. Today, we are a leader in geotechnical, construction materials, environmental and building science + infrastructure consulting services. We are employee-owned with more than 3,00 employees in 100+ offices and testing facilities coast to coast. ECS is currently ranked #60 in Engineering News-Record’s Top 500 Design Firms (April 2026), #148 in Engineering News-Record’s Top 200 Environmental Firms (October 2025) and #38 in Zweig Group’s Hot Firm List (June 2026). For additional information about ECS, visit: www.ecslimited.com. ECS is an Equal Opportunity Employer. To learn more, click here." We need to remove EEO line and maybe the "For additional information about ECS, visit: www.ecslimited.com." That's not boilerplate? It's company info, could be kept as part of About the role? Actually it's about the company. Could be part of About the role or maybe a separate "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include About the role for company overview? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings. We need to decide which sections have content. We have responsibilities: many bullet-like sentences. We can put them under Responsibilities

with

• . We have qualifications: High School Diploma or GED, 5+ years experience, ICC certification preferred, driver's license if driving. Those are qualifications/requirements. Could be under Requirements or Qualifications. We have both headings allowed. We need to decide: maybe Requirements for experience and certification, Qualifications for education? Or combine. But we should not create thin sections. We could have one Requirements section covering education, experience, certification, driver license. Or we could split into Requirements and Qualifications but that may be thin. Better to have one Requirements section with all. Skills: maybe not explicitly listed; we could omit Skills if no specific skill list. Benefits, Pay, Schedule: not mentioned, so omit. About the role: we could include a brief description of the role: performing inspections, preparing reports, knowledge of codes, project management, mentoring, P&L management, marketing. That's essentially responsibilities. But we already have Responsibilities. About the role could be a summary paragraph. However we must not repeat content. We could put a short paragraph summarizing the role (maybe first sentence). But we must preserve ALL substantive information; we cannot omit details. If we put details in Responsibilities, we can still have About the role with a brief overview that doesn't duplicate details? But we risk duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all details somewhere. If we put details in Responsibilities, we can still have About the role with a brief overview that is not a duplicate but maybe a summary; but that would be summarizing away detail? Not exactly; we could keep a short overview that is not repeating details but still includes some info. However we risk losing details if we omit them elsewhere. Safer to not include About the role if we already have Responsibilities covering all details. But we need to include a section only when posting has real specific content for it. The posting does have a description of the role; we could treat that as About the role. But then Responsibilities could be a list of duties. However the posting includes both general role description and specific duties. We could split: About the role: a paragraph summarizing the role (maybe first two sentences). Responsibilities: list of specific duties. That would preserve all info. Let's extract: Role description sentences: - Perform third party electrical, mechanical, architectural, structural, plumbing, and fire safety building inspections - Prepare and submit daily time and Inspection/Field Reports in accordance with ECS Policy - Demonstrate extensive knowledge of state and local building code regulations, policies, and procedures - This position also involves project management of code compliance projects, including reviewing plans, providing technical support, conducting inspections, monitoring project process for performance and budgetary conditions, proposal preparation, as well as attending project site meetings, and assisting with the resolution of technical and administrative problems - In this position you may be expected to mentor and train other building inspectors - Responsibilities also include assisting with management of P & L, marketing our services by maintaining and developing client interactions, and participating in marketing and business development functions related to code inspections These are all duties/responsibilities. So we could put them all under Responsibilities. Then About the role could be a brief overview like "This position involves performing third-party inspections across multiple disciplines, managing code compliance projects, mentoring staff, and supporting business development." But that would be summarizing, potentially losing detail. However we already have all details in Responsibilities, so About the role could be a short generic statement that doesn't omit any detail because details are elsewhere. That's acceptable: we are not removing detail, just providing a summary in addition. The instruction: "do NOT invent or summarize away detail." Summarizing away detail would be if we omitted details and only kept summary. If we keep details elsewhere, summarizing is okay. So we can include About the role with a brief summary. Now Requirements/Qualifications: we have: - High School Diploma or GED - 5+ years of experience in code compliance inspection of mechanical, electrical, plumbing, and fire protection systems and/or plan review preferred - At least one valid ICC certification (B2, M2, P2, E2, Fire Inspector I or Fire Inspector II) is preferred, or the ability to obtain certification within 90 days of hire - If driving for, or on behalf of, any ECS subsidiary, a valid driver’s license is required We could put these under Requirements (or Qualifications). Let's choose Requirements. Now we need to output HTML fragment with

  headings and

  • for lists,

    for prose. We'll have:

    About the role

    This position involves performing third‑party inspections across electrical, mechanical, architectural, structural, plumbing, and fire safety disciplines, preparing daily reports, applying extensive knowledge of state and local building codes, managing code compliance projects, mentoring junior inspectors, and supporting P & L, marketing, and business‑development activities.

    Responsibilities

    • Perform third party electrical, mechanical, architectural, structural, plumbing, and fire safety building inspections
    • Prepare and submit daily time and Inspection/Field Reports in accordance with ECS Policy
    • Demonstrate extensive knowledge of state and local building code regulations, policies, and procedures
    • Manage code compliance projects: review plans, provide technical support, conduct inspections, monitor project performance and budgetary conditions, prepare proposals, attend site meetings, and assist in resolving technical and administrative problems
    • Mentor and train other building inspectors
    • Assist with management of P & L, market services by maintaining and developing client interactions, and participate in marketing and business development functions related to code inspections

    Requirements

    • High School Diploma or GED
    • 5+ years of experience in code compliance inspection of mechanical, electrical, plumbing, and fire protection systems and/or plan review (preferred)
    • At least one valid ICC certification (B2, M2, P2, E2, Fire Inspector I or Fire Inspector II) preferred, or ability to obtain certification within 90 days of hire
    • Valid driver’s license required if driving for or on behalf of any ECS subsidiary
    We should not include Benefits, Pay, Schedule. We must not include any boilerplate like EEO, company ranking details? The company info we omitted; we could include a brief About the role that mentions ECS? But we already have About the role summary; we could incorporate that it's at ECS. However we omitted the company description; that's not required to preserve because it's not about the role? It's about the company; but the instruction says preserve ALL substantive information. Is company description substantive? It might be considered boilerplate but it's specific info about ECS. However it's not required for the job; but it's still part of posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company description is not listed as boilerplate to remove. It might be considered part of the posting but not required? The instruction says preserve ALL substantive information. So we should keep the company description somewhere. Where could we put it? Possibly under About the role or a separate section like "About ECS". But we only allowed headings list; we could add About the role and include company description there. However we must not repeat job title as heading. We can include About the role with both role summary and company info. That would preserve the company details. Thus we need to include the company description: "ECS Group of Companies (ECS) was founded in 1988 with the goal to raise the standards of professional engineering consulting. Today, we are a leader in geotechnical, construction materials, environmental and building science + infrastructure consulting services. We are employee-owned with more than 3,00 employees in 100+ offices and testing facilities coast to coast. ECS is currently ranked #60 in Engineering News-Record’s Top 500 Design Firms (April 2026), #148 in Engineering News-Record’s Top 200 Environmental Firms (October 2025) and #38 in Zweig Group’s Hot Firm List (June 2026). For additional information about ECS, visit: www.ecslimited.com." We should keep that as prose under About the role maybe after the role summary. Thus About the role

    could contain two paragraphs? We can have multiple

    under same heading? Probably we can have multiple

    elements. We'll output:

    About the role