Senior Construction Manager - Data Center Construction

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 parse the posting. First, the posting includes: - Intro about CoreWeave (company description) – not needed as heading? Possibly part of About the role? Actually "About The Role" heading present. The text after "About The Role" is: "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 responsibilities. Could be under Responsibilities. Then "Who You Are" includes qualifications: B.S. or B.A. degree..., minimum 7 years..., minimum 3 years direct experience..., 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..., Preferred PMP..., LEED AP..., Direct experience with electrical and low-voltage equipment coordination, commissioning, or quality assurance. That's qualifications/requirements. Then "Wondering if you’re a good fit?" includes qualities: love to take ownership..., curious..., expert in managing large-scale construction budgets, schedules, contracts... This could be Skills or maybe "Qualities". Could be under Skills. Then "Why CoreWeave?" includes About At CoreWeave... values etc. That's company culture; maybe not needed as a section unless we have Benefits etc. Could be omitted. Then "The 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)." That's Pay and Benefits. Then "What We Offer" includes list of benefits: Medical, dental, and vision insurance - 100% paid for by CoreWeave, Company-paid Life Insurance, Voluntary supplemental life insurance, Short and long-term disability insurance, Flexible Spending Account, Health Savings Account, Tuition Reimbursement, Ability to Participate in Employee Stock Purchase Program (ESPP), Mental Wellness Benefits through Spring Health, Family-Forming support provided by Carrot, Paid Parental Leave, Flexible, full-service childcare support with Kinside, 401(k) with a generous employer match, Flexible PTO, Catered lunch each day in our office and data center locations, A casual work environment, A work culture focused on innovative disruption. That's Benefits. Schedule: Not mentioned. No schedule info. So we should not include Schedule section. Pay: we have base salary range. So include Pay section. Now we need to decide sections: About the role (maybe we can use that heading for the description of role). Responsibilities (maybe we can combine with About the role? But we need to follow instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections. We need to decide which sections have content. We have: - About the role: Could be the introductory paragraph about the role (the "About The Role" paragraph). That is substantive. - Responsibilities: Could be the bullet list of duties? The posting didn't have bullet list but we can convert sentences into list items. The responsibilities are described in that paragraph. We could split into

• items. - Requirements: Could be the mandatory qualifications (B.S., 7 years, 3 years data center, $100M+, etc). That's requirements. - Qualifications: Could be the preferred qualifications (PMP, LEED AP, experience with electrical low-voltage). Or we could treat Requirements as mandatory and Qualifications as preferred. - Skills: Could be the "Wondering if you’re a good fit?" qualities (ownership, curiosity, expert managing budgets). Or we could treat as Skills. - Benefits: list from "What We Offer". - Pay: base salary range. We should not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We need to avoid boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we must remove the sections: "California Applicants California Consumer Privacy Act Equal Opportunity & Accommodations", "Export Control Compliance". Also remove "Wondering if you’re a good fit?" maybe not boilerplate but it's part of posting; we keep the qualities. We must not include duplicated lines. Now produce HTML fragment. We'll start with

  About the role

  then

  ... the paragraph from About The Role.

  Then

  Responsibilities

  then
  • items derived from that paragraph. We need to ensure we don't lose any detail. Let's extract responsibilities sentences: - Serve as CoreWeave’s on-site owner’s representative. - Leading construction projects from pre-construction through close-out. - Oversee general contractors. - Manage contracts. - Ensure projects are delivered in alignment with design specifications, budgets, master schedules, and committed Ready-for-Service (RFS) dates. - Have a strong 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 can break into list items. Now Requirements (mandatory): - 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. - A 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. Now Qualifications (preferred): - PMP (Project Management Professional) Certification. - LEED AP (Leadership in Energy and Environmental Design Accredited Professional) Certification. - Direct experience with electrical and low-voltage equipment coordination, commissioning, or quality assurance. Now Skills (from "Wondering if you’re a good fit?" qualities): - You love to take ownership and drive complex, technical projects from start to finish. - You’re curious about building the critical infrastructure that powers the future of computing. - You’re an expert in managing large-scale construction budgets, schedules, and contracts in mission-critical environments. We could phrase as list items. Now Benefits: list from "What We Offer". Need to preserve all items. Let's extract: - Medical, dental, and vision insurance - 100% paid for by CoreWeave - Company-paid Life Insurance - Voluntary supplemental life insurance - Short and long-term disability insurance - Flexible Spending Account - Health Savings Account - Tuition Reimbursement - Ability to Participate in Employee Stock Purchase Program (ESPP) - Mental Wellness Benefits through Spring Health - Family-Forming support provided by Carrot - Paid Parental Leave - Flexible, full-service childcare support with Kinside - 401(k) with a generous employer match - Flexible PTO - Catered lunch each day in our office and data center locations - A casual work environment - A work culture focused on innovative disruption We should keep each as
  • . Now Pay: base salary range $143,000 to $210,000. Also mention starting salary determined by job-related knowledge, skills, experience, market location; strive for market alignment and internal equity; total rewards includes discretionary bonus, equity awards, comprehensive benefits program (based on eligibility). We can include that in Pay section. Now Schedule: none, so omit. Now ensure we don't include any boilerplate like "CoreWeave is The Essential Cloud for AI™..." etc. That's company description at top; not needed as a heading. Could we include it under About the role? Probably not needed; but we might keep it as part of 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 we should stick to those. The company description is not part of those sections; we could omit it as it's not required. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive? It's about the company, not the role. Might be considered boilerplate? It's not navigation/legal/EEO etc. It's about the company. Might be considered relevant but not under headings. However the instruction says to output only HTML fragment; we could include a

    before any headings? It didn't forbid extra paragraphs. But they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings or paragraphs. But to be safe, we could include a brief intro paragraph before sections? The instruction: "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." So we can have

    for prose. So we could include a short paragraph about CoreWeave as prose before sections. That would preserve info. However the instruction also says "Prefer a few substantive sections over many thin ones." So we could include a brief intro paragraph. But the company description is several sentences; we could include as a

    before the first heading. Let's decide: include a

    with the 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." That's substantive. Now after that, we can have sections. Now ensure we don't include any duplicated lines. The posting had some duplicated lines like "What You’ll Do" and "About The Role". We'll not repeat. Now produce HTML. We'll need to escape any special characters? Not needed. Let's craft. Structure:

    CoreWeave is The Essential Cloud for