Director, Design Management
CoreWeave · Livingston, NJ · 3 wk ago
Hybrid$198k–$264k/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 remove boilerplate. Must preserve all substantive info.
We need to parse the posting: It includes "What You’ll Do" then "About The Role" then bullet list "In This Role, You Will" with many items. Then "Who You Are" with qualifications. Then "Wondering if you’re a good fit?" (some qualities). Then "Why CoreWeave? About At CoreWeave..." (some culture). No explicit Benefits, Pay, Schedule mentioned except "20% travel required". That's schedule? It's travel requirement, not schedule. No explicit pay or benefits. So we should not create Benefits, Pay, Schedule sections because no specific content.
We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (from "In This Role, You Will" list). Requirements (maybe from "Who You Are" bullet list of qualifications). Qualifications maybe overlapping; but we can combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can include both Requirements and Qualifications if content distinct. However "Who You Are" includes education, experience, skills, certifications. Could split into Requirements (experience) and Qualifications (education, licensure). Skills could be separate list of skills (people leadership, communication, analytical). But we must not create thin sections with filler. We need to ensure each section has substantive content.
Let's extract:
About the role: The paragraph after "About The Role": "We are seeking an accomplished Director level individual to lead the Design Management team responsible for overseeing project management across CoreWeave’s data center portfolio. This individual will supervise, mentor, and develop a team of Design Managers, ensuring they have the direction, resources, processes, and cross-functional support required to deliver successful projects. The Director will serve as CoreWeave’s subject matter expert in design project management, with a professional foundation in MEP, Architectural, Civil, or a related engineering discipline. This role will be accountable for the management and coordination of multidisciplinary design activities across Greenfield developments, build-to-suit facilities, leased data centers, tenant fit-outs, renovations, infrastructure upgrades, and equipment replacement projects. As a peer to the Director, Data Center Engineering and Director, Data Center Technology, the Director, Design Management will focus on design execution, project governance, resource allocation, consultant performance, and portfolio delivery. The role will partner closely with these technical leaders and their subject matter experts to ensure MEP, architectural, civil, low-voltage, structured cabling, and other technical requirements are incorporated into coordinated, constructible, and executable project designs. The Director will also serve as the senior escalation point for design delivery issues, providing leadership in resolving scope gaps, coordination conflicts, schedule constraints, consultant performance concerns, and other risks that could affect project outcomes. This individual will maintain portfolio-level visibility while remaining capable of engaging directly in complex or distressed projects when additional leadership is required. 20% travel required to various data center sites."
That's substantive.
Responsibilities: The list under "In This Role, You Will" each bullet (starting with "Team Leadership & Development:" etc). We'll put each as .
Requirements: Could be the experience requirements: "15+ years of progressively responsible experience in data center design, engineering, design management, construction, or project delivery, including at least 5 years in a leadership or people-management role." Also maybe "Bachelor’s degree in Mechanical, Electrical, Civil, Architectural or a related engineering discipline." That's more qualification. But we can treat education as Qualification. Let's decide:
Qualifications: Education + licensure: "Bachelor’s degree in Mechanical, Electrical, Civil, Architectural or a related engineering discipline. Professional Engineer (PE), Registered Architect (RA), or equivalent professional licensure is a plus."
Requirements: Experience: "15+ years of progressively responsible experience in data center design, engineering, design management, construction, or project delivery, including at least 5 years in a leadership or people-management role." Also maybe "Demonstrated subject matter expertise in data center design project management, including management of scope, schedules, budgets, risks, consultants, design deliverables, technical reviews, and stakeholder decisions." That's more like requirement. Also "Proven experience leading and developing Design Managers, Project Managers, engineers, architects, or other multidisciplinary professionals." etc. Many of those are qualifications/requirements. Might be better to have a single "Requirements" section covering all the bullet points under "Who You Are". But we also have "Skills" maybe separate.
Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section called "Requirements". But they ask to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using both Requirements and Qualifications if content exists. However we risk thin sections.
Let's see content for Skills: The posting includes many skill items: "Strong working knowledge of data center infrastructure, including power distribution, UPS systems, generators, cooling plants, liquid cooling, BMS and controls, life-safety systems, white space infrastructure, low-voltage systems, and structured cabling." "Experience working with data center providers, real estate developers, A/E consultants, contractors, commissioning agents, equipment manufacturers, and other external partners." "Strong understanding of design contracts, consultant scopes, design schedules, fee structures, change management, deliverables, and professional service provider performance." "Excellent people-leadership skills, including the ability to establish accountability, manage performance, develop talent, and create an effective and collaborative team environment." "Excellent written, verbal, and executive-level communication skills, with the ability to translate complex project and technical issues into clear business impacts, options, and recommendations." "Ability to operate effectively in a fast-paced, dynamic environment while managing multiple projects, competing priorities, and evolving business requirements." "Strong analytical, organizational, negotiation, and problem-solving skills." "Professional certifications such as PMP, Uptime Institute, LEED, BICSI, or similar credentials are a plus."
These could be Skills.
Thus we can have sections: About the role, Responsibilities, Requirements (experience), Qualifications (education/licensure), Skills (the list). That seems reasonable and each has substantive content.
We must not include Benefits, Pay, Schedule.
Now we need to output HTML fragment: use for each section heading. Use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all points from each section.
Let's extract each piece precisely.
About the role paragraph: We'll copy as is, maybe preserve line breaks? We'll put in
.
Responsibilities: The list items start with bold headings like "Team Leadership & Development:" then description. We'll keep each as
- containing the heading and description. Should we keep the bold? Not needed; just plain text.
List items:
- Team Leadership & Development: Lead, manage, mentor, and develop a team of Design Managers. Establish clear expectations, provide ongoing coaching, evaluate performance, and support the continued growth of a high-performing team.
- Portfolio Design Delivery: Maintain oversight of design delivery across a portfolio of concurrent data center projects, ensuring each project is progressing in accordance with approved scope, schedule, budget, quality, and business requirements.
- Design Project Management Expertise: Serve as the organizational subject matter expert for data center design project management, establishing consistent methods for planning, coordinating, tracking, and delivering multidisciplinary design activities.
- Project Assignment & Resource Management: Assign Design Managers to projects based on complexity, geography, schedule, risk, and business priority. Monitor team capacity and develop staffing or consultant strategies to address resource constraints.
- Design Delivery Governance: Establish and administer design management processes, deliverable requirements, project controls, meeting structures, review milestones, decision logs, risk registers, change controls, and escalation pathways.
- Consultant & Provider Management: Oversee the performance of data center providers, architects, engineers, and other professional consultants. Establish expectations for deliverable quality, responsiveness, schedule performance, coordination, and adherence to contractual requirements.
- Executive Escalation & Risk Resolution: Serve as the senior escalation point for design delivery risks, unresolved coordination issues, scope gaps, consultant performance concerns, and decisions affecting project cost or schedule.
- Standards Implementation: Ensure CoreWeave’s Design & Engineering Guidelines, Basis of Design, technology standards, and project-specific requirements are communicated to external partners and consistently incorporated into project deliverables.
- Design Quality & Completeness: Establish expectations for interdisciplinary coordination, constructability, document completeness, quality control, and resolution of review comments. Participate in critical design reviews and page-turn meetings for high-risk or strategically important projects.
- Budget & Schedule Coordination: Partner with Construction Management, Finance, and other stakeholders to develop and monitor design schedules, consultant budgets, forecasts, and key milestones. Ensure design activities support procurement, construction, commissioning, and customer deployment requirements.
- Design Change Management: Establish disciplined processes for evaluating and documenting design changes, including their effects on project scope, cost, schedule, constructability, operations, and technical performance.
- RFP & Consultant Selection: Lead or support the development of RFPs, evaluation of proposals, selection of A/E consultants and other design partners, negotiation of scopes and fees, and ongoing management of consultant contracts and invoices.
- OFCI Equipment Coordination: Ensure the Design Management team coordinates Owner-Furnished, Contractor-Installed equipment requirements with Engineering, Technology, Construction, Procurement, and external design teams.
- Construction & Commissioning Support: Ensure appropriate design support continues through construction and commissioning, including the timely resolution of RFIs, submittal reviews, field conditions, design clarifications, and changes affecting design intent.
- Executive & Portfolio Reporting: Provide executive leadership with clear reporting on design progress, project risks, consultant performance, key decisions, budgets, schedules, and issues requiring leadership action.
- Stakeholder Communication: Establish expectations for timely and effective communication across Design Management, Engineering, Technology, Construction, Operations, Capacity, Supply Chain, Network Engineering, and other project stakeholders.
- Project Handoffs: Ensure effective transitions between project development, design, procurement, construction, commissioning, and operations, with clear documentation of outstanding risks, decisions, and responsibilities.
- Process Improvement: Identify opportunities to improve design workflows, project gating, document control, consultant management, risk tracking, lessons learned, and overall consistency of project delivery.
- Continuous Improvement & Innovation: Collaborate with Engineering and Technology leadership to incorporate lessons learned, emerging technologies, and improved delivery practices into future projects.
Now Requirements (experience): We'll include:
- 15+ years of progressively responsible experience in data center design, engineering, design management, construction, or project delivery, including at least 5 years in a leadership or people-management role.
- Demonstrated subject matter expertise in data center design project management, including management of scope, schedules, budgets, risks, consultants, design deliverables, technical reviews, and stakeholder decisions.
- Proven experience leading and developing Design Managers, Project Managers, engineers, architects, or other multidisciplinary professionals.
- Proven track record of successfully managing the design delivery of large-scale, high-density data center projects.
- Experience overseeing multiple concurrent projects across different locations, project phases, delivery models, and levels of complexity.
We could also include "Strong working knowledge of data center infrastructure..." but that's more skill. We'll keep in Skills.
Qualifications (education/licensure):
- Bachelor’s degree in Mechanical, Electrical, Civil, Architectural or a related engineering discipline.
- Professional Engineer (PE), Registered Architect (RA), or equivalent professional licensure is a plus.
Skills: list:
- Strong working knowledge of data center infrastructure, including power distribution, UPS systems, generators, cooling plants, liquid cooling
for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all points from each section. Let's extract each piece precisely. About the role paragraph: We'll copy as is, maybe preserve line breaks? We'll put in
. Responsibilities: The list items start with bold headings like "Team Leadership & Development:" then description. We'll keep each as