QA/QC Program Engineer - Data Center
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes responsibilities, essential skills (maybe "Essential Skills" and "Additional Skills & Qualifications" combine as Skills?), also "Work Environment", "Job Type & Location", "Pay And Benefits", "Workplace Type", "Application Deadline". We need to map to headings: About the role (maybe description), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no explicit schedule info besides maybe "Workplace Type" and "Work Environment" but schedule not given. So we should not create Schedule heading unless there is schedule content. There's no schedule details like shift, hours. So omit Schedule.
We need to include Pay and Benefits sections if present. Pay: yes, pay range $95-102/hr. Benefits: list of benefits. So include Pay and Benefits sections.
We need About the role: we have job description paragraph at start: "The QA/QC Program Engineer V leads quality assurance and quality control programs for complex data center and mission-critical construction projects..." That's about the role. So we can put that in About the role
with
. Responsibilities: list of responsibilities bullet points. Use
- .
Requirements: maybe "Essential Skills" could be considered Requirements? But we also have "Additional Skills & Qualifications". Could combine into Skills section. However we have separate headings for Requirements, Qualifications, Skills. We need to decide what content goes where. The posting includes "Essential Skills" (list of experience requirements) and "Additional Skills & Qualifications" (list of abilities). Also "Job Type & Location" (Contract position based out of Montgomery, AL). Also "Work Environment". Also "Workplace Type". Also "Application Deadline". Also "About Actalent" and EEO etc which we should remove (boilerplate). Also "Job Title" line we should not repeat as heading.
We need to preserve all substantive information, but we can drop boilerplate like EEO, legal, etc. Also drop navigation, cookie, etc. Also drop "Application Deadline"? The instruction says remove application instructions. Application deadline might be considered application instruction? It's not exactly instruction to apply, but it's a deadline. Might be considered metadata; but we could keep as a short paragraph maybe under About the role? However instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Application deadline is minor metadata; we could fold into a short
maybe under About the role or at end. But we also have "Job Type & Location" which is also metadata; could be folded. We need to avoid creating sections with filler. So we likely will have sections: About the role, Responsibilities, Skills (combining essential and additional), Pay, Benefits. Possibly also "Work Environment" but not a standard heading; we could incorporate into About the role or maybe as a separate section? The allowed headings list does not include Work Environment, so we should not create a heading for it; we can fold its content into About the role or maybe into a
under About the role. Similarly "Job Type & Location" could be folded into About the role or a short
. "Application Deadline" also fold. We must not invent sections like Requirements or Qualifications if no specific content. We have "Essential Skills" which could be considered Requirements (experience). But we also have Skills section for abilities. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Essential Skills and Additional Skills & Qualifications into a single Skills section. That would cover both experience requirements and abilities. Then we don't need separate Requirements or Qualifications headings. Thus sections: About the role, Responsibilities, Skills, Pay, Benefits. Check if any content for Qualifications separate? Not needed. Now we need to output HTML fragment: use
for each heading, then content. For About the role: include the description paragraph(s) plus maybe job type location, work environment, application deadline as a short paragraph. We need to preserve all substantive information: so we must include details like: leads QA/QC programs, develops and monitors quality metrics, drives continuous improvement, ensures MECP systems meet standards, serves as interface, provides training, coordinates issues, audits, reviews submittals, performs quality engineering reviews, develops documentation, recommends corrective actions, reviews commissioning scripts, assists construction manager, drives closure of open issues, attends factory witness tests, conducts onsite visual inspections, assists confirming testing documentation, support reviewing labeling, assist developing dashboards, participate in meetings. Also include: Essential Skills list (at least 5 years experience, proven experience design-build, hands-on experience across civil and structural, demonstrated experience leading QA/QC and commissioning programs, experience managing contractors, experience with mission-critical power and cooling, background in construction management, experience in project management). Also Additional Skills & Qualifications list (strong analytical skills, ability to develop procedures, effective communication, capability to deliver training, attention to detail, organizational skills, comfort with dashboards, ability to participate in meetings). Also include Job Type & Location: Contract position based out of Montgomery, AL. Work Environment: description about large-scale data center, cross-functional teams, onsite inspections, etc. Application Deadline: anticipated to close on Oct 2, 2026. Pay: $95.00 - $102.00/hr. Benefits: list. We must not include boilerplate about Actalent, EEO, etc. Now craft HTML. Structure:
About the role
... (description paragraph) ...
Job type & location: Contract position based out of Montgomery, AL.
Work environment: ...
Application deadline: Anticipated to close on Oct 2, 2026.
But we need to avoid using ? Not prohibited; but we can just include as plain text. However we should keep it as prose. Could embed as sentences. Better: combine into a paragraph: "This is a Contract position based out of Montgomery, AL. The role operates within large-scale data center and mission-critical construction environments ... The position is anticipated to close on Oct 2, 2026." That preserves info. Now Responsibilities:Responsibilities
- ... each responsibility as a line from the list.
- under Skills.
Pay:
Pay
The pay range for this position is $95.00 - $102.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
We could keep the extra sentence about eligibility etc? That's part of Benefits section maybe. But we have separate Benefits. Benefits:Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available