Senior Construction Manager - Data Center Construction
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text like "commensurate with experience", etc. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Key content:
- Intro about CoreWeave (company description) maybe not needed? It's part of posting but not a section? Could be part of "About the role"? Actually "About The Role" heading appears. The intro before "What You’ll Do" is generic company description. Might be considered part of "About the role"? But we have "About The Role" heading already. We'll treat that as section heading.
- "What You’ll Do" is responsibilities.
- "About The Role" maybe duplicates? Actually they have "About The Role" heading then description. Then "Who You Are" is qualifications/requirements.
- Then "Preferred ..." maybe part of qualifications.
- Then "Wondering if you’re a good fit?" maybe not needed.
- Then "Why CoreWeave?" includes culture description.
- Then "The base salary range for this role is $143,000 to $210,000." plus details about compensation.
- Then "What We Offer" benefits list.
- Then "California Applicants" etc legal boilerplate to remove.
- Export Control Compliance also legal to remove.
We need to include sections only if real specific content.
Potential sections:
- About the role (maybe combine with What You’ll Do? Actually they have both. Could have "About the role" as prose, and "Responsibilities" as list.
But we need to follow instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content.
We have content for:
- About the role: description of role (owner's representative, leading projects, etc). Could be prose.
- Responsibilities: list of duties (oversee GCs, manage contracts, ensure alignment, focus on MEP commissioning, travel, drive projects, provide updates). Could be list.
- Requirements/Qualifications: education, years experience, data center experience, contract value, understanding of infrastructure, knowledge, software, driver's license, inspections, etc. Could be list.
- Skills: maybe not explicitly listed but could infer from requirements. Might not need separate Skills if covered.
- Benefits: list of benefits (medical, dental, vision, life insurance, disability, FSA, HSA, tuition reimbursement, ESPP, mental wellness, family-forming support, paid parental leave, childcare support, 401k match, flexible PTO, catered lunch, casual work environment, innovative disruption culture). Could be list.
- Pay: base salary range $143,000 to $210,000, plus discretionary bonus, equity awards, total rewards. Could be prose or list.
- Schedule: not mentioned (travel regularly to project sites). Could be considered schedule? Not explicit. Probably omit.
We should not include sections with placeholder text.
We need to avoid duplication: ensure we don't repeat same info.
We need to remove boilerplate: EEO, legal, export control, California Applicants, etc.
Also remove duplicated lines: maybe some repeated sentences.
We need to preserve all substantive information.
Let's extract substantive content:
Company description: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com."
This is company overview; could be included as part of "About the role" or maybe a separate "About CoreWeave"? Not in allowed headings list but we could put under "About the role". However "About the role" is supposed to be about the role, not company. But we could still include it as prose under About the role heading? Might be okay but maybe better to include a short paragraph about company under About the role? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It says "include a section ONLY when the posting has real, specific content for it". So we could have a section "About CoreWeave" but not in the list; maybe better to incorporate into About the role or omit. Since they didn't list "About CoreWeave" as example, but they said e.g., meaning those are examples, not exclusive. However to be safe, we can include a short paragraph under "About the role" that includes company description? Might be mixing.
Better: Have a section "About the role" with description of role (what you'll do). And maybe a separate "About CoreWeave" not needed. The company description is not essential to the role but is substantive. Could we include it as a preamble before headings? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid having introductory paragraphs before headings. But they said use for section headings. It didn't say we cannot have other elements like
outside sections. However they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can have
for prose anywhere.
Thus we could start with a
containing company overview, then headings for sections.
Let's decide:
-
company overview.
-
About the role
with prose describing role (owner's representative, leading projects, etc). Could be taken from "About The Role" paragraph.
- Responsibilities
with - list from "What You’ll Do" and maybe other duty sentences.
-
Requirements
with - list from "Who You Are" (education, years experience, data center experience, contract value, infrastructure understanding, knowledge, software, driver's license, inspections). Also maybe include "Preferred ..." as optional but we can include as part of requirements? Might be separate "Preferred Qualifications". But we can combine.
-
Benefits
with - list from "What We Offer".
-
Pay
with prose about base salary range, discretionary bonus, equity awards, total rewards.
We should not include Schedule as no specific schedule info.
We must not repeat job title as heading.
We must not include Job ID/requisition numbers.
We must remove boilerplate: EEO, legal, export control, California Applicants, etc.
We must remove duplicated lines: check for duplicates like "The base salary range for this role is $143,000 to $210,000." appears twice? Actually appears in "The base salary range for this role is $143,000 to $210,000." and later "The range we’ve posted represents the typical compensation range for this role." We'll keep only once.
Now craft HTML.
Let's extract precise sentences.
Company overview paragraph:
"CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com."
We'll put that as .
About the role paragraph: from "About The Role":
"As a Senior Data Center Construction Project Manager, you will serve as CoreWeave’s on-site owner’s representative, leading construction projects from pre-construction through close-out. You will oversee general contractors, manage contracts, and ensure projects are delivered in alignment with design specifications, budgets, master schedules, and committed Ready-for-Service (RFS) dates. You will have a strong focus on the coordination and commissioning of MEP and low-voltage systems and will travel regularly to project sites to validate construction progress, verify work quality, and proactively identify and address schedule, cost, and delivery risks. You will drive projects toward successful completion while providing leadership with regular updates on progress, financials, risks, and overall project status."
We'll put that as
under
About the role
.
Responsibilities list: from "What You’ll Do" (the bullet before About The Role) plus maybe some from About The Role? Actually "What You’ll Do" is a short sentence: "You will be a key leader within CoreWeave’s Construction Services and Program Management team, driving the successful delivery of hyperscale data center construction projects across our global portfolio." That's a responsibility. Also the About The Role paragraph includes many responsibilities. We'll combine.
List items:
- Be a key leader within CoreWeave’s Construction Services and Program Management team, driving the successful delivery of hyperscale data center construction projects across the global portfolio.
- Serve as CoreWeave’s on-site owner’s representative, leading construction projects from pre-construction through close-out.
- Oversee general contractors and manage contracts.
- Ensure projects are delivered in alignment with design specifications, budgets, master schedules, and committed Ready-for-Service (RFS) dates.
- Focus on the coordination and commissioning of MEP and low-voltage systems.
- Travel regularly to project sites to validate construction progress, verify work quality, and proactively identify and address schedule, cost, and delivery risks.
- Drive projects toward successful completion while providing leadership with regular updates on progress, financials, risks, and overall project status.
We'll put these in - .
Requirements list: from "Who You Are":
- B.S. or B.A. degree in Construction, Architecture, Engineering, or a related field.
- Minimum of 7 years of construction project management experience.
- Minimum of 3 years of direct experience managing data center construction projects with a strong emphasis on MEP (Mechanical, Electrical, Plumbing) systems.
- Demonstrated experience managing projects with a contract value of $100M+.
- Deep understanding of data center infrastructure, including power distribution, cooling systems, and redundancy protocols.
- Knowledge of construction components, processes, methodologies, and cost estimation.
- Experience with web-based project management software.
- Valid driver's license with no significant MVA points/violations.
- Experience conducting on-site progress inspections and verifying contractor work against drawings, specifications, and the master schedule.
Preferred (we could include as part of requirements or separate but we can add as bullet points prefixed with "Preferred:" or just include as requirements but note they are preferred. To avoid misrepresenting, we could add a note: "Preferred:" but that might be considered filler? It's substantive. We'll include as bullet points with "(Preferred)" maybe.
-
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text like "commensurate with experience", etc. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Intro about CoreWeave (company description) maybe not needed? It's part of posting but not a section? Could be part of "About the role"? Actually "About The Role" heading appears. The intro before "What You’ll Do" is generic company description. Might be considered part of "About the role"? But we have "About The Role" heading already. We'll treat that as section heading. - "What You’ll Do" is responsibilities. - "About The Role" maybe duplicates? Actually they have "About The Role" heading then description. Then "Who You Are" is qualifications/requirements. - Then "Preferred ..." maybe part of qualifications. - Then "Wondering if you’re a good fit?" maybe not needed. - Then "Why CoreWeave?" includes culture description. - Then "The base salary range for this role is $143,000 to $210,000." plus details about compensation. - Then "What We Offer" benefits list. - Then "California Applicants" etc legal boilerplate to remove. - Export Control Compliance also legal to remove. We need to include sections only if real specific content. Potential sections: - About the role (maybe combine with What You’ll Do? Actually they have both. Could have "About the role" as prose, and "Responsibilities" as list. But we need to follow instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content.
We have content for:
- About the role: description of role (owner's representative, leading projects, etc). Could be prose.
- Responsibilities: list of duties (oversee GCs, manage contracts, ensure alignment, focus on MEP commissioning, travel, drive projects, provide updates). Could be list.
- Requirements/Qualifications: education, years experience, data center experience, contract value, understanding of infrastructure, knowledge, software, driver's license, inspections, etc. Could be list.
- Skills: maybe not explicitly listed but could infer from requirements. Might not need separate Skills if covered.
- Benefits: list of benefits (medical, dental, vision, life insurance, disability, FSA, HSA, tuition reimbursement, ESPP, mental wellness, family-forming support, paid parental leave, childcare support, 401k match, flexible PTO, catered lunch, casual work environment, innovative disruption culture). Could be list.
- Pay: base salary range $143,000 to $210,000, plus discretionary bonus, equity awards, total rewards. Could be prose or list.
- Schedule: not mentioned (travel regularly to project sites). Could be considered schedule? Not explicit. Probably omit.
We should not include sections with placeholder text.
We need to avoid duplication: ensure we don't repeat same info.
We need to remove boilerplate: EEO, legal, export control, California Applicants, etc.
Also remove duplicated lines: maybe some repeated sentences.
We need to preserve all substantive information.
Let's extract substantive content:
Company description: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com."
This is company overview; could be included as part of "About the role" or maybe a separate "About CoreWeave"? Not in allowed headings list but we could put under "About the role". However "About the role" is supposed to be about the role, not company. But we could still include it as prose under About the role heading? Might be okay but maybe better to include a short paragraph about company under About the role? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It says "include a section ONLY when the posting has real, specific content for it". So we could have a section "About CoreWeave" but not in the list; maybe better to incorporate into About the role or omit. Since they didn't list "About CoreWeave" as example, but they said e.g., meaning those are examples, not exclusive. However to be safe, we can include a short paragraph under "About the role" that includes company description? Might be mixing.
Better: Have a section "About the role" with description of role (what you'll do). And maybe a separate "About CoreWeave" not needed. The company description is not essential to the role but is substantive. Could we include it as a preamble before headings? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid having introductory paragraphs before headings. But they said use for section headings. It didn't say we cannot have other elements like
for section headings. It didn't say we cannot have other elements like
outside sections. However they said "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can have
for prose anywhere. Thus we could start with a
containing company overview, then headings for sections. Let's decide: -
company overview. -
About the role
with prose describing role (owner's representative, leading projects, etc). Could be taken from "About The Role" paragraph. -Responsibilities
with- list from "What You’ll Do" and maybe other duty sentences.
-
Requirements
with- list from "Who You Are" (education, years experience, data center experience, contract value, infrastructure understanding, knowledge, software, driver's license, inspections). Also maybe include "Preferred ..." as optional but we can include as part of requirements? Might be separate "Preferred Qualifications". But we can combine.
-
Benefits
with- list from "What We Offer".
-
Pay
with prose about base salary range, discretionary bonus, equity awards, total rewards. We should not include Schedule as no specific schedule info. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, legal, export control, California Applicants, etc. We must remove duplicated lines: check for duplicates like "The base salary range for this role is $143,000 to $210,000." appears twice? Actually appears in "The base salary range for this role is $143,000 to $210,000." and later "The range we’ve posted represents the typical compensation range for this role." We'll keep only once. Now craft HTML. Let's extract precise sentences. Company overview paragraph: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com." We'll put that as. About the role paragraph: from "About The Role": "As a Senior Data Center Construction Project Manager, you will serve as CoreWeave’s on-site owner’s representative, leading construction projects from pre-construction through close-out. You will oversee general contractors, manage contracts, and ensure projects are delivered in alignment with design specifications, budgets, master schedules, and committed Ready-for-Service (RFS) dates. You will have a strong focus on the coordination and commissioning of MEP and low-voltage systems and will travel regularly to project sites to validate construction progress, verify work quality, and proactively identify and address schedule, cost, and delivery risks. You will drive projects toward successful completion while providing leadership with regular updates on progress, financials, risks, and overall project status." We'll put that as
under
About the role
. Responsibilities list: from "What You’ll Do" (the bullet before About The Role) plus maybe some from About The Role? Actually "What You’ll Do" is a short sentence: "You will be a key leader within CoreWeave’s Construction Services and Program Management team, driving the successful delivery of hyperscale data center construction projects across our global portfolio." That's a responsibility. Also the About The Role paragraph includes many responsibilities. We'll combine. List items: - Be a key leader within CoreWeave’s Construction Services and Program Management team, driving the successful delivery of hyperscale data center construction projects across the global portfolio. - Serve as CoreWeave’s on-site owner’s representative, leading construction projects from pre-construction through close-out. - Oversee general contractors and manage contracts. - Ensure projects are delivered in alignment with design specifications, budgets, master schedules, and committed Ready-for-Service (RFS) dates. - Focus on the coordination and commissioning of MEP and low-voltage systems. - Travel regularly to project sites to validate construction progress, verify work quality, and proactively identify and address schedule, cost, and delivery risks. - Drive projects toward successful completion while providing leadership with regular updates on progress, financials, risks, and overall project status. We'll put these in- . Requirements list: from "Who You Are": - B.S. or B.A. degree in Construction, Architecture, Engineering, or a related field. - Minimum of 7 years of construction project management experience. - Minimum of 3 years of direct experience managing data center construction projects with a strong emphasis on MEP (Mechanical, Electrical, Plumbing) systems. - Demonstrated experience managing projects with a contract value of $100M+. - Deep understanding of data center infrastructure, including power distribution, cooling systems, and redundancy protocols. - Knowledge of construction components, processes, methodologies, and cost estimation. - Experience with web-based project management software. - Valid driver's license with no significant MVA points/violations. - Experience conducting on-site progress inspections and verifying contractor work against drawings, specifications, and the master schedule. Preferred (we could include as part of requirements or separate but we can add as bullet points prefixed with "Preferred:" or just include as requirements but note they are preferred. To avoid misrepresenting, we could add a note: "Preferred:" but that might be considered filler? It's substantive. We'll include as bullet points with "(Preferred)" maybe. -
- list from "What We Offer".
-
- list from "Who You Are" (education, years experience, data center experience, contract value, infrastructure understanding, knowledge, software, driver's license, inspections). Also maybe include "Preferred ..." as optional but we can include as part of requirements? Might be separate "Preferred Qualifications". But we can combine.
-