VP Energy & Site Selection

We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We need to parse the job posting. First, there is an intro paragraph about Crux AI. That's likely "About the role"? Actually "What You'll Do" is responsibilities. Then "SIGNALS OF SUCCESS" maybe not a standard heading; but we can treat as maybe "Responsibilities"? Actually "What You'll Do" is responsibilities. Then "SIGNALS OF SUCCESS" maybe not needed; but we could treat as "Responsibilities"? However we must not invent sections; we can include only those headings that have content. We have sections: "What You'll Do" (Responsibilities). Then "SIGNALS OF SUCCESS" (maybe not a standard heading; but could be considered "Responsibilities"? Actually it's expectations after certain time frames; could be considered "Responsibilities" or maybe "Qualifications"? It's more about success metrics. Not a standard heading; we could omit because not in list? The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings for section headings. It doesn't forbid other headings? It says use h3 for section headings (e.g. ...). Likely we should only use those headings. So we need to map content to those categories. We have "Experiences EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" which is qualifications/requirements/skills. We can split into Requirements (experience), Qualifications (maybe same), Skills (attributes). We'll need to decide. We have "Salary Range Information" which is Pay. We have "About Crux" which is Benefits? Actually it's benefits description: "We offer generous base, bonus and additional incentive based compensation Health, dental, and vision coverage...". That's Benefits. We have no explicit Pay besides salary range info. So we can include Pay section with that content. Schedule: "Hybrid schedule offering four days in-office collaboration paired with one remote workday for focused, individual work". That's Schedule. Now we need to produce sections only if they have real specific content. Let's extract content. About the role: maybe a brief summary? The intro paragraph: "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." That's about the company, not role. Could be "About the role"? Might be considered "About the role" (description of role?). But it's more about company. However we could still put as About the role? The instruction: do NOT repeat the job title as a heading. It didn't say we cannot have About the role. We can include if there is content. This paragraph describes the company and mission; could be considered About the role? Might be okay. But we also have "What You'll Do" which is responsibilities. We have "SIGNALS OF SUCCESS" maybe could be considered "Responsibilities" as well but we already have responsibilities. We have "Experiences EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" which includes experience, attributes, mindset. That's qualifications/skills. We have "Salary Range Information" for Pay. We have "About Crux" for Benefits. We have schedule line. Now we need to format as HTML: use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none visible. Now we need to decide what goes where. Let's extract responsibilities from "What You'll Do" paragraph: "Reporting to the Chief Development Officer, you will build Crux AI's powered campus pipeline, leading the origination, structuring, acquisition, and development of the sites that carry the platform to roughly 2 GW of annual delivery. You will own each opportunity from origination through infrastructure hold point, handing over campuses that are ready for vertical construction. Power is the binding constraint, so you will lead power origination and capacity planning while coordinating the wider infrastructure ecosystem around it, driving procurement and delivery for substations, transformers, switchgear, transmission and distribution upgrades, broadband, and the other long-lead assets that determine energization dates. You will build and hold the relationships this depends on across utilities, ISOs and RTOs, municipalities, and infrastructure partners, and structure development and acquisition strategies that preserve expansion optionality without sacrificing near-term capacity. You will convert opportunities into executable, bankable projects with clear accountability for schedule, feasibility, and site readiness - orchestrating utilities, municipalities, permitting authorities, infrastructure providers, and communities while identifying and mitigating risks across infrastructure delivery. That means installing governance and diligence rigorous enough that development assumptions reflect real infrastructure availability, procurement timelines, and execution constraints rather than optimistic scheduling. And you will build a lean development organization using AI, automation, and modern diligence tools to qualify opportunities faster, and building the operating processes that let a small team run a rapidly expanding portfolio." That's responsibilities. Now "SIGNALS OF SUCCESS" details after 60 days, 6 months, 1 year. Could be considered part of responsibilities or maybe "Qualifications"? But it's expectations; we could include as part of responsibilities as well, but we already have responsibilities section; we could add as a sub-list? However we must not invent headings; we could keep responsibilities and include that content as part of responsibilities (maybe as a separate paragraph). That's fine. Now "Experiences EXPERIENCES, ATTRIBUTES AND MINDSET THAT INDICATE A GOOD MATCH" includes: "Origination through campus readiness. Senior experience in data center, digital infrastructure, power, or infrastructure development, with personal ownership of advancing large-scale projects from origination all the way to campus readiness. Power markets and utility engagement. Strong command of power markets, interconnection, utility engagement, and grid dynamics — specifically in constrained or competitive environments where capacity is contested. Securing infrastructure, not procuring inputs. Proven ability to secure and coordinate the full set of critical infrastructure required to enable development, rather than sourcing individual components in isolation. Complex deal structuring. Track record identifying, structuring, and executing development opportunities that deliver scalable capacity, with fluency across land, permitting, entitlements, and stakeholder engagement. Long-lead dependency management. Experience managing long-lead infrastructure requirements and multiple interlocking dependencies inside complex development programs. Attributes Hands-on and credible. Engages utilities, developers, and infrastructure partners at real depth. Creative and resourceful in sourcing. Finds and acts on opportunities others overlook, and is comfortable with deals that are imperfect and time-sensitive. Decisive and pragmatic. Assesses risk quickly and moves in competitive markets without waiting for perfect information. Commercially minded. Balances speed, cost, scalability, and long-term flexibility in every development and infrastructure decision. Mindset Technology-enabled operator. Uses AI, automation, and modern diligence tools to qualify opportunities and accelerate decisions, and builds scalable process so a lean team can carry a large portfolio. Honest about schedule. Builds development assumptions that reflect real procurement timelines and execution constraints, and would rather deliver a hard date than an appealing one." We need to map to sections: Requirements, Qualifications, Skills. Could treat Requirements as the experience bullets, Qualifications as attributes, Skills as mindset? Or combine. We need to avoid thin sections; maybe combine into one "Requirements" section with all bullets. But we need to follow instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using multiple of those. We can include Requirements, Qualifications, Skills each with content. We need to ensure we don't create sections with filler like "commensurate with experience". We have real content. Thus we can have: - About the role: company intro paragraph. - Responsibilities: "What You'll Do" plus SIGNALS OF SUCCESS maybe. - Requirements: experience bullets (Origination through campus readiness, Power markets..., Securing infrastructure..., Complex deal structuring..., Long-lead dependency management.) - Qualifications: attributes bullets (Hands-on..., Creative..., Decisive..., Commercially minded.) - Skills: mindset bullets (Technology-enabled operator..., Honest about schedule.) - Benefits: About Crux paragraph. - Pay: Salary Range Information paragraph. - Schedule: hybrid schedule sentence. Now we need to ensure we don't repeat content. Let's extract each. About the role: The intro paragraph (first paragraph). We'll keep as is. Responsibilities: The "What You'll Do" paragraph plus the SIGNALS OF SUCCESS details (maybe as a list). We'll keep as prose; could break into paragraphs. We need to preserve all substantive information; we can include the SIGNALS OF SUCCESS as a separate paragraph under responsibilities. Now Requirements: list of experience bullets. We'll make

  • for each. Qualifications: list of attributes bullets. Skills: list of mindset bullets. Benefits: About Crux paragraph. Pay: Salary Range Information paragraph. Schedule: hybrid schedule sentence. Now we need to ensure we don't include any boilerplate like "About Crux We offer generous base..." etc. That's fine. Now produce HTML fragment. We'll need to escape any HTML special characters? Not needed. Let's craft. First, About the role:

    About the role

    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.

    Second, Responsibilities:

    Responsibilities

    Reporting to the Chief Development Officer, you will build Crux AI's powered campus pipeline, leading the origination, structuring, acquisition, and development of the sites that carry the platform to roughly 2 GW of annual delivery. You will own each opportunity from origination through infrastructure hold point, handing over campuses that are ready for vertical construction. Power is the binding constraint, so you will lead power origination and capacity planning while coordinating the wider infrastructure ecosystem around it, driving procurement and delivery for substations, transformers, switchgear, transmission and distribution upgrades, broadband, and the other long-lead assets that determine energization dates. You will build and hold the relationships this depends on across utilities, ISOs and RTOs, municipalities, and infrastructure partners, and structure development and acquisition strategies that preserve expansion optionality without sacrificing near-term capacity. You will convert opportunities into executable, bankable projects with clear accountability for schedule, feasibility, and site readiness - orchestrating utilities, municipalities, permitting authorities, infrastructure providers, and communities while identifying and mitigating risks across infrastructure delivery. That means installing governance and diligence rigorous enough that development