Jobs · Quality Assurance · Missouri

QA/QC Manager - Michels Infrastructure Solutions, Inc.

Michels Corporation · St Louis, MO · 1 mo ago
On-siteQuality AssuranceFull-time
We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: Overview (position overview), Key Responsibilities, What You'll Do (maybe duplicate), Why Michels Infrastructure Solutions, Inc.? (benefits and culture), Why You? (maybe personal traits), What It Takes (qualifications). Also location, employment type, travel. We need to not repeat job title as heading. We should not include Job ID etc. We need to strip boilerplate like EEO etc. We need to preserve all substantive information. We'll create sections: About the role (maybe from Position Overview), Responsibilities (Key Responsibilities + What You'll Do), Requirements (What It Takes), Qualifications (maybe same as Requirements? Could combine). But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits. Possibly Skills? The posting includes skills in What It Takes. Could embed in Requirements. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not include Pay or Schedule unless stated. Not present. Travel is mentioned in location line: Travel: Approximately 75% Travel Required. That's a detail; we could include in About the role paragraph or maybe as a note. Not a separate section. We need to remove cookie/navigation/legal/EEO etc. At end there is AA/EOE/M/W/Vet/Disability and link. Remove. We need to preserve all substantive info: location, employment type, travel, overview, responsibilities, why Michels, why you, what it takes. Let's extract: Location: Project-Based Employment Type: Full-Time Travel: Approximately 75% Travel Required Position Overview paragraph: "As a QA/QC Manager, you will lead quality assurance and quality control activities across large-scale hyperscale data center and mission-critical infrastructure projects. You will be responsible for developing, implementing, and maintaining project-specific quality programs while ensuring all work complies with contract requirements, technical specifications, codes, standards, and customer expectations.This role works closely with project management, field operations, engineering, procurement, commissioning, subcontractors, vendors, and customers to establish a culture of quality throughout the project lifecycle. You will oversee inspections, testing programs, documentation requirements, corrective actions, and turnover processes to ensure successful project delivery.Success requires strong technical expertise, leadership capabilities, attention to detail, organizational skills, and a proactive approach to identifying and resolving quality concerns." Key Responsibilities bullet list (we need to convert to

    • ): - Develop, implement, and maintain project quality assurance and quality control programs. - Ensure construction activities comply with project specifications, contract requirements, quality standards, and customer expectations. - Oversee inspection and testing activities across civil, utility, structural, electrical, telecommunications, and mission-critical construction scopes. - Manage quality documentation, inspection reports, testing records, punch lists, non-conformance reports, and corrective action programs. - Coordinate quality activities with project teams, commissioning personnel, subcontractors, vendors, and customers. - Drive continuous improvement initiatives that strengthen quality performance and project execution. What You'll Do list (similar but more detailed). Might be redundant; we can combine or keep as part of Responsibilities. To avoid duplication, we could merge them into one Responsibilities section, but we must preserve all info. Could combine both lists into one
        with all items (some may be similar). Let's list What You'll Do items: - Lead QA/QC efforts supporting hyperscale data center and mission-critical infrastructure projects. - Review construction drawings, specifications, contracts, quality plans, inspection requirements, and testing procedures. - Develop and maintain inspection and test plans (ITPs), quality management plans, and project quality procedures. - Conduct site inspections, audits, field observations, and quality assessments throughout construction activities. - Verify compliance with project requirements related to grading, earthwork, utilities, concrete, power infrastructure, fiber systems, and commissioning activities. - Manage non-conformance reporting, root cause analysis, corrective action plans, and issue resolution processes. - Coordinate with project teams to ensure quality requirements are integrated into project execution plans. - Track and maintain project quality metrics, inspection logs, turnover documentation, and commissioning records. - Support owner inspections, customer audits, commissioning activities, and final turnover requirements. - Provide quality training, mentoring, and guidance to project personnel and subcontractors. We can combine both lists, removing duplicates. Many overlap: first list items similar to some of these. We'll just include the more detailed list (What You'll Do) as responsibilities, and maybe keep the first list as part of overview? But we need to preserve all substantive info; we can include both but avoid duplication by merging. Let's create a Responsibilities section with
          containing all unique items from both lists. Now Requirements/Qualifications: What It Takes paragraph plus bullet list of requirements. What It Takes paragraph: "Bachelor's degree in Construction Management, Engineering, Quality Management, Civil Engineering, or a related discipline and 7+ years of quality assurance, quality control, construction management, engineering, commissioning, or related experience, or an equivalent combination of education and experience.Experience supporting large-scale mission-critical, hyperscale data center, EPC, industrial, power, utility, heavy civil, or infrastructure construction projects.Strong understanding of quality management systems, inspection processes, testing procedures, commissioning requirements, and turnover practices.Experience developing and implementing project quality plans, inspection programs, audit programs, and corrective action processes.Experience evaluating civil, utility, structural concrete, telecommunications, fiber, power infrastructure, and mission-critical construction activities.Ability to read and interpret construction drawings, technical specifications, contracts, quality standards, and inspection requirements.Experience managing non-conformance reports (NCRs), punch lists, root cause analysis, and corrective action programs.Experience supporting commissioning activities, turnover packages, as-built documentation, and owner acceptance processes.Proficiency with Microsoft Office Suite and experience with Procore, Autodesk Construction Cloud, Bluebeam, BIM 360, SharePoint, Aconex, or similar construction management platforms is preferred.Strong leadership, communication, organizational, analytical, and problem-solving skills.Ability to effectively collaborate with project teams, field personnel, customers, subcontractors, vendors, and commissioning teams.Quality certifications such as CQM, CQM-C, ASQ, ISO Auditor, or related credentials are preferred but not required.Valid driver's license with an acceptable driving record.Ability to travel approximately 75% and support long-term onsite project assignments throughout North America as required. Travel may include extended durations based on project assignments and business needs." We can turn that into a
            list of requirements. Benefits section: "Comprehensive Benefits Package" list: Health Insurance, Dental Insurance, Life Insurance, Flexible Spending Accounts (FSA), Health Savings Account (HSA), Short-Term Disability Insurance, Long-Term Disability Insurance, 401(k) Retirement Plan, Legal Plan, Identity Theft Protection and Monitoring Plan. Also note "Benefits may vary based on position and location." We'll include that as a note. Why Michels Infrastructure Solutions, Inc.? includes bullet points: "We deliver some of North America's largest and most complex hyperscale data center and mission-critical infrastructure projects.We leverage a unique Super GC delivery model that combines specialty construction capabilities under a single-source execution approach.We provide exposure to every phase of project delivery, from planning and procurement through commissioning and turnover.We are family owned and operated.We invest an average of $5,000 per employee per year in training and career development.We perform challenging, meaningful work that supports cloud computing, artificial intelligence, digital connectivity, and economic growth.We believe everyone is responsible for promoting safety, regardless of job title.We are part of the Michels Family of Companies, one of North America's largest and most diversified energy and infrastructure contractors.We offer opportunities for long-term growth in quality, commissioning, project management, operations, and leadership." We could treat that as part of About the role or a separate section like "Why Michels". But headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Why Michels". However we could incorporate that content into About the role or Benefits? It's more about company culture. Could be part of About the role. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings? It says use

            for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map content to those headings. About the role: overview + maybe why Michels? Responsibilities: duties. Requirements: qualifications. Qualifications: maybe certifications? Skills: maybe skills. Benefits: benefits. Pay and Schedule only if present. We need to avoid thin sections. So we could combine Qualifications and Skills into Requirements? But we need to decide. Let's assign: - About the role: includes location, employment type, travel, position overview, why Michels (company info), maybe why you? Actually why you is personal traits; could be part of About the role or Skills. - Responsibilities: the detailed list. - Requirements: education, experience, core requirements. - Qualifications: maybe certifications, preferred platforms, driver's license, travel ability. - Skills: leadership, communication, etc. - Benefits: benefits list. We must ensure each heading has real specific content. Let's extract content for each. About the role: - Location: Project-Based Employment Type: Full-Time Travel: Approximately 75% Travel Required - Position Overview paragraph (first two sentences maybe). - Why Michels Infrastructure Solutions, Inc.? bullet points. - Why You? bullet points (personal traits) maybe also here. We'll combine. Responsibilities: the combined list. Requirements: education + years experience + experience supporting large-scale mission-critical etc + strong understanding of QMS etc + experience developing and implementing project quality plans etc + experience evaluating civil, utility, structural concrete, telecommunications, fiber, power infrastructure, mission-critical construction activities + ability to read and interpret drawings etc. Qualifications: experience managing NCRs etc + experience supporting commissioning activities etc + proficiency with MS Office and experience with specific platforms preferred + quality certifications preferred but not required + valid driver's license + ability to travel approx 75% (though travel already in About the role, but we can keep). Skills: strong leadership, communication, organizational, analytical, problem-solving skills + ability to collaborate effectively. Benefits: list. Now we need to output HTML fragment only. We'll wrap each section in

            Heading

            then either

            for prose or

            • for lists. We need to avoid repeating job title. Let's craft. First, About the role:

              Location: Project-Based | Employment Type: Full-Time | Travel: Approximately 75% Travel Required

              As a QA/QC Manager, you will lead quality assurance and quality control activities across large-scale hyperscale data center and mission-critical infrastructure projects. You will be responsible for developing, implementing, and maintaining project-specific quality programs while ensuring all work complies with contract requirements, technical specifications, codes, standards, and customer expectations. This role works closely with project management, field operations, engineering, procurement, commissioning, subcontractors, vendors, and customers to establish a culture of quality throughout the project lifecycle. You will oversee inspections, testing programs, documentation requirements, corrective actions, and turnover processes to ensure successful project delivery. Success requires strong technical expertise, leadership capabilities, attention to detail, organizational skills, and a proactive

Similar jobs