Construction Manager, Data Center Project Development

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include sections only when posting has real specific content. We have content: description of role (overview) could go under About the role. Responsibilities list. Minimum Qualifications (Requirements). Preferred Qualifications (maybe Qualifications or Skills). There's also "About Meta" but that's boilerplate? It's about company, not role; we can drop as it's not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Meta" might be considered boilerplate? It's not EEO but it's company description; could be considered not required but maybe we can keep as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The About Meta paragraph is substantive about company but not about role. However we might still include it under About the role? The heading "About the role" is for role description, not company. But we could treat the initial paragraph as role overview. The "About Meta" paragraph is separate; we could drop it as it's not about the role? The instruction says remove boilerplate, duplicated lines, and application instructions. "About Meta" is not boilerplate per se but it's generic company description; might be considered not needed. However they said preserve ALL substantive information; but also they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About Meta is not those categories. It's substantive about company. Should we keep? Probably yes, but we need a heading. Could use

About the role

and include both the role overview and About Meta? Might be mixing. Better to have

About the role

for the role overview paragraph (the first paragraph). Then maybe

About Meta

is not in the list of allowed headings; only allowed headings are those listed. So we cannot create a heading not in list. So we must either omit About Meta or incorporate it into About the role section (since it's still substantive). The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but likely only those headings allowed. Safer to stick to those headings. So we can put company description under About the role as extra context. Now Responsibilities: we have a list after "Responsibilities:" with multiple bullet-like sentences separated by line breaks. We'll turn each into

. Requirements: Minimum Qualifications list. Qualifications: Preferred Qualifications list. Skills: maybe we can extract skills from preferred qualifications? But we already have Qualifications section; Skills could be separate if we have skill-specific content. The preferred qualifications include AI skill development, integrating AI tools, familiarity with data center M&E systems, professional credentials, experience delivering hyperscale data center projects, proficiency with construction analytics platforms. Those could be considered skills. But we already have Qualifications; we could treat Preferred Qualifications as Qualifications section. The instruction: Use headings like Qualifications, Skills. We could have both Qualifications (minimum) and Skills (preferred). But we need to avoid thin sections. Let's decide: Use Requirements for Minimum Qualifications, and Qualifications for Preferred Qualifications. Skills maybe not needed. Pay: we have salary range "$150,000/year to $209,000/year + bonus + equity + benefits". Also note about compensation details. So we can create Pay section with that info. Schedule: not mentioned; no schedule info. So omit Schedule. Benefits: mention "benefits" but not detailed; we have " + bonus + equity + benefits". No specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It mentions benefits generically but not specific. Likely we should not create Benefits section because no specific benefits listed. However there is a line: "In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." That's a generic statement; not specific. So we should omit Benefits. Thus sections: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Pay. Now we need to output HTML fragment only, no /. Use

for each heading, then content:

for prose,

• for lists. We must not repeat job title as heading. The job title is "Construction Manager, Data Center Project Development". Not used as heading. We must not put Job ID/requisition numbers as headings; none present. We need to preserve all substantive information: ensure we include all responsibilities, qualifications, etc. Let's extract the role overview paragraph: "Meta is seeking a Construction Manager to lead the delivery of large-scale data center construction projects that power the infrastructure behind Meta's global platforms. In this role, you will oversee all phases of data center construction — from site mobilization through commissioning — while driving analytics-informed decision-making across project schedules, cost performance, and contractor execution. You will serve as a key technical authority on construction methodology, quality assurance, and project controls, ensuring Meta's data center portfolio is delivered on time, within budget, and to the highest standards of operational readiness." That's the prose for About the role. Now Responsibilities list: after "Responsibilities:" we have sentences each ending with a period, separated by line breaks. Let's list them: - Lead end-to-end construction management for large-scale, mission-critical data center projects, including civil, structural, mechanical, and electrical scopes - Develop and maintain integrated project schedules, cost forecasts, and risk registers using construction analytics platforms and project controls methodologies - Establish and enforce quality assurance and quality control programs across general contractors, subcontractors, and specialty vendors on data center construction sites - Analyze construction performance data — including earned value, schedule variance, and productivity metrics — to identify trends, surface risks, and drive corrective actions - Partner with design, engineering, and commissioning teams to resolve field conflicts, manage RFIs and submittals, and ensure constructability of data center systems - Oversee contractor and subcontractor performance, including scope compliance, safety program adherence, and milestone accountability - Drive cross-functional alignment between real estate, design, procurement, and operations teams to support data center program delivery at scale - Define and implement construction reporting frameworks and dashboards that provide leadership with accurate, timely visibility into project health across the data center portfolio - Lead lessons-learned processes and contribute to the development of construction standards, playbooks, and best practices for future data center builds - Manage change order processes, contract compliance reviews, and owner-contractor dispute resolution to protect project scope and budget integrity Now Minimum Qualifications list: after "Minimum Qualifications:" we have bullet points: - 8+ years of experience in construction management for large-scale, mission-critical facilities such as data centers, industrial plants, or advanced manufacturing facilities - Experience applying project controls and construction analytics methodologies, including schedule analysis, cost tracking, earned value management, and risk quantification - Experience managing general contractors and subcontractors across civil, structural, mechanical, and electrical scopes on complex construction programs - Experience leading cross-functional project teams and driving alignment across design, engineering, procurement, and commissioning stakeholders - Experience with construction contract administration, including RFI management, submittal review, change order negotiation, and claims avoidance Now Preferred Qualifications list: after "Preferred Qualifications:" we have many items, some duplicated. Let's extract unique items: - Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies - Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements) - Familiarity with data center mechanical and electrical systems, including chilled water plants, UPS infrastructure, switchgear, and generator systems - Professional credentials such as CCM, PMP, or PE licensure in a relevant engineering discipline - Experience delivering hyperscale or colocation data center construction projects exceeding 50MW critical IT load - Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews) - Proficiency with construction analytics and project controls platforms such as Primavera P6, Procore, or Power BI for portfolio-level reporting Note there are duplicates: "Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements)" appears twice; "Demonstrated ongoing AI skill development..." appears twice; "Experience adhering to and implementing responsible, ethical AI practices..." appears twice. We'll keep each once. Now Pay: "$150,000/year to $209,000/year + bonus + equity + benefits Individual compensation is determined by skills, qualifications, experience, and location. Compensation details listed in this posting reflect the base hourly rate, monthly rate, or annual salary only, and do not include bonus, equity or sales incentives, if applicable. In addition to base compensation, Meta offers benefits. Learn more about benefits at Meta." We should preserve all that info. Could be a

  with that text. Now we need to ensure we don't include any boilerplate like EEO etc. We removed the About Meta paragraph and EEO statement. Now construct HTML:

  About the role

  Meta is seeking a Construction Manager to lead the delivery of large-scale data center construction projects that power the infrastructure behind Meta's global platforms. In this role, you will oversee all phases of data center construction — from site mobilization through commissioning — while driving analytics-informed decision-making across project schedules, cost performance, and contractor execution. You will serve as a key technical authority on construction methodology, quality assurance, and project controls, ensuring Meta's data center portfolio is delivered on time, within budget, and to the highest standards of operational readiness.

  Responsibilities

  • Lead end-to-end construction management for large-scale, mission-critical data center projects, including civil, structural, mechanical, and electrical scopes
  • Develop and maintain integrated project schedules, cost forecasts, and risk registers using construction analytics platforms and project controls methodologies
  • Establish and enforce quality assurance and quality control programs across general contractors, subcontractors, and specialty vendors on data center construction sites
  • Analyze construction performance data — including earned value, schedule variance, and productivity metrics — to identify trends, surface risks, and drive corrective actions
  • Partner with design, engineering, and commissioning teams to resolve field conflicts, manage RFIs and submittals, and ensure constructability of data center systems
  • Oversee contractor and subcontractor performance, including scope compliance, safety program adherence, and milestone accountability
  • Drive cross-functional alignment between real estate, design, procurement, and operations teams to support data center program delivery at scale
  • Define and implement construction reporting frameworks and dashboards that provide leadership with accurate, timely visibility into project health across the data center portfolio
  • Lead lessons-learned processes and contribute to the development of construction standards, playbooks, and best practices for future data center builds
  • Manage change order processes, contract compliance reviews, and owner-contractor dispute resolution to protect project scope and budget integrity

  Requirements

  • 8+ years of experience in construction management for large-scale, mission-critical facilities such as data centers, industrial plants, or advanced manufacturing facilities
  • Experience applying project controls and construction analytics methodologies, including schedule analysis, cost tracking, earned value management, and risk quantification
  • Experience managing general contractors and subcontractors