Vice President Preconstruction
for 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. No metadata like Job ID. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting and extract sections.
Let's identify content:
- About the role: description of company, role context. Could be first paragraph: "My client, a global data center developer and operator..." etc. That's about the role.
- Responsibilities: bullet list of duties: "You own the full preconstruction lifecycle..." etc. Many bullet points.
- Requirements/Qualifications/Skills: The "What they are looking for" list: 15+ years experience, proven hyperscale, depth in power driven site selection, exposure to high density compute, commercial and financial acumen, executive presence, comfortable running several projects, degree in Construction Management, Engineering, Real Estate or similar, advanced degree welcome, travel around 30 percent.
We need to decide which headings to use: Requirements, Qualifications, Skills. The posting lumps them together; we could put under Requirements or Qualifications. Since they ask to prefer few substantive sections over many thin ones, we could combine into one section like "Requirements" containing all. Or we could split but they'd be thin. Better to have one "Requirements" section.
- Benefits, Pay, Schedule: Not explicitly mentioned. There's mention of travel 30% but that's not a benefit. No explicit benefits, pay, schedule. So we should NOT include those sections.
Thus we will have sections: About the role, Responsibilities, Requirements.
We need to use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. Must not omit details.
Let's extract prose for About the role: The first paragraph(s) up to "What you own". Actually "About the role" could be the introductory description before responsibilities. Let's capture: "My client, a global data center developer and operator with live campuses across North America, EMEA and Asia Pacific is hiring a VP of Preconstruction to lead the front end of its US expansion. They deliver for the largest hyperscalers, cloud providers and enterprise users in the world, and they build capacity ahead of demand rather than chasing it. This is an owner side seat with real authority. You decide whether a site is viable, what it should look like, what it should cost and when it can be delivered. The business builds its investment case around your answer. Where the role sits You sit inside the development group that shapes the entire US growth plan. Four functions under one roof: market strategy, site selection and acquisition, new site development, and preconstruction. The team assesses power, supply, demand, pricing and network fundamentals long before anyone buys land, then carries those sites through with commercial, sales, solution engineering, design, construction, and operations and finance. You are in the room when the big decisions get made. Preconstruction here is a strategic function, not a service function bolted onto construction. Location Washington DC, Virginia". That's a lot. We'll keep as prose.
But we need to avoid duplication: The location appears also later maybe. We'll include location in About the role.
Now Responsibilities: bullet list from "What you own" and day-to-day tasks. Let's extract bullet points:
- The full preconstruction lifecycle. Site validation and power feasibility at the front, master planning and design development through the middle, and a permit ready handover to construction at the back. The mandate is simple. Nothing reaches construction until the power is secured, the site is entitled, the cost is right and the design scales across multiple phases. Get that right and the business can commit hundreds of millions with confidence and execute on a predictable timeline.
- You are also the connector between development, design and construction. In most businesses those three groups sit in separate lanes and only meet when something has gone wrong. Here you keep them aligned from day one.
- Day to day:
* Set the preconstruction strategy, standards and delivery models for hyperscale and AI deployments. You are creating repeatable processes that let the business open new campuses faster than the competition, not inheriting someone else's playbook.
* Lead due diligence with power at the centre of everything. Utility coordination, large contiguous capacity, phased expansion capability and readiness for high density infrastructure. Environmental, zoning and permitting all sit under you, so sites arrive entitled and executable.
* Drive early design. Campus master planning, high density layouts, basis of design, liquid cooling readiness and rack densities built for what is coming rather than what is current. You shape how these campuses look for the next decade.
* Own the cost models and the schedules. Balance cost against speed against scalability, flag risk early and protect delivery certainty in markets where power is scarce and timelines are aggressive.
* Hand construction a project they can start immediately. Scope defined, budget aligned, documents permit ready and risk already stripped out.
* Represent the business externally with utilities, jurisdictions and strategic partners to secure power, entitlements and approvals. These relationships move timelines and you own them.
* Champion new delivery methods, design strategies and technologies that improve density, efficiency and speed to market, and feed lessons learned back across the portfolio.
We need to preserve all details; we can break into bullet items.
Now Requirements: list from "What they are looking for" and maybe also "Why this one is worth the call" but that's more motivational; could be included in About the role? It's not a requirement. We'll keep it maybe as part of About the role? But it's not required. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include that motivational paragraph somewhere. Could be part of About the role or a separate section like "Why this role is worth the call". But we only have headings list; we could add a section like "About the role" includes that. Or we could add a section "Why this role is worth the call" but not in prescribed headings; but we could still use
for any section heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could add other headings but they said "use for section headings (e.g. About the role, ...)". Likely they expect only those headings. Safer to stick to those. So we incorporate the motivational paragraph into About the role or Responsibilities? It's more about why the role is worth the call; could go under About the role as additional prose.
Thus About the role will include company description, role context, location, and the "Why this one is worth the call" paragraph.
Now we need to ensure we don't repeat job title. Not include "VP of Preconstruction" as heading. It's okay to mention in prose.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Make sure to preserve all details.
Let's craft About the role paragraph:
"My client, a global data center developer and operator with live campuses across North America, EMEA and Asia Pacific is hiring a VP of Preconstruction to lead the front end of its US expansion. They deliver for the largest hyperscalers, cloud providers and enterprise users in the world, and they build capacity ahead of demand rather than chasing it. This is an owner side seat with real authority. You decide whether a site is viable, what it should look like, what it should cost and when it can be delivered. The business builds its investment case around your answer. Where the role sits: you sit inside the development group that shapes the entire US growth plan. Four functions under one roof: market strategy, site selection and acquisition, new site development, and preconstruction. The team assesses power, supply, demand, pricing and network fundamentals long before anyone buys land, then carries those sites through with commercial, sales, solution engineering, design, construction, operations and finance. You are in the room when the big decisions get made. Preconstruction here is a strategic function, not a service function bolted onto construction. Location: Washington DC, Virginia. The AI build out is the biggest infrastructure story of our generation, and the winners will be the ones who secure power and get capacity live faster than anyone else. This role sits directly on that lever. You get the front end of a global platform, a power‑first development strategy, AI‑driven campus builds, real influence over capital decisions and the room to write the standards rather than follow them. If you have spent years delivering hyperscale work inside a GC or a consultancy and you are tired of executing someone else's strategy, this is the step across the table. There are not many preconstruction roles at this level, with this much ownership, in this market. When one comes up it usually goes quietly."
That seems to capture all.
Now Responsibilities bullet list: need to capture each bullet as separate - . Ensure we keep details.
Let's list:
- Own the full preconstruction lifecycle. Site validation and power feasibility at the front, master planning and design development through the middle, and a permit‑ready handover to construction at the back. The mandate is simple: nothing reaches construction until the power is secured, the site is entitled, the cost is right and the design scales across multiple phases. Getting this right lets the business commit hundreds of millions with confidence and execute on a predictable timeline.
- Act as the connector between development, design and construction. In most businesses those groups sit in separate lanes and only meet when something has gone wrong; here you keep them aligned from day one.
- Set the preconstruction strategy, standards and delivery models for hyperscale and AI deployments, creating repeatable processes that let the business open new campuses faster than the competition rather than inheriting someone else's playbook.
- Lead due diligence with power at the centre of everything: utility coordination, securing large contiguous capacity, ensuring phased expansion capability and readiness for high‑density infrastructure; environmental, zoning and permitting also fall under your purview so sites arrive entitled and executable.
- Drive early design: campus master planning, high‑density layouts, basis of design, liquid‑cooling readiness and rack densities built for what is coming rather than what is current, shaping how these campuses will look for the next decade.
- Own the cost models and the schedules, balancing cost against speed and scalability, flagging risk early and protecting delivery certainty in markets where power is scarce and timelines are aggressive.
- Hand construction a project they can start immediately: scope defined, budget aligned, documents permit‑ready and risk already stripped out.
- Represent the business externally with utilities, jurisdictions and strategic partners to secure power, entitlements and approvals; these relationships move timelines and you own them.
- Champion new delivery methods, design strategies and technologies that improve density, efficiency and speed to market, and feed lessons learned back across the portfolio.
Now Requirements bullet list:
- 15+ years of experience across preconstruction, development, design or construction leadership in data centres, critical infrastructure or large‑scale industrial projects.
- Proven hyperscale or campus‑style delivery experience, including phased execution across multiple buildings.
- Genuine depth in power‑driven site selection, due diligence, design management and cost estimation.
- Exposure to high‑density compute and AI infrastructure is a strong plus (though not a deal‑breaker).
- Strong commercial and financial acumen; you will influence investment decisions and portfolio strategy, not just report on them.
- Executive presence: you will regularly interface with senior leadership, utility executives and hyperscale customers.
- Comfortable running several large, fast‑moving projects simultaneously in competitive markets.
- Degree in Construction Management, Engineering, Real Estate or a related field; an advanced degree is welcome.
- Willingness to travel approximately 30
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. Must not omit details. Let's extract prose for About the role: The first paragraph(s) up to "What you own". Actually "About the role" could be the introductory description before responsibilities. Let's capture: "My client, a global data center developer and operator with live campuses across North America, EMEA and Asia Pacific is hiring a VP of Preconstruction to lead the front end of its US expansion. They deliver for the largest hyperscalers, cloud providers and enterprise users in the world, and they build capacity ahead of demand rather than chasing it. This is an owner side seat with real authority. You decide whether a site is viable, what it should look like, what it should cost and when it can be delivered. The business builds its investment case around your answer. Where the role sits You sit inside the development group that shapes the entire US growth plan. Four functions under one roof: market strategy, site selection and acquisition, new site development, and preconstruction. The team assesses power, supply, demand, pricing and network fundamentals long before anyone buys land, then carries those sites through with commercial, sales, solution engineering, design, construction, and operations and finance. You are in the room when the big decisions get made. Preconstruction here is a strategic function, not a service function bolted onto construction. Location Washington DC, Virginia". That's a lot. We'll keep as prose. But we need to avoid duplication: The location appears also later maybe. We'll include location in About the role. Now Responsibilities: bullet list from "What you own" and day-to-day tasks. Let's extract bullet points: - The full preconstruction lifecycle. Site validation and power feasibility at the front, master planning and design development through the middle, and a permit ready handover to construction at the back. The mandate is simple. Nothing reaches construction until the power is secured, the site is entitled, the cost is right and the design scales across multiple phases. Get that right and the business can commit hundreds of millions with confidence and execute on a predictable timeline. - You are also the connector between development, design and construction. In most businesses those three groups sit in separate lanes and only meet when something has gone wrong. Here you keep them aligned from day one. - Day to day: * Set the preconstruction strategy, standards and delivery models for hyperscale and AI deployments. You are creating repeatable processes that let the business open new campuses faster than the competition, not inheriting someone else's playbook. * Lead due diligence with power at the centre of everything. Utility coordination, large contiguous capacity, phased expansion capability and readiness for high density infrastructure. Environmental, zoning and permitting all sit under you, so sites arrive entitled and executable. * Drive early design. Campus master planning, high density layouts, basis of design, liquid cooling readiness and rack densities built for what is coming rather than what is current. You shape how these campuses look for the next decade. * Own the cost models and the schedules. Balance cost against speed against scalability, flag risk early and protect delivery certainty in markets where power is scarce and timelines are aggressive. * Hand construction a project they can start immediately. Scope defined, budget aligned, documents permit ready and risk already stripped out. * Represent the business externally with utilities, jurisdictions and strategic partners to secure power, entitlements and approvals. These relationships move timelines and you own them. * Champion new delivery methods, design strategies and technologies that improve density, efficiency and speed to market, and feed lessons learned back across the portfolio. We need to preserve all details; we can break into bullet items. Now Requirements: list from "What they are looking for" and maybe also "Why this one is worth the call" but that's more motivational; could be included in About the role? It's not a requirement. We'll keep it maybe as part of About the role? But it's not required. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include that motivational paragraph somewhere. Could be part of About the role or a separate section like "Why this role is worth the call". But we only have headings list; we could add a section like "About the role" includes that. Or we could add a section "Why this role is worth the call" but not in prescribed headings; but we could still use
for any section heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we could add other headings but they said "use
for section headings (e.g. About the role, ...)". Likely they expect only those headings. Safer to stick to those. So we incorporate the motivational paragraph into About the role or Responsibilities? It's more about why the role is worth the call; could go under About the role as additional prose. Thus About the role will include company description, role context, location, and the "Why this one is worth the call" paragraph. Now we need to ensure we don't repeat job title. Not include "VP of Preconstruction" as heading. It's okay to mention in prose. Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
- . Ensure we keep details. Let's list: - Own the full preconstruction lifecycle. Site validation and power feasibility at the front, master planning and design development through the middle, and a permit‑ready handover to construction at the back. The mandate is simple: nothing reaches construction until the power is secured, the site is entitled, the cost is right and the design scales across multiple phases. Getting this right lets the business commit hundreds of millions with confidence and execute on a predictable timeline. - Act as the connector between development, design and construction. In most businesses those groups sit in separate lanes and only meet when something has gone wrong; here you keep them aligned from day one. - Set the preconstruction strategy, standards and delivery models for hyperscale and AI deployments, creating repeatable processes that let the business open new campuses faster than the competition rather than inheriting someone else's playbook. - Lead due diligence with power at the centre of everything: utility coordination, securing large contiguous capacity, ensuring phased expansion capability and readiness for high‑density infrastructure; environmental, zoning and permitting also fall under your purview so sites arrive entitled and executable. - Drive early design: campus master planning, high‑density layouts, basis of design, liquid‑cooling readiness and rack densities built for what is coming rather than what is current, shaping how these campuses will look for the next decade. - Own the cost models and the schedules, balancing cost against speed and scalability, flagging risk early and protecting delivery certainty in markets where power is scarce and timelines are aggressive. - Hand construction a project they can start immediately: scope defined, budget aligned, documents permit‑ready and risk already stripped out. - Represent the business externally with utilities, jurisdictions and strategic partners to secure power, entitlements and approvals; these relationships move timelines and you own them. - Champion new delivery methods, design strategies and technologies that improve density, efficiency and speed to market, and feed lessons learned back across the portfolio. Now Requirements bullet list: - 15+ years of experience across preconstruction, development, design or construction leadership in data centres, critical infrastructure or large‑scale industrial projects. - Proven hyperscale or campus‑style delivery experience, including phased execution across multiple buildings. - Genuine depth in power‑driven site selection, due diligence, design management and cost estimation. - Exposure to high‑density compute and AI infrastructure is a strong plus (though not a deal‑breaker). - Strong commercial and financial acumen; you will influence investment decisions and portfolio strategy, not just report on them. - Executive presence: you will regularly interface with senior leadership, utility executives and hyperscale customers. - Comfortable running several large, fast‑moving projects simultaneously in competitive markets. - Degree in Construction Management, Engineering, Real Estate or a related field; an advanced degree is welcome. - Willingness to travel approximately 30