Quality Control Manager

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. We need to parse the job description. Key parts: - Opening: "Ryan Companies US, Inc. has an immediate career opportunity for a Quality Control Manager to join our national Mission Critical sector team! Do you bring at last 5 years of successful field quality management experience in mission critical construction or large construction projects? Do you enjoy working in a fast, fun, inclusive and collaborative work space? Do you want the next chapter of your career to be with an industry leader in commercial real estate who brings a fully integrated and creative design-build approach? If this describes you, we encourage you to apply today." That's about the role / overview. Could be "About the role". - Then: "To be successful in this role, a technical degree in construction, civil, architecture, engineering, or equivalent is required. You must have at least 5 years of experiences in design, construction, and/or commissioning for large & complex MEP-heavy projects. Previous experience leading construction documentation and contract administration is required." That's Requirements/Qualifications. - Then: "Some Things You Can Expect To Expect To Do:" followed by a long list of duties. That's Responsibilities. - Then: "You Will Really Stand Out If You Have: Knowledge of one or more quality systems (i.e., Malcolm Baldridge, ISO 9000, Lean, Kaizen, Army Corps of Engineers, etc. Experience using Procore, Bluebeam, and Revit" That's Skills (or Qualifications). Could be "Skills". - Then: "Benefits:" list: Competitive Salary, Medical, Dental and Vision Benefits, Retirement and Savings Benefits, Flexible Spending Accounts, Life Insurance, Educational Assistance, Paid Time Off (PTO), Parenting Benefits, Long-term Disability, Ryan Foundation – charitable matching funds, Paid Time for Volunteer Events. Later there is another Benefits block with more details: "Benefits: Competitive SalaryMedical, Dental and Vision BenefitsRetirement and Savings BenefitsFlexible Spending and Health Savings AccountsLife InsuranceShort-Term and Long-Term DisabilityEducational AssistancePaid Time Off (PTO)Employee Assistance and Wellness ProgramsFamily Planning & Parenting BenefitsEmployee Discount ProgramsPet insuranceCharitable Donation MatchingVolunteer Time Off (VTO)Employee Resource Groups (ERGs)". This duplicates but adds more items. We need to preserve all substantive info, not duplicate lines. We should combine unique items. We need to avoid duplication. So we should list benefits without repeating same items. Let's compile unique benefits: From first block: - Competitive Salary - Medical, Dental and Vision Benefits - Retirement and Savings Benefits - Flexible Spending Accounts - Life Insurance - Educational Assistance - Paid Time Off (PTO) - Parenting Benefits - Long-term Disability - Ryan Foundation – charitable matching funds - Paid Time for Volunteer Events From second block: - Competitive Salary (duplicate) - Medical, Dental and Vision Benefits (duplicate) - Retirement and Savings Benefits (duplicate) - Flexible Spending and Health Savings Accounts (note: first had Flexible Spending Accounts; second adds Health Savings Accounts; we can combine as Flexible Spending and Health Savings Accounts) - Life Insurance (duplicate) - Short-Term and Long-Term Disability (first had Long-term Disability only; second adds Short-Term and Long-Term Disability) - Educational Assistance (duplicate) - Paid Time Off (PTO) (duplicate) - Employee Assistance and Wellness Programs - Family Planning & Parenting Benefits (similar to Parenting Benefits but more specific) - Employee Discount Programs - Pet insurance - Charitable Donation Matching (similar to Ryan Foundation – charitable matching funds) - Volunteer Time Off (VTO) (similar to Paid Time for Volunteer Events) - Employee Resource Groups (ERGs) We need to preserve all substantive info, not invent. So we should list each distinct benefit. Avoid duplication but include nuance. Let's create a combined list: - Competitive Salary - Medical, Dental and Vision Benefits - Retirement and Savings Benefits - Flexible Spending Accounts - Health Savings Accounts (if we separate) but second says "Flexible Spending and Health Savings Accounts". Could combine as "Flexible Spending and Health Savings Accounts". Safer to list as "Flexible Spending and Health Savings Accounts". - Life Insurance - Short-Term Disability - Long-Term Disability - Educational Assistance - Paid Time Off (PTO) - Employee Assistance and Wellness Programs - Family Planning & Parenting Benefits - Employee Discount Programs - Pet insurance - Charitable Donation Matching - Volunteer Time Off (VTO) - Employee Resource Groups (ERGs) - Ryan Foundation – charitable matching funds (maybe same as Charitable Donation Matching; but we have both; we can keep both if they are distinct? The first says "Ryan Foundation – charitable matching funds". Second says "Charitable Donation Matching". Likely same. To avoid duplication, we can keep one: "Charitable Donation Matching (Ryan Foundation)". But we must not invent; we can note both but it's duplication. Safer to include "Charitable Donation Matching" and maybe note Ryan Foundation? Might be considered duplication. I'd include "Charitable Donation Matching" as it's explicit. The Ryan Foundation mention is part of first block; we could keep "Ryan Foundation – charitable matching funds". But that is essentially same. To avoid duplication, we could combine: "Charitable Donation Matching (Ryan Foundation)". That preserves both mentions without duplication. Good. - Paid Time for Volunteer Events (first) and Volunteer Time Off (VTO) (second). Could combine: "Paid Time for Volunteer Events / Volunteer Time Off (VTO)". Keep both. Thus benefits list. Now Pay and Schedule sections: The posting does not mention specific pay or schedule details. So we should NOT include Pay or Schedule sections because they are not stated. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have, so include Benefits. Pay and Schedule not present, so omit. Now sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. We need to decide what goes where. The posting includes: - Overview / About the role: first paragraph. - Requirements: technical degree, 5 years experience, leading construction documentation and contract administration. - Qualifications: maybe same as requirements? Could combine. But we have separate sections for Requirements and Qualifications. We could put degree and experience under Requirements, and maybe "previous experience leading construction documentation and contract administration" under Qualifications. Or we could treat all as Requirements. But we need to follow instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have to use headings only when there is real specific content. We could have Requirements (includes degree, experience, etc.) and Qualifications (maybe same). To avoid thin sections, we could merge them into a single "Requirements" section and omit Qualifications. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't require us to use all; we can omit those not needed. So we can have About the role, Responsibilities, Requirements, Skills, Benefits. That's enough. But we also have "You Will Really Stand Out If You Have:" which is skills/preferred qualifications. That could go under Skills. Thus: - About the role: overview paragraph. - Responsibilities: the long list after "Some Things You Can Expect To Do:" (including all bullet-like sentences). We'll put each as

inside

. - Requirements: technical degree, 5 years experience in design, construction, and/or commissioning for large & complex MEP-heavy projects, previous experience leading construction documentation and contract administration is required. Also maybe "at least 5 years of successful field quality management experience in mission critical construction or large construction projects?" That's also in opening but it's part of requirements. We'll include. - Skills: Knowledge of quality systems (list), Experience using Procore, Bluebeam, and Revit. - Benefits: list as above. We must not include duplicated lines. Ensure we capture all substantive info from responsibilities list. Let's extract responsibilities list precisely: "Some Things You Can Expect To Do: Lead the planning, development, and implementation of Ryan’s quality program for data centers. Responsible for managing and performing the daily QC responsibilities of specific projects to ensure the project is constructed in accordance with the established contract documents. Lead and train other project team members on quality-related activities. The Quality manager role includes direct oversight and review of the entire documentation and physical inspection phase of the workflow process and working with other in-house personnel (e.g.: Project Managers, Superintendents, etc.) and external personnel to produce and document a quality product. Review shop drawings and submittals for conformance with project specifications by direct review, and by leveraging the knowledge and experience of others in the project team when necessary. Participate in preparatory meetings to establish an understanding of the standards of care desired for each scope of work. Participate in pre-installation meetings with new and existing subcontractors, project team members, and any other stakeholders, prior to the start of each new phase of the work, to discuss issues that affect quality. Ensure project team members, trade partners, and all stakeholders understand the quality management requirements, for each scope of work. Set quality management expectations, including the quantity and timing of field inspections, testing requirements, and documentation requirements for each scope of work. Verify and document that all materials received for the project are in conformance with the approved submittal, are handled and stored appropriately, and are installed and acceptable for use in the project. Conduct, participate in, or assign quality management tasks to other project team members. Monitor, Track, Log and Audit all quality control activities, including all testing, inspections, and supporting documentation throughout the project. Monitor, Track, and support the project team to verify effective implementation of corrective actions for project non-conformances and quality issues. Conduct Root Cause Analysis to identify, resolve and implement solutions to quality issues Conduct and document weekly QC meetings with the superintendent, and provide and distribute written minutes, as described in project specific contract document. Conduct periodic quality walkthroughs with the client, the design team, and/or any other client quality representative. Conduct and document weekly QC Meetings with the client and provide and distribute meeting minutes. Provide weekly QC reports that reinforce activities that are being constructed in conformance with each specific project’s established standard and constructively confronts any non-conformance to produce the desired outcome in a timely manner. Support the project team with punch list and other phase turnover activities. Stop work if necessary to resolve matters that affect safety, quality and/or inhibit the logical progress of work. Capture and share lessons learned with the project team, trade partners, and other Ryan Mission Critical project teams. Travel as needed if not living local to the project site" We need to preserve all that. We'll put each sentence as
• . Now Requirements: we need to capture: - "To be successful in this role, a technical degree in construction, civil, architecture, engineering, or equivalent is required." - "You must have at least 5 years of experiences in design, construction, and/or commissioning for large & complex MEP-heavy projects." - "Previous experience leading construction documentation and contract administration is required." - Also from opening: "Do you bring at last 5 years of successful field quality management experience in mission critical construction or large construction projects?" That's a requirement too. We'll include. We should not repeat same info; combine. Thus Requirements list: