Director, LPS Development

We need to output HTML fragment with sections: About the role (maybe "About the role" heading), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. From posting: - About the role: The first paragraph: "We are seeking a senior leader to drive NVIDIA’s Land, Power, Shell (LPS) strategy, enabling rapid scale-out of our global data center footprint. This role sits at the intersection of site acquisition, power strategy, and shell delivery, translating complex land, utility, and permitting realities into executable data center programs. The ideal candidate brings hands-on experience with large-scale infrastructure, powered land and shell developments, and the broader data center ecosystem. Bringing to bear deep field exposure and strong external relationships, you will help NVIDIA secure, structure, and deliver LPS assets that unlock next-generation AI capacity!" This is prose. - Responsibilities: The bullet list under "What You Will Be Doing". Items: Own end-to-end LPS site strategy across targeted regions, from early scouting and feasibility through site control and shell delivery.; Lead evaluation of complex land and power opportunities, including transmission/distribution constraints, interconnection timelines, and long-term scalability of each site.; Partner with data center developers, utilities, architects, and construction teams to build and complete powered shell programs aligned with NVIDIA’s technical and capacity requirements.; Navigate permitting, zoning, and local collaborator dynamics to de-risk timelines and accelerate path to power and build-ready status.; Develop and maintain strong relationships across the data center ecosystem (utilities, ISPs, developers, operators, and local partners) to improve NVIDIA’s leverage and deal flow.; Provide clear, data-backed recommendations to internal leadership on site prioritization, tradeoffs, and investment decisions for LPS assets. - Requirements: The "What We Need To See" section includes: Bachelors Degree within a relevant area or equivalent experience in practice.; 15+ overall years of experience in land, power, and data center or large-scale infrastructure development dedicated to hardware and physical systems, with direct experience in site strategy and execution.; 7+ years of experience in building, training and managing teams.; Practical understanding of power procurement and delivery, permitting, and the physical realities of complex data center sites (access, easements, grid constraints, cooling implications).; Ability to engage credibly with data center builders, utilities, site developers, and local authorities, translating technical and commercial requirements into aligned execution plans.; Experience with architecture, engineering, or construction for critical facilities is highly valued. - Qualifications: Might be similar to requirements; but we can treat "What We Need To See" as Requirements. Could also have Qualifications separate but not needed. The posting also has "Ways To Stand Out From The Crowd": Proven track record operating in fast-growing, ambiguous environments and influencing cross-functional teams and external partners.; Strong communication skills, with the ability to “pressure-test” assumptions in the field and bring back clear insights to NVIDIA’s infrastructure and leadership teams. That could be Skills. - Benefits: The posting mentions "You will also be eligible for equity and benefits." Not specific benefits listed. So we cannot create Benefits section because no specific benefits listed. The rule: never create Benefits unless posting actually states them. It says eligible for equity and benefits but not specifics. Likely we should not create Benefits section. - Pay: The posting includes cash compensation details: "Your cash compensation will be determined based on your location, experience and the pay of employees in similar positions with 85% paid through base salary and 15% variable compensation. The cash compensation range is 296,000 USD - 448,500 USD." That's specific pay range. So we can include Pay section with that info. - Schedule: Not mentioned (Full time is given but that's time type; but schedule details like hours not given). The rule: only include Schedule if posting actually states them. It says Time Type Full time. That's schedule info? Might be considered schedule. However they said "Time Type Full time". Could be considered schedule. But they said "do not put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Time Type is metadata; could be included in a short paragraph. But we could also include Schedule section with "Full time". However they said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Full time is specific. So we could include Schedule section with "Full time". However they also said "Prefer a few substantive sections over many thin ones." Might be okay to include Schedule. But we need to decide: Should we include Schedule? The posting includes "Time Type Full time". That's a schedule detail. I'd include Schedule section with a

Full time

. However they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Time Type is metadata similar to Job ID. So maybe we should fold it into a short

rather than a heading. The rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we could include a short paragraph at top with metadata: Job Requisition ID JR2025663, Job Category Sales, Time Type Full time. But they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. They didn't say to remove metadata like Job ID, but they said not to put them as headings. So we could include a short paragraph with that info. Thus final HTML: maybe start with a

containing metadata: "Job Requisition ID JR2025663 | Job Category Sales | Time Type Full time". Then sections: About the role (

About the role

...)

, Responsibilities (

Responsibilities

...), Requirements (

Requirements

...), Skills (

Skills

...), Pay (

Pay

...)

