Director, Design Management

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: "What You’ll Do", "About The Role", "In This Role, You Will", "Who You Are", "Why CoreWeave?" plus maybe "About". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We need to include sections only when posting has real specific content. We must not include filler like "commensurate with experience". We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The posting includes some fluff like "CoreWeave is The Essential Cloud for AI™...". That's about company description; maybe we can include as part of "About" section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also have other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems those are examples; we can use those headings if appropriate. We need to map content. We have: - What You’ll Do: description of team responsibilities. Could map to Responsibilities. - About The Role: description of role expectations. Could map to About the role. - In This Role, You Will: bullet list of duties. Could map to Responsibilities as well (maybe combine). But we need to avoid duplication. We could have a single Responsibilities section with bullet list covering all duties. - Who You Are: qualifications, requirements. Could map to Requirements and Qualifications. - Why CoreWeave?: benefits/culture. Could map to Benefits (maybe also About company). But we need to include only if specific content. It includes culture statements: "we work hard, have fun, move fast..." plus core values. That's substantive. We also have travel requirement: 20% travel required. That could be part of Responsibilities or maybe a separate Schedule? Travel is not schedule but could be included in Responsibilities. We have no explicit Pay or Schedule (like work hours). So we should not create Pay or Schedule sections. We need to avoid duplication and boilerplate like "Learn more at www.coreweave.com." That's minor metadata; we can fold into a short p or drop. Probably drop. We need to remove duplicated lines, cookie/navigation/legal/EEO etc. There's none obvious. We need to preserve all substantive info. So we need to include the bullet points from "In This Role, You Will" as list items. Also include the responsibilities from "What You’ll Do" maybe as prose. We need to ensure we don't invent or summarize away detail. So we need to keep the specifics. Let's extract content: Company intro: "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 could include this as an "About" section (maybe not required but could be useful). The instruction says we can use headings like About the role etc. But we could also have an "About" heading for company overview. Not explicitly prohibited. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we could map company overview to "About the role"? No, that's about the role. Better to have a separate "About CoreWeave" maybe as

About CoreWeave

. But the instruction didn't list that as example; but it didn't say we cannot use other headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests those are typical headings; we can use them. Using other headings might be okay but risk. Safer to stick to those examples. So we could incorporate company overview into a short paragraph under "About the role" or maybe under a generic "About" but not listed. Could put under "About the role" as part of description? But "About the role" should be about the role, not company. However we could still include company overview as a brief intro 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." It doesn't forbid a general intro paragraph before headings. So we can have a

with company overview, then headings. Thus output:

CoreWeave is The Essential Cloud for AI™...

then sections. Now sections: - About the role: from "About The Role" paragraph(s). That includes description of role expectations, supervising team, etc. We'll put that as prose. - Responsibilities: combine "What You’ll Do" and "In This Role, You Will" bullet list. We'll make a

• list. - Requirements / Qualifications: from "Who You Are". Could split into Requirements (education, experience) and Qualifications (skills, certifications). But we can combine into one section maybe "Requirements". However instruction says we can have Requirements and Qualifications separate. We'll create two sections: Requirements (education, experience, licensure) and Qualifications (skills, expertise). But we need to ensure not to create thin sections. We have enough content. - Benefits: from "Why CoreWeave?" includes culture, values, hyper-growth, etc. We'll put as
  • list. - Pay and Schedule: not present, so omit. We must not include filler like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive info. Let's extract details. Company intro paragraph: We'll keep as is. About The Role paragraph(s): Let's copy: "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." We can keep that as prose. What You’ll Do paragraph: "The Data Center Design team is responsible for managing the delivery of architectural, engineering, and technology designs across CoreWeave’s global data center portfolio. The team coordinates the design lifecycle from early-stage project definition through construction, commissioning support and IT deployment, ensuring CoreWeave’s technical requirements are incorporated into each project and delivered in accordance with established scope, schedule, budget, and quality expectations. Working in partnership with the Data Center Engineering and Data Center Technology teams, Design Management integrates the work of internal subject matter experts, data center providers, architects, engineers, consultants, contractors, and equipment suppliers. Through disciplined project leadership, design coordination, and consistent execution, the team enables CoreWeave to rapidly and reliably expand its physical infrastructure to support next-generation, high-density compute workloads." We could incorporate that into Responsibilities as prose or bullet. But we already have About the role covering similar. To avoid duplication, we could merge What You’ll Do into Responsibilities as bullet points? But it's more description of team responsibilities. We'll keep it as part of Responsibilities prose maybe. In This Role, You Will: list of many bullet points. We'll extract each bullet as
  • . Let's list them: - 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