Senior Construction Project Manager
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include. The posting includes:
- About the role: The description paragraph at start: "The Senior Construction Project Manager is responsible for leading the planning, execution, and financial performance of MEP-intensive construction projects, specifically within the data center space. This role oversees electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover, ensuring projects are delivered safely, on schedule, and within budget."
That's a prose description; could be under "About the role".
- Responsibilities: bullet list: "Lead the planning and execution of MEP-intensive construction projects within the data center space.", "Oversee electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover.", "Ensure projects are delivered safely, on schedule, and within budget.", "Engage in contract negotiation and manage construction resources effectively.", "Address and resolve any issues related to construction, RFIs, and site development."
- Essential Skills: list: "Experience in construction management.", "Expertise in mission-critical and data center construction.", "Proficiency in hyperscale construction and contract negotiation.", "Strong understanding of mechanical systems and site development."
- Additional Skills & Qualifications: "Proficiency with Procore.", "Experience using Bluebeam."
- Work Environment: prose: "The work environment involves managing multiple construction projects within data centers, requiring a strong understanding of MEP systems. The role demands familiarity with industry-specific software such as Procore and Bluebeam. The focus is on ensuring safety, timely delivery, and adherence to budget constraints."
- Job Type & Location: "This is a Contract position based out of Saint Louis, MO."
- Pay And Benefits: includes pay range: "$60.00 - $100.00/hr." and benefits list: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). Also note eligibility etc.
- Workplace Type: "This is a fully onsite position in Saint Louis,MO."
- Application Deadline: "This position is anticipated to close on Oct 1, 2026."
- About Actalent: company description.
We need to remove boilerplate: equal opportunity, accommodation, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI, etc. Also remove duplicated lines.
We need to decide sections: About the role, Responsibilities, Skills (maybe combine Essential Skills and Additional Skills & Qualifications into Skills), Benefits, Pay, Schedule? There's no explicit schedule info besides maybe "Workplace Type" (fully onsite) and "Job Type & Location" (Contract). Schedule not given. So we should not create Schedule section unless posting actually states it. It does not. So omit Schedule.
Pay section: we have pay range. Should we create a Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated: "$60.00 - $100.00/hr." So we can include Pay section.
Benefits: benefits are listed, so include Benefits section.
We could also include a section for "Job Type & Location" maybe as "About the role"? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Job Type & Location under About the role or maybe as a short paragraph under About the role. Or we could create a separate section like "Job Type & Location" but not in allowed headings list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive list? 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. If we have content that doesn't fit exactly, we can incorporate into existing sections.
Thus:
- About the role: include the initial description paragraph plus maybe Job Type & Location and Workplace Type and Application Deadline? Those are metadata but could be included as short paragraphs.
- Responsibilities: list.
- Requirements: maybe combine Essential Skills and Additional Skills & Qualifications? Or we could have Requirements for mandatory skills, Qualifications for additional? But we have both Essential Skills and Additional Skills & Qualifications. Could treat Essential Skills as Requirements, Additional Skills & Qualifications as Qualifications. Or combine into Skills. The heading list includes Skills as separate. So we could have:
- Requirements: Essential Skills (maybe "Experience in construction management..." etc.)
- Qualifications: Additional Skills & Qualifications (Procore, Bluebeam)
- Skills: maybe combine both? But we already used Requirements and Qualifications. Could also have Skills for something else like "Strong understanding of mechanical systems and site development." but that's already in Essential Skills.
Better to follow: Requirements = Essential Skills, Qualifications = Additional Skills & Qualifications, Skills = maybe not needed. But we have to avoid thin sections. Could combine Requirements and Qualifications into a single Skills section? But we have both headings allowed. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Perhaps we combine Essential Skills and Additional Skills & Qualifications into one "Skills" section. Then we could have Requirements maybe not needed. But we need to include all substantive info. Let's think.
We have:
- About the role (description)
- Responsibilities (list)
- Skills (combined essential and additional)
- Benefits (list)
- Pay (range)
- Maybe Job Type & Location and Workplace Type and Application Deadline could go under About the role as extra paragraphs.
We should not create Schedule.
Thus sections: About the role, Responsibilities, Skills, Benefits, Pay.
Check if any content missing: Work Environment description is similar to About the role; we can incorporate into About the role.
Now ensure we don't include boilerplate: remove equal opportunity, accommodation, etc.
Now format: Use for each section heading. Inside, use
for prose,
- for lists.
We need to preserve all substantive information: ensure we keep the pay range sentence exactly: "The pay range for this position is $60.00 - $100.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." Also benefits list exactly as given.
We need to include the benefits list exactly: "Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)". The original had line breaks but we can keep as list items.
Also include "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following:" That's prose before list. We should keep that as a
before the
.
Now About the role: combine initial description, work environment, job type & location, workplace type, application deadline maybe.
Let's craft:
The Senior Construction Project Manager is responsible for leading the planning, execution, and financial performance of MEP-intensive construction projects, specifically within the data center space. This role oversees electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover, ensuring projects are delivered safely, on schedule, and within budget.
The work environment involves managing multiple construction projects within data centers, requiring a strong understanding of MEP systems. The role demands familiarity with industry-specific software such as Procore and Bluebeam. The focus is on ensuring safety, timely delivery, and adherence to budget constraints.
This is a Contract position based out of Saint Louis, MO. This is a fully onsite position in Saint Louis, MO. This position is anticipated to close on Oct 1, 2026.
We could combine duplicate location statements.
Now Responsibilities: list each responsibility as - .
Now Skills: combine essential and additional.
Essential Skills list:
- Experience in construction management.
- Expertise in mission-critical and data center construction.
- Proficiency in hyperscale construction and contract negotiation.
- Strong understanding of mechanical systems and site development.
Additional Skills & Qualifications:
- Proficiency with Procore.
- Experience using Bluebeam.
We'll combine into one list.
Now Benefits: include preamble paragraph then list.
Now Pay: include paragraph(s) about pay range and compensation factors.
Now ensure we don't include any boilerplate like "Eligibility requirements apply..." that's part of benefits preamble, we keep that.
Now output only HTML fragment.
Let's craft.
Check for any duplicated lines: we have "This is a Contract position based out of Saint Louis, MO." and "This is a fully onsite position in Saint Louis, MO." Could combine: "This is a Contract, fully onsite position based out of Saint Louis, MO." Keep both? Might be redundant but we can combine to avoid duplication. The rule: remove duplicated lines. So we should combine.
Thus About the role paragraph: combine.
Let's write:
The Senior Construction Project Manager is responsible for leading the planning, execution, and financial performance of MEP-intensive construction projects, specifically within the data center space. This role oversees electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover, ensuring projects are delivered safely, on schedule, and within budget.
The work environment involves managing multiple construction projects within data centers, requiring a strong understanding of MEP systems. The role demands familiarity with industry-specific software such as Procore and Bluebeam. The focus is on ensuring safety, timely delivery, and adherence to budget constraints.
This is a Contract, fully onsite position based out of Saint Louis, MO. This position is anticipated to close on Oct 1, 2026.
Now Responsibilities: list.
Now Skills: list.
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - About the role: The description paragraph at start: "The Senior Construction Project Manager is responsible for leading the planning, execution, and financial performance of MEP-intensive construction projects, specifically within the data center space. This role oversees electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover, ensuring projects are delivered safely, on schedule, and within budget." That's a prose description; could be under "About the role". - Responsibilities: bullet list: "Lead the planning and execution of MEP-intensive construction projects within the data center space.", "Oversee electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover.", "Ensure projects are delivered safely, on schedule, and within budget.", "Engage in contract negotiation and manage construction resources effectively.", "Address and resolve any issues related to construction, RFIs, and site development." - Essential Skills: list: "Experience in construction management.", "Expertise in mission-critical and data center construction.", "Proficiency in hyperscale construction and contract negotiation.", "Strong understanding of mechanical systems and site development." - Additional Skills & Qualifications: "Proficiency with Procore.", "Experience using Bluebeam." - Work Environment: prose: "The work environment involves managing multiple construction projects within data centers, requiring a strong understanding of MEP systems. The role demands familiarity with industry-specific software such as Procore and Bluebeam. The focus is on ensuring safety, timely delivery, and adherence to budget constraints." - Job Type & Location: "This is a Contract position based out of Saint Louis, MO." - Pay And Benefits: includes pay range: "$60.00 - $100.00/hr." and benefits list: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). Also note eligibility etc. - Workplace Type: "This is a fully onsite position in Saint Louis,MO." - Application Deadline: "This position is anticipated to close on Oct 1, 2026." - About Actalent: company description. We need to remove boilerplate: equal opportunity, accommodation, San Francisco Fair Chance, Massachusetts Lie Detector, Use of AI, etc. Also remove duplicated lines. We need to decide sections: About the role, Responsibilities, Skills (maybe combine Essential Skills and Additional Skills & Qualifications into Skills), Benefits, Pay, Schedule? There's no explicit schedule info besides maybe "Workplace Type" (fully onsite) and "Job Type & Location" (Contract). Schedule not given. So we should not create Schedule section unless posting actually states it. It does not. So omit Schedule. Pay section: we have pay range. Should we create a Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. Pay is stated: "$60.00 - $100.00/hr." So we can include Pay section. Benefits: benefits are listed, so include Benefits section. We could also include a section for "Job Type & Location" maybe as "About the role"? But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put Job Type & Location under About the role or maybe as a short paragraph under About the role. Or we could create a separate section like "Job Type & Location" but not in allowed headings list? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive list? 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. If we have content that doesn't fit exactly, we can incorporate into existing sections.
Thus:
- About the role: include the initial description paragraph plus maybe Job Type & Location and Workplace Type and Application Deadline? Those are metadata but could be included as short paragraphs.
- Responsibilities: list.
- Requirements: maybe combine Essential Skills and Additional Skills & Qualifications? Or we could have Requirements for mandatory skills, Qualifications for additional? But we have both Essential Skills and Additional Skills & Qualifications. Could treat Essential Skills as Requirements, Additional Skills & Qualifications as Qualifications. Or combine into Skills. The heading list includes Skills as separate. So we could have:
- Requirements: Essential Skills (maybe "Experience in construction management..." etc.)
- Qualifications: Additional Skills & Qualifications (Procore, Bluebeam)
- Skills: maybe combine both? But we already used Requirements and Qualifications. Could also have Skills for something else like "Strong understanding of mechanical systems and site development." but that's already in Essential Skills.
Better to follow: Requirements = Essential Skills, Qualifications = Additional Skills & Qualifications, Skills = maybe not needed. But we have to avoid thin sections. Could combine Requirements and Qualifications into a single Skills section? But we have both headings allowed. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Perhaps we combine Essential Skills and Additional Skills & Qualifications into one "Skills" section. Then we could have Requirements maybe not needed. But we need to include all substantive info. Let's think.
We have:
- About the role (description)
- Responsibilities (list)
- Skills (combined essential and additional)
- Benefits (list)
- Pay (range)
- Maybe Job Type & Location and Workplace Type and Application Deadline could go under About the role as extra paragraphs.
We should not create Schedule.
Thus sections: About the role, Responsibilities, Skills, Benefits, Pay.
Check if any content missing: Work Environment description is similar to About the role; we can incorporate into About the role.
Now ensure we don't include boilerplate: remove equal opportunity, accommodation, etc.
Now format: Use for each section heading. Inside, use
for each section heading. Inside, use
for prose,
- for lists.
We need to preserve all substantive information: ensure we keep the pay range sentence exactly: "The pay range for this position is $60.00 - $100.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." Also benefits list exactly as given.
We need to include the benefits list exactly: "Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)". The original had line breaks but we can keep as list items.
Also include "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following:" That's prose before list. We should keep that as a
before the
- .
Now About the role: combine initial description, work environment, job type & location, workplace type, application deadline maybe.
Let's craft:
- .
Now Skills: combine essential and additional.
Essential Skills list:
- Experience in construction management.
- Expertise in mission-critical and data center construction.
- Proficiency in hyperscale construction and contract negotiation.
- Strong understanding of mechanical systems and site development.
Additional Skills & Qualifications:
- Proficiency with Procore.
- Experience using Bluebeam.
We'll combine into one list.
Now Benefits: include preamble paragraph then list.
Now Pay: include paragraph(s) about pay range and compensation factors.
Now ensure we don't include any boilerplate like "Eligibility requirements apply..." that's part of benefits preamble, we keep that.
Now output only HTML fragment.
Let's craft.
Check for any duplicated lines: we have "This is a Contract position based out of Saint Louis, MO." and "This is a fully onsite position in Saint Louis, MO." Could combine: "This is a Contract, fully onsite position based out of Saint Louis, MO." Keep both? Might be redundant but we can combine to avoid duplication. The rule: remove duplicated lines. So we should combine.
Thus About the role paragraph: combine.
Let's write:
The Senior Construction Project Manager is responsible for leading the planning, execution, and financial performance of MEP-intensive construction projects, specifically within the data center space. This role oversees electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover, ensuring projects are delivered safely, on schedule, and within budget.
The work environment involves managing multiple construction projects within data centers, requiring a strong understanding of MEP systems. The role demands familiarity with industry-specific software such as Procore and Bluebeam. The focus is on ensuring safety, timely delivery, and adherence to budget constraints.
This is a Contract, fully onsite position based out of Saint Louis, MO. This position is anticipated to close on Oct 1, 2026.
Now Responsibilities: list. Now Skills: list.
The Senior Construction Project Manager is responsible for leading the planning, execution, and financial performance of MEP-intensive construction projects, specifically within the data center space. This role oversees electrical, mechanical, controls, life safety, and low-voltage systems from preconstruction through commissioning and turnover, ensuring projects are delivered safely, on schedule, and within budget.
The work environment involves managing multiple construction projects within data centers, requiring a strong understanding of MEP systems. The role demands familiarity with industry-specific software such as Procore and Bluebeam. The focus is on ensuring safety, timely delivery, and adherence to budget constraints.
This is a Contract position based out of Saint Louis, MO. This is a fully onsite position in Saint Louis, MO. This position is anticipated to close on Oct 1, 2026.
We could combine duplicate location statements. Now Responsibilities: list each responsibility as - .
Now Skills: combine essential and additional.
Essential Skills list:
- Experience in construction management.
- Expertise in mission-critical and data center construction.
- Proficiency in hyperscale construction and contract negotiation.
- Strong understanding of mechanical systems and site development.
Additional Skills & Qualifications:
- Proficiency with Procore.
- Experience using Bluebeam.
We'll combine into one list.
Now Benefits: include preamble paragraph then list.
Now Pay: include paragraph(s) about pay range and compensation factors.
Now ensure we don't include any boilerplate like "Eligibility requirements apply..." that's part of benefits preamble, we keep that.
Now output only HTML fragment.
Let's craft.
Check for any duplicated lines: we have "This is a Contract position based out of Saint Louis, MO." and "This is a fully onsite position in Saint Louis, MO." Could combine: "This is a Contract, fully onsite position based out of Saint Louis, MO." Keep both? Might be redundant but we can combine to avoid duplication. The rule: remove duplicated lines. So we should combine.
Thus About the role paragraph: combine.
Let's write: