Senior Construction Manager - Data Center Construction
CoreWeave · West Chicago, IL · 4 wk ago
HybridManagement$143k–$210k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no boilerplate.
We need to parse the posting.
Let's extract sections:
- About the role: The paragraph after "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."
That's prose.
- Responsibilities: Possibly the "What You’ll Do" section: "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 short sentence. Could be considered responsibilities. Also maybe other responsibilities listed later? The "What You’ll Do" is a bullet? It's a sentence. Could be responsibilities.
- Requirements: The "Who You Are" bullet list: B.S. or B.A. degree..., minimum 7 years..., minimum 3 years..., demonstrated experience managing projects with contract value $100M+, deep understanding..., knowledge..., experience with web-based project management software, valid driver's license..., experience conducting on-site progress inspections... That's requirements.
- Qualifications: Possibly the "Preferred" bullet list: PMP Certification, LEED AP Certification, Direct experience with electrical and low-voltage equipment coordination, commissioning, or quality assurance. Those are preferred qualifications.
- Skills: Not explicitly listed but could be inferred from requirements: maybe we can include a Skills section summarizing skills like MEP coordination, contract management, budgeting, scheduling, etc. But we must not invent detail; we can only include if posting explicitly states skills. The posting mentions "Experience with web-based project management software", "Knowledge of construction components, processes, methodologies, and cost estimation", "Deep understanding of data center infrastructure". Those could be considered skills. However we need to decide if we should create a Skills section. The instruction: "Prefer a few substantive sections over many thin ones." We could combine Requirements and Qualifications into one? But they ask to use headings for those categories if content exists. We have content for Requirements and Qualifications (Preferred). So we can include both.
- Benefits: The posting lists benefits under "What We Offer": Medical, dental, vision insurance - 100% paid, Company-paid Life Insurance, Voluntary supplemental life insurance, Short and long-term disability, FSA, HSA, Tuition Reimbursement, Ability to Participate in ESPP, Mental Wellness Benefits through Spring Health, Family-Forming support via Carrot, Paid Parental Leave, Flexible, full-service childcare support with Kinside, 401(k) with generous employer match, Flexible PTO, Catered lunch each day, Casual work environment, Work culture focused on innovative disruption. That's substantive.
- Pay: The posting includes "The base salary range for this role is $143,000 to $210,000." Also mentions discretionary bonus, equity awards. So we have Pay content.
- Schedule: Not mentioned explicitly. No schedule info (like full-time, remote, etc). There's mention of travel regularly to project sites, but not schedule. So we should not create Schedule section.
- Also there is "About CoreWeave?" section: "Why CoreWeave? About At CoreWeave, we work hard, have fun, and move fast! ..." That's more about company culture; could be considered Benefits? But we already have Benefits. Could be a separate section like "About the Company" but not in allowed headings. The allowed headings are limited to those listed. So we could incorporate that into Benefits? But it's not a benefit; it's culture. However we could maybe put it under "About the role"? No. The instruction: "include a section ONLY when the posting has real, specific content for it". The allowed headings are those; we could decide not to include a section for company culture if not matching headings. So we omit.
- Also there is "Wondering if you’re a good fit?" paragraph with qualities; could be considered "Requirements" or "Skills"? It's more about qualities. Could be part of Requirements? But we already have requirements list. Might be better to include as a separate section like "Qualifications"? But we already have Preferred qualifications. Could treat those qualities as part of "Requirements" or "Skills". However to avoid inventing, we could include them as a bullet list under "Requirements" or "Skills"? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that content somewhere. If we don't have a heading that matches, we could still include it as a paragraph under an existing heading if appropriate. For example, under "About the role" we already have description; we could add those qualities as a paragraph under "About the role" or maybe under "Requirements". But they are not exactly requirements; they are "qualities we’ve found compatible". Could be considered "Preferred Qualifications". So we could add them to the Preferred qualifications list.
Thus we need to capture all substantive info: The "What You’ll Do" sentence, the "About The Role" paragraph, the "Who You Are" list (requirements), the "Preferred" list (preferred qualifications), the "Wondering if you’re a good fit?" paragraph (qualities), the "Why CoreWeave?" paragraph (culture), the benefits list, the pay range.
We must not include boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must remove the sections: "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations", "Export Control Compliance". Also remove the "Learn more at www.coreweave.com." maybe considered boilerplate? It's a link but not navigation; it's part of intro. Might be considered substantive? It's just a link; but it's not essential. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The link to website is not necessarily boilerplate but could be considered navigation? It's a link to learn more. Might be safe to keep? However it's not essential info about job. I'd consider it as optional; but we can keep it as part of intro? The intro also includes description of CoreWeave. That's company overview; not required heading but could be included as a paragraph under maybe "About the role"? But we already have About the role. Could add a brief intro before sections? The instruction: Output ONLY the HTML fragment. It didn't say we cannot have a leading paragraph before headings. But we should not repeat job title. The intro about CoreWeave could be considered "About the company" but not a heading. We could include it as a
before first heading. That's permissible. Thus structure:
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.
Then maybeAbout the role
with the paragraph. ThenResponsibilities
with- 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.
Requirements
with- list of the bullet points from "Who You Are". Also include the experience conducting on-site progress inspections etc.
Then
- ...
Qualifications
with- list of preferred: PMP Certification, LEED AP Certification, Direct experience with electrical and low-voltage equipment coordination, commissioning, or quality assurance. Also include the qualities from "Wondering if you’re a good fit?" maybe as additional list items.
Then
Benefits
with- list of benefits.
Then
Pay
withThe base salary range for this role is $143,000 to $210,000. The starting salary will be determined by job-related knowledge, skills, experience, and the market location. We strive for both market alignment and internal equity when determining compensation. In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility).
We could also include the sentence about "The range we’ve posted represents the typical compensation range for this role..." but that's somewhat repetitive; we can include as part of Pay. We must not include schedule. Check for any duplicated lines: Ensure we don't repeat same content. Now ensure we don't include any boilerplate like "California Applicants..." etc. Now produce HTML fragment. Let's draft. We need to ensure proper nesting:About the role
...
For lists: