Data Center Site Selection - Hyperscale
Cloudflare · Seattle, WA · 3 wk ago
Engineering$166k–$271k/yrFull-time
We need to output only HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for headings. Use
for headings. Use - for lists. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content.
We need to parse the posting.
First, "About Us" is not needed; we can ignore.
"Available Locations: San Francisco, Austin, Seattle, or New York" - location info maybe part of About the role? Not a heading. Could be included as a paragraph under About the role? Not required but we can include as part of About the role.
"About The Role" heading: we have description. We'll put that under
About the role
with paragraphs.
Then "What you get to do in this role:" list of duties. That's responsibilities. So we can create Responsibilities
with - each bullet.
Then "Skills/Experience:" list of required experience. That's Requirements/Qualifications/Skills. We need to decide sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate ones.
We have "Skills/Experience:" with bullet points. That's skills/experience required. Could go under
Skills
or Requirements
. Also there is "Nice to have:" list. Could be under Qualifications
maybe? But we need to avoid thin sections. Perhaps combine required and nice-to-have under Skills? But we need to preserve all info.
We could have:
- About the role (description)
- Responsibilities (the "What you get to do...")
- Requirements (the "Skills/Experience:" required)
- Qualifications (the "Nice to have:")
- Benefits (the benefits description)
- Pay (the compensation section)
- Schedule (maybe travel expectation? There's "Travel as needed (expect :30%)" and also "Willing to travel :30%" in Skills/Experience. That's schedule? Not exactly schedule but travel expectation. Could put under Schedule heading: Travel expectation.
But we need to ensure we only create sections when there is real specific content. Travel expectation is specific: "Travel as needed (expect :30%)". So we can have Schedule section with that.
Pay: we have compensation details with ranges per location. That's specific. So Pay section.
Benefits: we have benefits description. So Benefits section.
Now we need to format.
We must not include boilerplate like "Equal opportunity employer", etc. Remove those.
We need to preserve all substantive information. Let's extract.
About the role paragraph: The block after "About The Role" up to "What you get to do in this role:" is description.
Let's copy:
"The Data Center Strategy team needs a site-selection manager who has closed NNN and wholesale leases at MW scale. You find the site, underwrite it, and get the paper signed. The binding constraint is usually power: available MW, interconnection, substation work, and when the site actually energizes. You also have to be right about land or campus control, fiber, water, flood and seismic, permitting, and latency onto Cloudflare’s network. The commercial work is NNN paper and the structures next to it: modified gross, FRI, wholesale dedicated-room, powered shell, build-to-suit, sale-leaseback, joint venture. Base rent, OpEx and tax passthroughs, escalators, work letters, landlord delivery, PUE treatment, delay credits, SLAs, ramp, expansion options, ROFR, exit and renewal. You build the pipeline (developers, brokers, wholesale operators, power developers, utilities), run technical diligence, and take a TCO / cost-per-MW / NPV pack to leadership for the capital ask. Several of these will be live at once, across markets. Legal, capacity planning, network strategy, energy, security, and finance all sit in the process. You own it through execution."
That's the prose.
Now Responsibilities: bullet list after "What you get to do in this role:" includes:
- Build and run a pipeline of MW-scale sites: developers, landlords, wholesale operators, power developers, utilities
- Lead technical diligence: power availability and energization, electrical topology and redundancy, rack density and cooling (including liquid), fiber diversity, PUE, geotech, permitting, commissioning evidence, network latency
- Run the deal from long list through RFP, site visit, LOI, lease or powered-shell, work letter, and signature (campuses, dedicated buildings, dedicated halls, core expansions, BTS)
- Negotiate NNN / triple-net and the structures next to it (modified gross, FRI, wholesale dedicated-room, powered shell, BTS, sale-leaseback, JV): $/kW-month, NRC/MRC, escalators, PUE, delay credits, SLAs, ramp, expansion rights, ROFR, exit and renewal
- Keep landlord scope and Cloudflare scope explicit, including power to dedicated PDU and tenant fit-out
- Build the TCO / cost-per-MW / NPV case and take the capital ask to leadership
- Work with legal, operations, capacity planning, network strategy, energy, and security on requirements and delivery dates
- Run QBRs with campus landlords. Represent Cloudflare with landlord executives and at industry events.
- Put MW, rent, passthroughs, NRC, and unit cost into the annual data center budget. Check rent and NNN recovery invoices against the lease.
- Travel as needed (expect :30%)
- Other duties as assigned
We should keep "Other duties as assigned" maybe but it's generic; could keep but it's not specific. Might be okay to keep but it's filler. The instruction: never emit a heading followed by filler/placeholder text. But this is a list item; it's okay? It's generic but not a heading. Probably fine to keep.
Now Requirements/Skills: The "Skills/Experience:" block:
- 10+ years selecting or leasing hyperscale or wholesale data centers, or planning MW-scale infrastructure, at a cloud, internet, content, or colocation company
- Closed NNN / triple-net leases as tenant or buy-side advisor, or the wholesale equivalents (modified gross, FRI, dedicated-hall, powered shell). Colo order forms and rack-level MRC do not count.
- Can underwrite $/kW-month or $/MW, escalators, OpEx passthrough, tenant improvement / work letters, TCO, and lease NPV, and take that pack to leadership
- Has led technical diligence on candidate sites (power, electrical topology, cooling, fiber, PUE, commissioning), not only commercial terms
- Knows how utility interconnection and substation timelines actually work
- Can run several site processes at once, across time zones, with incomplete information
- Has taken a campus or BTS lease from LOI to execution
- Willing to travel :30%
- International deal experience preferred
- Bachelor’s degree or equivalent experience required
Now "Nice to have:" list:
- Sale-leaseback, JV, or PPA / power-procurement work
- Existing relationships with developers, wholesale operators, brokers, or utilities
- High-density / liquid-cooling site constraints
- Network (fiber diversity, latency, MMR)
- Government incentives or economic-development agreements
- Another language
Now Benefits: The block after "Benefits" heading includes description. We need to extract substantive content: list of benefits categories.
Paragraph: "Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S."
Then list:
Health & Welfare Benefits
- Medical/Rx Insurance
- Dental Insurance
- Vision Insurance
- Flexible Spending Accounts
- Commuter Spending Accounts
- Fertility & Family Forming Benefits
- On-demand mental health support and Employee Assistance Program
- Global Travel Medical Insurance
Financial Benefits
- Short and Long Term Disability Insurance
- Life & Accident Insurance
- 401(k) Retirement Savings Plan
- Employee Stock Participation Plan
Time Off
- Flexible paid time off covering vacation and sick leave
- Leave programs, including parental, pregnancy health, medical, and bereavement leave
We should keep these as list items under Benefits.
Now Pay: Compensation section:
"Compensation Compensation may be adjusted depending on work location. For Bay Area based hires: Estimated annual salary of $166,000 - $271,000For New York based hires: Estimated annual salary of $158,000 - $257,000 For Seattle based hires: Estimated annual Salary of $158,000 - $257,000 Equity This role is eligible to participate in Cloudflare’s equity plan."
We need to format nicely. Probably separate paragraphs.
We should not repeat "Compensation Compensation". We'll just have a paragraph.
Now Schedule: Travel expectation. Already included in responsibilities bullet but also we could have a Schedule section with "Travel as needed (expect :30%)". But we already have that bullet. Might be redundant. The instruction: prefer a few substantive sections over many thin ones. We could omit Schedule section and keep travel under Responsibilities. However we have travel also in Skills/Experience. Might be okay to not have separate Schedule.
But we need to include Schedule heading only if posting has real specific content for it. The posting does mention travel expectation. Could be considered schedule. But we already have it under Responsibilities. Might be okay to not create Schedule heading to avoid thin section. However we need to decide.
Given we already have Responsibilities with travel bullet, we can skip Schedule.
Now we need to output only HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
...
We need to ensure we don't include empty sections.
Now we need to copy the text exactly, preserving details.
Let's craft About the role paragraph exactly as given.
Paragraph: "The Data Center Strategy team needs a site-selection manager who has closed NNN and wholesale leases at MW scale. You find the site, underwrite it, and get the paper signed. The binding constraint is usually power: available MW, interconnection, substation work, and when the site actually energizes. You also have to be right about land or campus control, fiber, water, flood and seismic, permitting, and latency onto Cloudflare’s network. The commercial work is NNN paper and the structures next to it: modified gross, FRI, wholesale dedicated-room, powered shell, build-to-suit, sale-leaseback, joint venture. Base rent, OpEx and tax passthroughs, escalators, work letters, landlord delivery, PUE treatment, delay credits, SLAs, ramp, expansion options, ROFR, exit and renewal. You build the pipeline (developers, brokers, wholesale operators, power developers, utilities), run technical diligence, and take a TCO / cost-per-MW / NPV pack to leadership for the capital ask. Several of these will be live at once, across markets. Legal, capacity planning, network strategy
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content. We need to parse the posting. First, "About Us" is not needed; we can ignore. "Available Locations: San Francisco, Austin, Seattle, or New York" - location info maybe part of About the role? Not a heading. Could be included as a paragraph under About the role? Not required but we can include as part of About the role. "About The Role" heading: we have description. We'll put that under
About the role
with paragraphs. Then "What you get to do in this role:" list of duties. That's responsibilities. So we can createResponsibilities
with- each bullet.
Then "Skills/Experience:" list of required experience. That's Requirements/Qualifications/Skills. We need to decide sections. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate ones.
We have "Skills/Experience:" with bullet points. That's skills/experience required. Could go under
Skills
orRequirements
. Also there is "Nice to have:" list. Could be underQualifications
maybe? But we need to avoid thin sections. Perhaps combine required and nice-to-have under Skills? But we need to preserve all info. We could have: - About the role (description) - Responsibilities (the "What you get to do...") - Requirements (the "Skills/Experience:" required) - Qualifications (the "Nice to have:") - Benefits (the benefits description) - Pay (the compensation section) - Schedule (maybe travel expectation? There's "Travel as needed (expect :30%)" and also "Willing to travel :30%" in Skills/Experience. That's schedule? Not exactly schedule but travel expectation. Could put under Schedule heading: Travel expectation. But we need to ensure we only create sections when there is real specific content. Travel expectation is specific: "Travel as needed (expect :30%)". So we can have Schedule section with that. Pay: we have compensation details with ranges per location. That's specific. So Pay section. Benefits: we have benefits description. So Benefits section. Now we need to format. We must not include boilerplate like "Equal opportunity employer", etc. Remove those. We need to preserve all substantive information. Let's extract. About the role paragraph: The block after "About The Role" up to "What you get to do in this role:" is description. Let's copy: "The Data Center Strategy team needs a site-selection manager who has closed NNN and wholesale leases at MW scale. You find the site, underwrite it, and get the paper signed. The binding constraint is usually power: available MW, interconnection, substation work, and when the site actually energizes. You also have to be right about land or campus control, fiber, water, flood and seismic, permitting, and latency onto Cloudflare’s network. The commercial work is NNN paper and the structures next to it: modified gross, FRI, wholesale dedicated-room, powered shell, build-to-suit, sale-leaseback, joint venture. Base rent, OpEx and tax passthroughs, escalators, work letters, landlord delivery, PUE treatment, delay credits, SLAs, ramp, expansion options, ROFR, exit and renewal. You build the pipeline (developers, brokers, wholesale operators, power developers, utilities), run technical diligence, and take a TCO / cost-per-MW / NPV pack to leadership for the capital ask. Several of these will be live at once, across markets. Legal, capacity planning, network strategy, energy, security, and finance all sit in the process. You own it through execution." That's the prose. Now Responsibilities: bullet list after "What you get to do in this role:" includes: - Build and run a pipeline of MW-scale sites: developers, landlords, wholesale operators, power developers, utilities - Lead technical diligence: power availability and energization, electrical topology and redundancy, rack density and cooling (including liquid), fiber diversity, PUE, geotech, permitting, commissioning evidence, network latency - Run the deal from long list through RFP, site visit, LOI, lease or powered-shell, work letter, and signature (campuses, dedicated buildings, dedicated halls, core expansions, BTS) - Negotiate NNN / triple-net and the structures next to it (modified gross, FRI, wholesale dedicated-room, powered shell, BTS, sale-leaseback, JV): $/kW-month, NRC/MRC, escalators, PUE, delay credits, SLAs, ramp, expansion rights, ROFR, exit and renewal - Keep landlord scope and Cloudflare scope explicit, including power to dedicated PDU and tenant fit-out - Build the TCO / cost-per-MW / NPV case and take the capital ask to leadership - Work with legal, operations, capacity planning, network strategy, energy, and security on requirements and delivery dates - Run QBRs with campus landlords. Represent Cloudflare with landlord executives and at industry events. - Put MW, rent, passthroughs, NRC, and unit cost into the annual data center budget. Check rent and NNN recovery invoices against the lease. - Travel as needed (expect :30%) - Other duties as assigned We should keep "Other duties as assigned" maybe but it's generic; could keep but it's not specific. Might be okay to keep but it's filler. The instruction: never emit a heading followed by filler/placeholder text. But this is a list item; it's okay? It's generic but not a heading. Probably fine to keep. Now Requirements/Skills: The "Skills/Experience:" block: - 10+ years selecting or leasing hyperscale or wholesale data centers, or planning MW-scale infrastructure, at a cloud, internet, content, or colocation company - Closed NNN / triple-net leases as tenant or buy-side advisor, or the wholesale equivalents (modified gross, FRI, dedicated-hall, powered shell). Colo order forms and rack-level MRC do not count. - Can underwrite $/kW-month or $/MW, escalators, OpEx passthrough, tenant improvement / work letters, TCO, and lease NPV, and take that pack to leadership - Has led technical diligence on candidate sites (power, electrical topology, cooling, fiber, PUE, commissioning), not only commercial terms - Knows how utility interconnection and substation timelines actually work - Can run several site processes at once, across time zones, with incomplete information - Has taken a campus or BTS lease from LOI to execution - Willing to travel :30% - International deal experience preferred - Bachelor’s degree or equivalent experience required Now "Nice to have:" list: - Sale-leaseback, JV, or PPA / power-procurement work - Existing relationships with developers, wholesale operators, brokers, or utilities - High-density / liquid-cooling site constraints - Network (fiber diversity, latency, MMR) - Government incentives or economic-development agreements - Another language Now Benefits: The block after "Benefits" heading includes description. We need to extract substantive content: list of benefits categories. Paragraph: "Cloudflare offers a complete package of benefits and programs to support you and your family. Our benefits programs can help you pay health care expenses, support caregiving, build capital for the future and make life a little easier and fun! The below is a description of our benefits for employees in the United States, and benefits may vary for employees based outside the U.S." Then list: Health & Welfare Benefits - Medical/Rx Insurance - Dental Insurance - Vision Insurance - Flexible Spending Accounts - Commuter Spending Accounts - Fertility & Family Forming Benefits - On-demand mental health support and Employee Assistance Program - Global Travel Medical Insurance Financial Benefits - Short and Long Term Disability Insurance - Life & Accident Insurance - 401(k) Retirement Savings Plan - Employee Stock Participation Plan Time Off - Flexible paid time off covering vacation and sick leave - Leave programs, including parental, pregnancy health, medical, and bereavement leave We should keep these as list items under Benefits. Now Pay: Compensation section: "Compensation Compensation may be adjusted depending on work location. For Bay Area based hires: Estimated annual salary of $166,000 - $271,000For New York based hires: Estimated annual salary of $158,000 - $257,000 For Seattle based hires: Estimated annual Salary of $158,000 - $257,000 Equity This role is eligible to participate in Cloudflare’s equity plan." We need to format nicely. Probably separate paragraphs. We should not repeat "Compensation Compensation". We'll just have a paragraph. Now Schedule: Travel expectation. Already included in responsibilities bullet but also we could have a Schedule section with "Travel as needed (expect :30%)". But we already have that bullet. Might be redundant. The instruction: prefer a few substantive sections over many thin ones. We could omit Schedule section and keep travel under Responsibilities. However we have travel also in Skills/Experience. Might be okay to not have separate Schedule. But we need to include Schedule heading only if posting has real specific content for it. The posting does mention travel expectation. Could be considered schedule. But we already have it under Responsibilities. Might be okay to not create Schedule heading to avoid thin section. However we need to decide. Given we already have Responsibilities with travel bullet, we can skip Schedule. Now we need to output only HTML fragment. Structure:About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
...
We need to ensure we don't include empty sections. Now we need to copy the text exactly, preserving details. Let's craft About the role paragraph exactly as given. Paragraph: "The Data Center Strategy team needs a site-selection manager who has closed NNN and wholesale leases at MW scale. You find the site, underwrite it, and get the paper signed. The binding constraint is usually power: available MW, interconnection, substation work, and when the site actually energizes. You also have to be right about land or campus control, fiber, water, flood and seismic, permitting, and latency onto Cloudflare’s network. The commercial work is NNN paper and the structures next to it: modified gross, FRI, wholesale dedicated-room, powered shell, build-to-suit, sale-leaseback, joint venture. Base rent, OpEx and tax passthroughs, escalators, work letters, landlord delivery, PUE treatment, delay credits, SLAs, ramp, expansion options, ROFR, exit and renewal. You build the pipeline (developers, brokers, wholesale operators, power developers, utilities), run technical diligence, and take a TCO / cost-per-MW / NPV pack to leadership for the capital ask. Several of these will be live at once, across markets. Legal, capacity planning, network strategy