Construction Manager, Lease - Data Center Construction
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 (the page already shows it) and 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 have Pay: "$150,000/year to $209,000/year + bonus + equity + benefits". That's specific, so we can include Pay section. Benefits: they mention benefits but not details; they say "Meta offers benefits. Learn more about benefits at Meta." That's vague; not specific benefits listed. So we should not create Benefits section unless specific content. So we omit Benefits.
Schedule: not mentioned. So omit.
About the role: The initial paragraph(s) before responsibilities: "Meta is seeking a Lease Construction Manager to oversee the delivery of leased data center facilities that power Meta's global infrastructure. In this role, you will serve as Meta's primary construction representative on colocation and build-to-suit data center projects, ensuring that landlord-delivered shell and core construction, critical infrastructure systems, and tenant improvement work meet Meta's technical specifications, schedule requirements, and quality standards. You will partner closely with real estate, design engineering, and data center operations teams to manage project execution from lease execution through facility acceptance and handover." That's substantive. So we can have About the role section.
Responsibilities: The bullet list after "Responsibilities:" is a long list of duties. We'll put each as
- under
.
Minimum Qualifications: list of qualifications. We'll put under Requirements or Qualifications? The instruction mentions sections: Requirements, Qualifications, Skills. We have Minimum Qualifications and Preferred Qualifications. We could combine into Qualifications section with sub-sections? But we need to follow instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have Requirements for minimum qualifications, Qualifications for preferred qualifications, maybe Skills for specific skills like Primavera P6, Google Workspace, Bluebeam, etc. However we must not create thin sections. We have a lot of content; we can split into Requirements (minimum qualifications) and Qualifications (preferred qualifications). Skills could be extracted from both but might be redundant. Better to have Requirements and Qualifications sections.
We need to preserve all substantive information. So we need to include all bullet points from Minimum Qualifications and Preferred Qualifications. Also we have some repeated lines about AI ethics etc repeated many times; we need to preserve but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say to deduplicate duplicates. However the duplicated lines appear many times (the AI ethics repeated). Should we keep them as they appear? Probably yes, but we could keep them once? The instruction says preserve ALL substantive information; duplicated lines are still substantive but repeating them may be unnecessary. However they are part of the posting; we could keep them but it's okay to deduplicate? The instruction does not explicitly forbid deduplication, but says do not invent or summarize away detail. Removing duplicates could be considered summarizing away detail? Might be okay but safer to keep them as they appear, but we can combine duplicates into a single entry to avoid redundancy? I'd lean to keep them as they appear but we can note that they are repeated many times; but the output would be huge with many repeats. Might be considered noise. However the instruction to remove duplicated lines: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should remove duplicated lines. Good. So we need to deduplicate repeated lines. The repeated lines: "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy review)" appears many times. We'll keep only one instance.
Also there is duplicate of "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)" with slight variation (reviews vs review). We'll treat as same and keep one.
Also there is duplicate of "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)" repeated many times. We'll keep one.
Also there is duplicate of "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)" maybe same.
We'll deduplicate.
Now we need to format.
We'll produce:
About the role
Meta is seeking a Lease Construction Manager to oversee the delivery of leased data center facilities that power Meta's global infrastructure. In this role, you will serve as Meta's primary construction representative on colocation and build-to-suit data center projects, ensuring that landlord-delivered shell and core construction, critical infrastructure systems, and tenant improvement work meet Meta's technical specifications, schedule requirements, and quality standards. You will partner closely with real estate, design engineering, and data center operations teams to manage project execution from lease execution through facility acceptance and handover.
Responsibilities
- Serve as Meta's owner's representative on leased data center construction projects, managing landlord and developer obligations from groundbreaking through certificate of occupancy and facility acceptance
- Review and provide technical feedback on landlord construction documents, including civil, structural, architectural, mechanical, electrical, and plumbing drawings, to ensure alignment with Meta's data center design standards
- Monitor construction progress on colocation and build-to-suit data center sites, conducting regular site visits to assess schedule adherence, quality of work, and conformance to contract requirements
- Coordinate tenant improvement construction activities, managing Meta's general contractors and specialty subcontractors delivering fit-out of white space, power distribution, cooling infrastructure, and network cabling systems
- Track and manage project schedules, budgets, and change order logs across multiple concurrent leased data center projects, providing regular status reporting to internal stakeholders
- Lead construction milestone reviews, factory acceptance tests, and integrated systems testing for critical infrastructure including UPS, generators, switchgear, cooling systems, and fire suppression
- Identify and escalate construction risks, schedule delays, and quality deficiencies to landlords and developers, driving resolution through contractual mechanisms and collaborative problem-solving
- Collaborate with data center commissioning teams to coordinate the transition from construction to commissioning and operations, ensuring all systems are tested and documented prior to handover
- Partner with real estate, legal, and lease administration teams to track landlord delivery obligations, punch list completion, and substantial completion milestones defined in lease agreements
- Contribute to the development and continuous improvement of Meta's leased data center construction standards, playbooks, and vendor qualification processes
Requirements
- 10+ years of work experience in construction management
- General knowledge of electrical and mechanical systems
- Knowledge of industry standards, building codes and safety standards including fire protection regulations
- Knowledge of capital budget management
- Negotiation skills and experience providing solutions to problems
- Experience using Primavera P6 for construction scheduling
- Proficient working knowledge of Google Workspace
- Proficient working knowledge of Bluebeam
Qualifications
- Bachelor's degree in Construction Management, Civil Engineering or equivalent degree and/or 12+ years of direct experience in project planning and construction management
- Experience reviewing/editing lease agreements, amendments and work letters
- Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements)
- MS Visio and Google Cloud experience
- Building Environment Accreditations (i.e. LEED, SITES, TRUE, WELL)
- Experience in adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy review)
- Multi-Project experience in large scale construction management, mission critical or infrastructure preferred
- Construction Management experience in the Lease/Colo market and live environment retrofit scopes of work
- Unified software experience
- Procore software experience
- Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies
- Connectivity Cabling and Data Center Construction Experience
- BIM 360 software experience
Pay
$150,000/year to $209,000/year + bonus + equity + benefits
We should not include Benefits section as no specific benefits listed.
Check for any other metadata like "Individual compensation is determined by skills, qualifications, experience, and location." That's more detail about pay; we could include in Pay section as a sentence. The instruction: preserve ALL substantive information. So we should include that line as part of Pay section maybe. Also "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." That's also substantive. We'll include in Pay section.
Thus Pay section could have multiple paragraphs.
We'll put:
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.
Now ensure no boilerplate like EEO etc removed. We removed the About Meta paragraph? Actually we kept About the role but not About Meta. The "About Meta:" paragraph is boilerplate? It's generic company description; could be considered boilerplate but it's substantive about Meta. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Meta:" is not explicitly listed as boilerplate to remove, but it's generic. However it's not about the role; it's about the company. Might be considered boilerplate but not prohibited. Safer to keep? The instruction says remove EEO etc. Not about Meta. I'd keep it? But we already have About the role section; we could add a short paragraph about Meta under About the role? Actually the About the role section already includes role description. The About Meta paragraph is separate; we could either include it as part of About the role or drop. Since it's not prohibited, we can keep it as a separate section maybe "About Meta". But the instruction only lists certain headings; we could add a section "About Meta" but not in the list. Better to
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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 have Pay: "$150,000/year to $209,000/year + bonus + equity + benefits". That's specific, so we can include Pay section. Benefits: they mention benefits but not details; they say "Meta offers benefits. Learn more about benefits at Meta." That's vague; not specific benefits listed. So we should not create Benefits section unless specific content. So we omit Benefits. Schedule: not mentioned. So omit. About the role: The initial paragraph(s) before responsibilities: "Meta is seeking a Lease Construction Manager to oversee the delivery of leased data center facilities that power Meta's global infrastructure. In this role, you will serve as Meta's primary construction representative on colocation and build-to-suit data center projects, ensuring that landlord-delivered shell and core construction, critical infrastructure systems, and tenant improvement work meet Meta's technical specifications, schedule requirements, and quality standards. You will partner closely with real estate, design engineering, and data center operations teams to manage project execution from lease execution through facility acceptance and handover." That's substantive. So we can have About the role section. Responsibilities: The bullet list after "Responsibilities:" is a long list of duties. We'll put each as
- .
Minimum Qualifications: list of qualifications. We'll put under Requirements or Qualifications? The instruction mentions sections: Requirements, Qualifications, Skills. We have Minimum Qualifications and Preferred Qualifications. We could combine into Qualifications section with sub-sections? But we need to follow instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have Requirements for minimum qualifications, Qualifications for preferred qualifications, maybe Skills for specific skills like Primavera P6, Google Workspace, Bluebeam, etc. However we must not create thin sections. We have a lot of content; we can split into Requirements (minimum qualifications) and Qualifications (preferred qualifications). Skills could be extracted from both but might be redundant. Better to have Requirements and Qualifications sections.
We need to preserve all substantive information. So we need to include all bullet points from Minimum Qualifications and Preferred Qualifications. Also we have some repeated lines about AI ethics etc repeated many times; we need to preserve but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say to deduplicate duplicates. However the duplicated lines appear many times (the AI ethics repeated). Should we keep them as they appear? Probably yes, but we could keep them once? The instruction says preserve ALL substantive information; duplicated lines are still substantive but repeating them may be unnecessary. However they are part of the posting; we could keep them but it's okay to deduplicate? The instruction does not explicitly forbid deduplication, but says do not invent or summarize away detail. Removing duplicates could be considered summarizing away detail? Might be okay but safer to keep them as they appear, but we can combine duplicates into a single entry to avoid redundancy? I'd lean to keep them as they appear but we can note that they are repeated many times; but the output would be huge with many repeats. Might be considered noise. However the instruction to remove duplicated lines: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should remove duplicated lines. Good. So we need to deduplicate repeated lines. The repeated lines: "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy review)" appears many times. We'll keep only one instance.
Also there is duplicate of "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)" with slight variation (reviews vs review). We'll treat as same and keep one.
Also there is duplicate of "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)" repeated many times. We'll keep one.
Also there is duplicate of "Experience adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy reviews)" maybe same.
We'll deduplicate.
Now we need to format.
We'll produce:
- Serve as Meta's owner's representative on leased data center construction projects, managing landlord and developer obligations from groundbreaking through certificate of occupancy and facility acceptance
- Review and provide technical feedback on landlord construction documents, including civil, structural, architectural, mechanical, electrical, and plumbing drawings, to ensure alignment with Meta's data center design standards
- Monitor construction progress on colocation and build-to-suit data center sites, conducting regular site visits to assess schedule adherence, quality of work, and conformance to contract requirements
- Coordinate tenant improvement construction activities, managing Meta's general contractors and specialty subcontractors delivering fit-out of white space, power distribution, cooling infrastructure, and network cabling systems
- Track and manage project schedules, budgets, and change order logs across multiple concurrent leased data center projects, providing regular status reporting to internal stakeholders
- Lead construction milestone reviews, factory acceptance tests, and integrated systems testing for critical infrastructure including UPS, generators, switchgear, cooling systems, and fire suppression
- Identify and escalate construction risks, schedule delays, and quality deficiencies to landlords and developers, driving resolution through contractual mechanisms and collaborative problem-solving
- Collaborate with data center commissioning teams to coordinate the transition from construction to commissioning and operations, ensuring all systems are tested and documented prior to handover
- Partner with real estate, legal, and lease administration teams to track landlord delivery obligations, punch list completion, and substantial completion milestones defined in lease agreements
- Contribute to the development and continuous improvement of Meta's leased data center construction standards, playbooks, and vendor qualification processes
- 10+ years of work experience in construction management
- General knowledge of electrical and mechanical systems
- Knowledge of industry standards, building codes and safety standards including fire protection regulations
- Knowledge of capital budget management
- Negotiation skills and experience providing solutions to problems
- Experience using Primavera P6 for construction scheduling
- Proficient working knowledge of Google Workspace
- Proficient working knowledge of Bluebeam
- Bachelor's degree in Construction Management, Civil Engineering or equivalent degree and/or 12+ years of direct experience in project planning and construction management
- Experience reviewing/editing lease agreements, amendments and work letters
- Demonstrated ability to integrate AI tools to optimize/redesign workflows and drive measurable impact (e.g., efficiency gains, quality improvements)
- MS Visio and Google Cloud experience
- Building Environment Accreditations (i.e. LEED, SITES, TRUE, WELL)
- Experience in adhering to and implementing responsible, ethical AI practices (e.g., risk assessment, bias mitigation, quality and accuracy review)
- Multi-Project experience in large scale construction management, mission critical or infrastructure preferred
- Construction Management experience in the Lease/Colo market and live environment retrofit scopes of work
- Unified software experience
- Procore software experience
- Demonstrated ongoing AI skill development (e.g., prompt/context engineering, agent orchestration) and staying current with emerging AI technologies
- Connectivity Cabling and Data Center Construction Experience
- BIM 360 software experience
About the role
Meta is seeking a Lease Construction Manager to oversee the delivery of leased data center facilities that power Meta's global infrastructure. In this role, you will serve as Meta's primary construction representative on colocation and build-to-suit data center projects, ensuring that landlord-delivered shell and core construction, critical infrastructure systems, and tenant improvement work meet Meta's technical specifications, schedule requirements, and quality standards. You will partner closely with real estate, design engineering, and data center operations teams to manage project execution from lease execution through facility acceptance and handover.
Responsibilities
Requirements
Qualifications
Pay
$150,000/year to $209,000/year + bonus + equity + benefits
We should not include Benefits section as no specific benefits listed. Check for any other metadata like "Individual compensation is determined by skills, qualifications, experience, and location." That's more detail about pay; we could include in Pay section as a sentence. The instruction: preserve ALL substantive information. So we should include that line as part of Pay section maybe. Also "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." That's also substantive. We'll include in Pay section. Thus Pay section could have multiple paragraphs. We'll put: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.
Now ensure no boilerplate like EEO etc removed. We removed the About Meta paragraph? Actually we kept About the role but not About Meta. The "About Meta:" paragraph is boilerplate? It's generic company description; could be considered boilerplate but it's substantive about Meta. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Meta:" is not explicitly listed as boilerplate to remove, but it's generic. However it's not about the role; it's about the company. Might be considered boilerplate but not prohibited. Safer to keep? The instruction says remove EEO etc. Not about Meta. I'd keep it? But we already have About the role section; we could add a short paragraph about Meta under About the role? Actually the About the role section already includes role description. The About Meta paragraph is separate; we could either include it as part of About the role or drop. Since it's not prohibited, we can keep it as a separate section maybe "About Meta". But the instruction only lists certain headings; we could add a section "About Meta" but not in the list. Better to