Quality Control Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. The posting includes: - Intro about Ameresco (company description). That could be "About the role"? Actually "About the role" would be description of the job. The intro about company could be considered "About the role"? Usually "About the role" includes overview of position. The posting says: "We are seeking an experienced Construction Quality Control Manager (QCM) to oversee quality programs on USACE, NAVFAC, or GSA federal projects. This position will initially be based at Marine Corp Air Station (MCAS) Cherry Point in Havlock, NC." That's about the role. Thus we can have

About the role

with paragraph(s) containing that description. Then "Job Responsibilities:" list bullet points. Thus

Responsibilities

with

• each bullet. Then "Minimum Qualifications:" list bullet points (though they are sentences). Could be under Requirements or Qualifications. The instruction: sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each piece. Minimum Qualifications likely go under Requirements or Qualifications. Additional Qualifications maybe under Qualifications or Skills. They mention "Strong knowledge of UFGS specifications..." etc. Also "Must be proficient with USACE RMS..." etc. Also "Must type at greater than 60 WPM." etc. Also "Strong communication, documentation, and leadership skills." That's skills. Thus we can have: - Requirements: Minimum Qualifications (5 years experience, 2 years QCM on USACE/NAVFAC, demonstrated experience implementing three-phase QC plan, valid USACE/NAVFAC CQ/CM certificate). - Qualifications: Additional Qualifications (knowledge of UFGS specs, proficiency with reporting software, MS Office, BlueBeam, typing speed, etc.) Might also include skills. - Skills: Strong communication, documentation, leadership skills. But we need to avoid duplication. Could combine Additional Qualifications and Skills into Qualifications or Skills. Let's think. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But they have distinct headings allowed. We could have Requirements (minimum qualifications) and Qualifications (additional qualifications + skills). Or we could have Requirements (minimum qualifications) and Skills (communication etc). Additional qualifications could be under Qualifications. Thus we will have sections: - About the role - Responsibilities - Requirements - Qualifications - Skills We will not include Benefits, Pay, Schedule because not specified. Now we need to preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, fraud warnings, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to remove lines like: "Ameresco challenges the brightest..." that's maybe fluff but still substantive? It's about environment fostering initiative. Might be considered boilerplate? It's not a specific job duty. It's generic company statement. Might be considered fluff but not explicitly prohibited. However we should preserve all substantive information; that statement is not about the job specifics but about company culture. Could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That statement is not those categories. It's more like a generic company culture statement. Might be okay to keep but could be considered filler. However they said "Prefer a few substantive sections over many thin ones." Might be better to omit that fluff. But we need to be careful not to omit substantive info. The statement about challenging brightest individuals is not a requirement or responsibility. It's more marketing. I'd lean to omit it as not substantive to the role. Similarly "We are proud of our comprehensive and competitive employee benefits..." is benefits but not specific; we cannot create Benefits section because not specific. So we can omit that line. Also "All official communications from Ameresco will originate from an @ameresco.com email address..." is fraud warning, remove. "For further inquiries or concerns, please contact us at 1-866-AMERESCO" is contact info, maybe considered application instruction? It's not exactly application instruction but contact for inquiries. Might be considered boilerplate; safer to remove. "Ameresco is an Equal Opportunity Employer." Remove EEO. Thus we keep only: - Company intro? Might be considered "About the role"? Actually the first paragraph about Ameresco is company overview, not role. Could be omitted as not specific to role. But we need some description of the role. The role description is in the sentence: "We are seeking an experienced Construction Quality Control Manager (QCM) to oversee quality programs on U.S. Army Corps of Engineers (USACE), Naval Facilities Engineering Command (NAVFAC), or General Services Administration (GSA) federal projects. This position will initially be based at Marine Corp Air Station (MCAS) Cherry Point in Havlock, NC." Thus we can put that as About the role. Now responsibilities list: - Develop and manage the project Quality Control (QC) Plan per contract requirements. - Execute the Three-Phases of Quality Control. - Perform daily quality inspections and coordinate required testing. - Coordinate with Superintendents, SSHOs, and subcontractors on new Definable Features of Work (DFOW). - Review and manage submittals, RFIs, and quality documentation - Track and resolve deficiencies through corrective actions and follow-up inspections. - Maintain daily reports, inspection logs, and quality records. - Other duties as assigned. We need to preserve all; keep "Other duties as assigned." Now Minimum Qualifications: - Minimum of five (5) years of professional commercial or industrial construction experience. - At least two (2) of those years must include serving as a QCM on USACE or NAVFAC construction projects. - Demonstrated experience implementing a three-phase Quality Control (QC) plan. - Valid USACE/NAVFAC CQ/CM certificate at time of hire is required. Now Additional Qualifications: - Strong knowledge of UFGS specifications, quality control plans, and federal construction requirements - Must be proficient with USACE RMS, NAVFAC QCS, or similar reporting software. - Must be proficient in Microsoft Office (Outlook, Excel, Word, Teams) and able to use independently. - Must use BlueBeam Revu or similar and know how to manipulate PDF documents and drawings. - Must type at greater than 60 WPM. - Strong communication, documentation, and leadership skills. We could split: Additional Qualifications (first five bullets) and Skills (last bullet). Or combine. Let's make: - Requirements: Minimum Qualifications. - Qualifications: Additional Qualifications (knowledge, software proficiency, MS Office, BlueBeam, typing speed). - Skills: Strong communication, documentation, and leadership skills. Now we need to output HTML fragment with

  headings and

  for prose,

  • for lists. We need to avoid repeating job title as heading. Not using. We need to not include any empty sections. Thus final HTML:

    About the role

    We are seeking an experienced Construction Quality Control Manager (QCM) to oversee quality programs on U.S. Army Corps of Engineers (USACE), Naval Facilities Engineering Command (NAVFAC), or General Services Administration (GSA) federal projects. This position will initially be based at Marine Corp Air Station (MCAS) Cherry Point in Havlock, NC.

    Responsibilities

    • Develop and manage the project Quality Control (QC) Plan per contract requirements.
    • Execute the Three-Phases of Quality Control.
    • Perform daily quality inspections and coordinate required testing.
    • Coordinate with Superintendents, SSHOs, and subcontractors on new Definable Features of Work (DFOW).
    • Review and manage submittals, RFIs, and quality documentation
    • Track and resolve deficiencies through corrective actions and follow-up inspections.
    • Maintain daily reports, inspection logs, and quality records.
    • Other duties as assigned.

    Requirements

    • Minimum of five (5) years of professional commercial or industrial construction experience.
    • At least two (2) of those years must include serving as a QCM on USACE or NAVFAC construction projects.
    • Demonstrated experience implementing a three-phase Quality Control (QC) plan.
    • Valid USACE/NAVFAC CQ/CM certificate at time of hire is required.

    Qualifications

    • Strong knowledge of UFGS specifications, quality control plans, and federal construction requirements
    • Must be proficient with USACE RMS, NAVFAC QCS, or similar reporting software.
    • Must be proficient in Microsoft Office (Outlook, Excel, Word, Teams) and able to use independently.
    • Must use BlueBeam Revu or similar and know how to manipulate PDF documents and drawings.
    • Must type at greater than 60 WPM.

    Skills

    Strong communication, documentation, and leadership skills.

    Check for any leftover boilerplate: we removed all. Now ensure we didn't miss any substantive info: The line "Ameresco provides design-build, general construction services, and energy savings projects nationwide for government and military facilities." That's company info, not role-specific; could be omitted. The line "Since 2000, we have served as a trusted partner..." also company overview. Could be omitted. The instruction says preserve ALL substantive information; but is that substantive to the job? It's about the company, not the role. Might be considered not required. However they said "Preserve ALL substantive information; do NOT invent or summarize away detail." That could be interpreted as we must keep all info from the posting, except boilerplate etc. The company overview might be considered substantive? It's not boilerplate like legal/EEO. It's about the company. Might be considered relevant to the role context. However the instruction also says "Prefer a few substantive sections over many thin ones." Including a long company overview might create a thin section if we put it as About the role? But we already have About the role with role-specific description. Adding company overview would make About the role longer but still okay. We could include a brief paragraph about Ameresco in About the role before the role-specific description. That would preserve that info. Let's do that. Thus About the role paragraph could combine both: "Ameresco, Inc. (NYSE: AMRC) is a leading energy infrastructure company delivering integrated solutions that provide reliable power and modernize infrastructure. Since 2000, we have served as a trusted partner to public and private sector customers across North America, the UK and Europe, delivering over $15 billion in solutions and contracting more than 5 GW of energy resources. At Ameresco, we integrate energy resources and modernize the built environment through innovative infrastructure solutions that improve reliability, optimize performance, strengthen resilience, and support long-term sustainability. Join us in building the infrastructure that powers the future. Explore opportunities to make a meaningful impact while growing your career with a company at the forefront of energy innovation. Ameresco provides design-build, general construction services, and energy savings projects nationwide for government and military facilities. We are seeking an experienced Construction Quality Control Manager (QCM) to oversee quality programs on U.S. Army Corps of Engineers (USACE), Naval Facilities Engineering Command (NAVFAC), or General Services Administration (GSA) federal projects. This position will initially