. No Benefits, Qualifications, Schedule. Check if we need Qualifications separate: Could combine Requirements and Qualifications but we have Requirements. The posting also has "What We Need To See" which is requirements. Could also treat "Ways To Stand Out From The Crowd" as Skills. Good. Now ensure we preserve all substantive information: The About the role paragraph includes all sentences. Responsibilities list includes all six items. Requirements list includes all six bullet points. Skills list includes two items. Pay includes the compensation details. We must not include boilerplate like "NVIDIA is widely considered to be one of the technology world’s most desirable employers..." etc. That's not substantive? It's fluff but maybe considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The fluff about NVIDIA being desirable employer maybe not boilerplate but could be considered fluff. However it's substantive? It's more marketing. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The fluff about NVIDIA being desirable employer is not essential to job duties but is still part of posting. However it's not a list; it's prose. Could keep it in About the role? But we already have About the role paragraph from earlier. The fluff appears later: "NVIDIA is widely considered to be one of the technology world’s most desirable employers. We have some of the most forward-thinking and hardworking people in the world working for us. If you're creative and autonomous, we want to hear from you!" That's more like a selling point. Could be considered part of About the role? Might be okay to include in About the role section as additional prose. However the instruction says "Prefer a few substantive sections over many thin ones." Adding that fluff may be okay. But we need to decide: Should we include that fluff? It's not boilerplate like EEO; it's more marketing. I'd include it in About the role after the initial paragraph. Thus About the role paragraph: combine the two paragraphs: first about role, second about NVIDIA being desirable employer and creative autonomous. Let's craft: About the role: "We are seeking a senior leader to drive NVIDIA’s Land, Power, Shell (LPS) strategy, enabling rapid scale-out of our global data center footprint. This role sits at the intersection of site acquisition, power strategy, and shell delivery, translating complex land, utility, and permitting realities into executable data center programs. The ideal candidate brings hands-on experience with large-scale infrastructure, powered land and shell developments, and the broader data center ecosystem. Bringing to bear deep field exposure and strong external relationships, you will help NVIDIA secure, structure, and deliver LPS assets that unlock next-generation AI capacity! NVIDIA is widely considered to be one of the technology world’s most desirable employers. We have some of the most forward-thinking and hardworking people in the world working for us. If you're creative and autonomous, we want to hear from you!" Now Responsibilities as list. Requirements as list. Skills as list: "Proven track record operating in fast-growing, ambiguous environments and influencing cross-functional teams and external partners." and "Strong communication skills, with the ability to “pressure-test” assumptions in the field and bring back clear insights to NVIDIA’s infrastructure and leadership teams" Pay: "Your cash compensation will be determined based on your location, experience and the pay of employees in similar positions with 85% paid through base salary and 15% variable compensation. The cash compensation range is 296,000 USD - 448,500 USD. You will also be eligible for equity and benefits." We could also mention equity and benefits but not specifics. Now metadata paragraph: maybe at top:

Job Requisition ID JR2025663 | Job Category Sales | Time Type Full time

Now output HTML fragment. Check for any duplicated lines: none. Make sure not to include any headings for empty sections. Thus final HTML:

Job Requisition ID JR2025663 | Job Category Sales | Time Type Full time

About the role

We are seeking a senior leader to drive NVIDIA’s Land, Power, Shell (LPS) strategy, enabling rapid scale-out of our global data center footprint. This role sits at the intersection of site acquisition, power strategy, and shell delivery, translating complex land, utility, and permitting realities into executable data center programs. The ideal candidate brings hands-on experience with large-scale infrastructure, powered land and shell developments, and the broader data center ecosystem. Bringing to bear deep field exposure and strong external relationships, you will help NVIDIA secure, structure, and deliver LPS assets that unlock next-generation AI capacity! NVIDIA is widely considered to be one of the technology world’s most desirable employers. We have some of the most forward-thinking and hardworking people in the world working for us. If you're creative and autonomous, we want to hear from you!

Responsibilities

• Own end-to-end LPS site strategy across targeted regions, from early scouting and feasibility through site control and shell delivery.
• Lead evaluation of complex land and power opportunities, including transmission/distribution constraints, interconnection timelines, and long-term scalability of each site.
• Partner with data center developers, utilities, architects, and construction teams to build and complete powered shell programs aligned with NVIDIA’s technical and capacity requirements.
• Navigate permitting, zoning, and local collaborator dynamics to de-risk timelines and accelerate path to power and build-ready status.
• Develop and maintain strong relationships across the data center ecosystem (utilities, ISPs, developers, operators, and local partners) to improve NVIDIA’s