VP Construction & Delivery
for headings, - for lists,
for prose.
We must not repeat job title. Not include Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "250 MW of incremental capacity every quarter", "one to two gigawatts of AI infrastructure annually", etc.
We need to convert paragraphs into
. For lists, we need to identify bullet points.
Let's extract responsibilities:
"What You'll Do Reporting to the Chief Development Officer, you will lead Crux AI's data center construction program with a delivery mandate that runs the full distance from bare earth to a turnkey, operable product, taking in tenant fit-out readiness and the supply chain for next-generation designs. You carry full accountability for getting capacity built on time, on budget, and to standard, across both greenfield builds and fit-out inside partner shells. You will build and sustain a repeatable delivery engine capable of producing at least 250 MW of incremental capacity every quarter without compromising quality. That requires designing and building for the operational realities of AI data centers, including multiple availability levels across the capacity base rather than defaulting to one redundancy standard, and building capacity that stays fit for purpose as the hardware evolves. Over time the platform intends to deliver one to two gigawatts of AI infrastructure annually, which puts this among the most ambitious single-entity data center delivery programs ever attempted. You will own contractor engagement, program controls, and construction execution end to end, managing complex supply chains under demanding contract structures. The job is to deliver AI-ready capacity as a product - balancing speed, cost, and the technical demands of the next hardware generation, and building facilities customers will still want years from now. You will do that working hand in hand with development, the technical organization, and operations, and you will be central to converting unprecedented capital commitments into operational AI capacity."
We can break into paragraphs.
Now "SIGNALS OF SUCCESS" sections: After 60 Days, After 6 Months, After 1 Year. These are expectations; could be considered "Qualifications" or maybe "Requirements"? But they are more about what success looks like; could be under "Qualifications". However we have a separate "Qualifications" heading; we could put these signals there as a list.
But we also have "EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" which is clearly requirements/qualifications.
We need to decide mapping.
Option: Use "Requirements" for experiences/attributes/mindset. Use "Qualifications" for signals of success (maybe as expected outcomes). Or we could combine.
But we must not create empty sections. So we need to ensure each heading has content.
Let's list content blocks:
1. About the role: company intro paragraph.
2. Responsibilities: What You'll Do paragraph(s).
3. Requirements: Experiences, Attributes, Mindset section.
4. Qualifications: Signals of Success (60 days, 6 months, 1 year) maybe as list.
5. Skills: maybe not present; we could omit.
6. Benefits: benefits paragraph (health, dental, vision, life insurance, disability, optional benefits, 401k match).
7. Pay: Salary Range Information paragraph.
8. Schedule: Hybrid schedule detail (maybe we could include under Benefits but we have separate schedule heading; we can put schedule there and keep benefits without schedule duplication). However the benefits paragraph includes hybrid schedule; we could split: benefits paragraph without schedule, schedule paragraph separate.
But we must preserve all info; we can duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing; it's repeating. Might be okay but better to avoid duplication. We could put schedule in Benefits section and not have separate Schedule heading. But then we would have no Schedule section; that's okay if posting doesn't have specific schedule content separate from benefits. However the posting does mention hybrid schedule as part of benefits. So we could include schedule within Benefits. The instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having schedule info inside Benefits. So we can omit Schedule heading.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now we need to format.
Let's extract each block precisely.
About the role: The first paragraph(s) before "What You'll Do". It includes two sentences? Actually it's: "Built to set the gold standard for integrated AI infrastructure Crux AI is a newly formed, U.S.-based integrated AI infrastructure company created to remove the physical and operational constraints on consequential AI ambitions. Crux brings together power, high-density data centers, TPU silicon, networking, orchestration software, and ongoing operations as one integrated system. Crux is being capitalized to plan every layer together, develop each one to demanding standards, and operate the whole system with efficiency and reliability. That gives hyperscalers, frontier AI labs, sovereign customers, enterprises, and AI-native companies greater freedom to pursue the AI they are here to create."
We'll keep as one
.
Responsibilities: The "What You'll Do" block. Could split into multiple
for readability but not required. We'll keep as one
maybe long. But we could break into logical sentences; but not required. We'll keep as one
.
Requirements: The "EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" block. It includes bullet-like sentences separated by periods. We can convert to
- each item.
Let's list items:
- Hyperscale multi-site delivery. Senior experience leading construction of hyperscale or AI data center capacity, with direct accountability for large-scale, multi-site delivery.
- Groundworks to turnkey. Track record delivering from groundworks through to a fully operable turnkey product including tenant fit-out.
- A repeatable delivery engine. Command of construction execution at pace, with the ability to build and sustain an engine that produces significant incremental capacity on a rolling basis.
- Contractor and supply chain leadership. Deep experience managing contractors and complex supply chains under demanding contract structures.
- AI data center realities. Genuine understanding of the multiple availability levels that shape design, redundancy, and cost, and familiarity with next-generation design standards and what they mean for construction and the supply chain.
- Cost and TCO fluency. Commercial command of cost management and total cost of ownership, with a clear view on where modern methods of construction genuinely reduce cost rather than simply adding margin.
Then Attributes:
- Hands-on with real construction depth. Commands respect across contractors, engineers, and specialist delivery teams because the technical depth is there.
- Decisive under pressure. Makes high-quality construction decisions quickly and at scale.
- Cost-conscious and commercially minded. Delivers capacity efficiently without trading away reliability.
- Builds for operations, not for handover. Treats commissioning and operational readiness as the finish line rather than a closeout activity.
Mindset:
- Capacity as a product. Thinks in terms of a standard, repeatable, improving product rather than a series of bespoke projects.
- Comfortable in a capital-intensive, fast-moving environment. Entrepreneurial, without the scaffolding of an established program.
- Resilient and composed. Sustains pace and quality across a long-running, demanding program.
- Motivated by the build. Drawn to helping define a category rather than administering an existing one.
We could group all as list items.
Qualifications: Signals of Success.
We have three timeframes: After 60 Days, After 6 Months, After 1 Year. Each with bullet points.
We'll make
- each.
After 60 Days:
- You have your own assessment of every project in flight - schedule, budget, GMP quality, contractor performance.
- The basis of design and construction standards are locked for the first wave of sites, including the availability tiering that shapes redundancy and cost.
- Your construction leadership bench, program controls function, and commissioning approach are defined, and hiring is underway.
After 6 Months:
- The delivery engine is realized: standard playbooks, program controls, reporting, and a construction schedule the whole company plans against.
- GC and trade partner relationships are in place in every active market, contracted under structures that hold on price and schedule and hold contractors to both.
- Long-lead equipment and the supply chain for next-generation designs are mapped, with orders placed or escalated where they gate energization.
- The commissioning program is built and staffed through Level 5 and integrated systems testing, with the handover standard defined so operations inherits a proven facility.
- Fit-out execution inside partner shells is running in parallel with greenfield, and you can move capacity between the two paths as schedules shift.
- Cost forecasting is credible, with a view on where modern methods of construction take cost out rather than move margin around.
After 1 Year:
- The first building is energized and turned over on schedule, commissioned to standard, and operations accepted it without a punch list argument.
- You are delivering turnkey operable capacity.
- Tenant fit-out and next-generation design standards are integrated
for prose. We must not repeat job title. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "250 MW of incremental capacity every quarter", "one to two gigawatts of AI infrastructure annually", etc. We need to convert paragraphs into
. For lists, we need to identify bullet points. Let's extract responsibilities: "What You'll Do Reporting to the Chief Development Officer, you will lead Crux AI's data center construction program with a delivery mandate that runs the full distance from bare earth to a turnkey, operable product, taking in tenant fit-out readiness and the supply chain for next-generation designs. You carry full accountability for getting capacity built on time, on budget, and to standard, across both greenfield builds and fit-out inside partner shells. You will build and sustain a repeatable delivery engine capable of producing at least 250 MW of incremental capacity every quarter without compromising quality. That requires designing and building for the operational realities of AI data centers, including multiple availability levels across the capacity base rather than defaulting to one redundancy standard, and building capacity that stays fit for purpose as the hardware evolves. Over time the platform intends to deliver one to two gigawatts of AI infrastructure annually, which puts this among the most ambitious single-entity data center delivery programs ever attempted. You will own contractor engagement, program controls, and construction execution end to end, managing complex supply chains under demanding contract structures. The job is to deliver AI-ready capacity as a product - balancing speed, cost, and the technical demands of the next hardware generation, and building facilities customers will still want years from now. You will do that working hand in hand with development, the technical organization, and operations, and you will be central to converting unprecedented capital commitments into operational AI capacity." We can break into paragraphs. Now "SIGNALS OF SUCCESS" sections: After 60 Days, After 6 Months, After 1 Year. These are expectations; could be considered "Qualifications" or maybe "Requirements"? But they are more about what success looks like; could be under "Qualifications". However we have a separate "Qualifications" heading; we could put these signals there as a list. But we also have "EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" which is clearly requirements/qualifications. We need to decide mapping. Option: Use "Requirements" for experiences/attributes/mindset. Use "Qualifications" for signals of success (maybe as expected outcomes). Or we could combine. But we must not create empty sections. So we need to ensure each heading has content. Let's list content blocks: 1. About the role: company intro paragraph. 2. Responsibilities: What You'll Do paragraph(s). 3. Requirements: Experiences, Attributes, Mindset section. 4. Qualifications: Signals of Success (60 days, 6 months, 1 year) maybe as list. 5. Skills: maybe not present; we could omit. 6. Benefits: benefits paragraph (health, dental, vision, life insurance, disability, optional benefits, 401k match). 7. Pay: Salary Range Information paragraph. 8. Schedule: Hybrid schedule detail (maybe we could include under Benefits but we have separate schedule heading; we can put schedule there and keep benefits without schedule duplication). However the benefits paragraph includes hybrid schedule; we could split: benefits paragraph without schedule, schedule paragraph separate. But we must preserve all info; we can duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not inventing; it's repeating. Might be okay but better to avoid duplication. We could put schedule in Benefits section and not have separate Schedule heading. But then we would have no Schedule section; that's okay if posting doesn't have specific schedule content separate from benefits. However the posting does mention hybrid schedule as part of benefits. So we could include schedule within Benefits. The instruction says include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having schedule info inside Benefits. So we can omit Schedule heading. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now we need to format. Let's extract each block precisely. About the role: The first paragraph(s) before "What You'll Do". It includes two sentences? Actually it's: "Built to set the gold standard for integrated AI infrastructure Crux AI is a newly formed, U.S.-based integrated AI infrastructure company created to remove the physical and operational constraints on consequential AI ambitions. Crux brings together power, high-density data centers, TPU silicon, networking, orchestration software, and ongoing operations as one integrated system. Crux is being capitalized to plan every layer together, develop each one to demanding standards, and operate the whole system with efficiency and reliability. That gives hyperscalers, frontier AI labs, sovereign customers, enterprises, and AI-native companies greater freedom to pursue the AI they are here to create." We'll keep as one
. Responsibilities: The "What You'll Do" block. Could split into multiple
for readability but not required. We'll keep as one
maybe long. But we could break into logical sentences; but not required. We'll keep as one
. Requirements: The "EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" block. It includes bullet-like sentences separated by periods. We can convert to
- each item.
Let's list items:
- Hyperscale multi-site delivery. Senior experience leading construction of hyperscale or AI data center capacity, with direct accountability for large-scale, multi-site delivery.
- Groundworks to turnkey. Track record delivering from groundworks through to a fully operable turnkey product including tenant fit-out.
- A repeatable delivery engine. Command of construction execution at pace, with the ability to build and sustain an engine that produces significant incremental capacity on a rolling basis.
- Contractor and supply chain leadership. Deep experience managing contractors and complex supply chains under demanding contract structures.
- AI data center realities. Genuine understanding of the multiple availability levels that shape design, redundancy, and cost, and familiarity with next-generation design standards and what they mean for construction and the supply chain.
- Cost and TCO fluency. Commercial command of cost management and total cost of ownership, with a clear view on where modern methods of construction genuinely reduce cost rather than simply adding margin.
Then Attributes:
- Hands-on with real construction depth. Commands respect across contractors, engineers, and specialist delivery teams because the technical depth is there.
- Decisive under pressure. Makes high-quality construction decisions quickly and at scale.
- Cost-conscious and commercially minded. Delivers capacity efficiently without trading away reliability.
- Builds for operations, not for handover. Treats commissioning and operational readiness as the finish line rather than a closeout activity.
Mindset:
- Capacity as a product. Thinks in terms of a standard, repeatable, improving product rather than a series of bespoke projects.
- Comfortable in a capital-intensive, fast-moving environment. Entrepreneurial, without the scaffolding of an established program.
- Resilient and composed. Sustains pace and quality across a long-running, demanding program.
- Motivated by the build. Drawn to helping define a category rather than administering an existing one.
We could group all as list items.
Qualifications: Signals of Success.
We have three timeframes: After 60 Days, After 6 Months, After 1 Year. Each with bullet points.
We'll make
- each. After 60 Days: - You have your own assessment of every project in flight - schedule, budget, GMP quality, contractor performance. - The basis of design and construction standards are locked for the first wave of sites, including the availability tiering that shapes redundancy and cost. - Your construction leadership bench, program controls function, and commissioning approach are defined, and hiring is underway. After 6 Months: - The delivery engine is realized: standard playbooks, program controls, reporting, and a construction schedule the whole company plans against. - GC and trade partner relationships are in place in every active market, contracted under structures that hold on price and schedule and hold contractors to both. - Long-lead equipment and the supply chain for next-generation designs are mapped, with orders placed or escalated where they gate energization. - The commissioning program is built and staffed through Level 5 and integrated systems testing, with the handover standard defined so operations inherits a proven facility. - Fit-out execution inside partner shells is running in parallel with greenfield, and you can move capacity between the two paths as schedules shift. - Cost forecasting is credible, with a view on where modern methods of construction take cost out rather than move margin around. After 1 Year: - The first building is energized and turned over on schedule, commissioned to standard, and operations accepted it without a punch list argument. - You are delivering turnkey operable capacity. - Tenant fit-out and next-generation design standards are integrated