Head of Strategic Accounts

We need to output HTML fragment with sections: About the role? Actually the posting includes "Role Summary", "Key Responsibilities", "Skills & Experience", "Career Trajectory", "Location & Reporting", "Employment Basis", "Diversity". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we should map headings accordingly. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? It says e.g., meaning examples. We should use appropriate headings based on content. Likely we need sections: About the role (role summary), Responsibilities (key responsibilities), Skills (skills & experience), Qualifications maybe not separate, Career Trajectory maybe part of Skills? Location & Reporting maybe not needed? Employment Basis maybe not needed? Diversity maybe not needed? We should only include sections when posting has real, specific content. We have content for Role Summary, Key Responsibilities, Skills & Experience, Career Trajectory, Location & Reporting, Employment Basis, Diversity. However we should avoid boilerplate like Diversity statement? It's not boilerplate? It's a diversity statement; maybe we should drop as it's boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Diversity statement could be considered EEO boilerplate. Likely drop Diversity. Employment Basis maybe not needed? It's just "Full-time". Could be considered minor metadata; we could fold into a short

or drop. Location & Reporting maybe also minor metadata; we could include as a short paragraph under a heading? But we should not create headings for minor metadata. Probably better to include Location & Reporting as a short

after role summary? But we need to follow rule: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections: About the role (role summary), Responsibilities (key responsibilities), Skills (skills & experience). Possibly also Qualifications? But we have skills & experience includes qualifications. Could combine. Career Trajectory maybe could be part of Skills? But it's separate content about progression; maybe we can include as a separate section "Career Progression" but not in list of allowed headings? The instruction says use those as examples, not strict list. So we can create headings that make sense. However they said "Prefer a few substantive sections over many thin ones." So maybe combine Career Trajectory into Skills & Experience? Or keep as separate if substantive. It's a few paragraphs about senior IC then director. That's substantive. Could be its own section. We also need to use

• for any list of duties/requirements/benefits. Responsibilities is a list; we should output
  • each responsibility. Skills & Experience is also a list? It's bullet-like sentences but not explicitly bullet list. Could treat as
    • . Career Trajectory is also bullet-like? It's two bullet points. Could treat as list. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from role summary, responsibilities, skills & experience, career trajectory, location & reporting, employment basis maybe. We must not repeat job title as heading. The job title is "Strategic Account Lead". Not to repeat. We must not put Job ID/requisition numbers as headings. We must output ONLY HTML fragment, no /, no markdown fences. Let's extract content. Role Summary paragraph: "Firmus is executing one of the most ambitious AI infrastructure build-outs in the world — creating entirely new markets for sovereign AI compute, and scaling to become one of the most prolific AI infrastructure companies globally. The Strategic Account Lead is the single accountable owner for Firmus’s largest and most strategic GPU capacity relationships .This is a Director-level role that will begin as a Senior Individual Contributor, with the mandate to prove out account ownership and delivery execution before scaling into a team-building Director position. This is a commercial leadership role spanning account ownership, capacity commercialisation, and cross-functional delivery orchestration. Accounts are supported by a dedicated coverage pod — Solution Architecture, Customer Success, Technical Program Management, and Engineering — typically shared across two accounts today, with a path to a fully dedicated pod per account as an account’s scale and requirements warrant it — as already in place for Meta and Nvidia, these accounts an a exception will both report directly into the Vice President, North America. You will translate customer AI compute roadmaps into structured, multi-year Gigascale GPU capacity commitments, working closely with capacity planning, network engineering, and delivery teams to ensure every commitment is met on schedule. You will own deal structuring and negotiation for large, complex contracts, including pricing, terms, delivery milestones, and expansion rights, while identifying and progressing growth opportunities within existing accounts as customer compute needs scale. The role is executive-facing with strong technical fluency, focused on capacity planning, GPU deployment timelines, networking architecture, and power and data centre constraints. You will act as the primary point of contact for Firmus’s most important customers, coordinating closely with engineering, finance, and legal to protect and grow these relationships. This position is ideal for someone who thrives on owning complex, high-stakes commercial relationships, building deep executive trust, and operating with significant autonomy in a fast-scaling environment — with the ambition to build and lead a team as the strategic accounts function matures." Key Responsibilities list (each bullet): - Own end-to-end account leadership for Firmus’s largest GPU capacity customers, acting as the primary commercial point of contact and executive-level relationship owner. - Translate customer AI compute roadmaps into structured, multi-year Gigascale GPU capacity commitments, working closely with capacity planning and network engineering teams. - Lead deal structuring and negotiation for large, complex, multi-hundred-million to billion-dollar contracts, including pricing, terms, delivery milestones, and expansion rights. - Own the executive governance cadence for each account — running quarterly and executive business reviews with customer and Firmus leadership — to keep commitments, performance, and escalations visible at the highest level. - Own end-to-end delivery outcomes for your accounts, leading a dedicated coverage pod — Solution Architecture, Customer Success, Technical Program Management, and Engineering (SDI/Network/Platform) — and coordinating cross-functionally with finance, legal, and executive leadership to ensure customer commitments are met on schedule and risks are surfaced early. - Own the customer feedback loop into Firmus engineering — capturing technical issues, capacity requirements, and roadmap requests from your accounts and translating them into clear input for engineering and product priorities. - Drive the evolution of account coverage from shared pods (currently two accounts per pod) toward dedicated, single-customer pods as individual account requirements and scale justify a fully dedicated team — following the model already established for Meta and Nvidia, which report directly into the Vice President, North America. - Identify and execute account growth opportunities as customer compute needs scale, while maintaining clear executive reporting on strategic account health, pipeline, capacity utilisation, and risk. Skills & Experience list (bullet-like): - 10 + years in strategic account management, enterprise/complex sales, or commercial leadership in cloud infrastructure, data centre, semiconductor, or AI compute markets. - Direct experience selling, negotiating, or managing large-scale GPU/compute capacity contracts, ideally with a hyperscaler, neocloud, or AI infrastructure background. - Demonstrated ability to manage $500M+ commercial relationships, ideally with exposure to Billion $ + scale accounts. - Strong technical fluency in GPU infrastructure, able to speak credibly to customers on capacity planning, deployment timelines, networking architecture, and power and data centre constraints. - Track record of operating with significant autonomy in ambiguous, high-growth environments. - Comfort operating as an individual contributor initially, with the ambition and capability to build and lead a team as the function matures. Career Trajectory: - Senior IC : direct ownership of multiple flagship strategic accounts, proving commercial and delivery execution. - The 1st podDirector (as book of business scales): expanded account portfolio, formal team-building mandate, and elevated executive visibility across Firmus leadership. Location & Reporting: - Location: San Francisco Bay Area, California, USA - Reporting to the Vice President, North America Employment Basis: - Full-time Diversity statement we may drop. We need to decide sections. Potential sections:

      About the role

      with role summary paragraph(s). Could be multiple paragraphs but we can combine into one

      .

      Responsibilities

      with
      • each.

        Skills & Experience

        with
        • each.

          Career Trajectory

          with
          • each.

            Location & Reporting

            maybe as

            (since not a list). Could be

            Location: San Francisco Bay Area, California, USA. Reporting to the Vice President, North America.

            Employment Basis maybe also

            Employment Basis: Full-time.

            but could be folded into location paragraph. We should not create Pay/Benefits/Schedule sections because not present. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive information. Ensure we didn't miss any details: The role summary includes mention "as already in place for Meta and Nvidia, these accounts an a exception will both report directly into the Vice President, North America." There's a typo "an a exception". We'll keep as is. Also mention "Accounts are supported by a dedicated coverage pod — Solution Architecture, Customer Success, Technical Program Management, and Engineering — typically shared across two accounts today, with a path to a fully dedicated pod per account as an account’s scale and requirements warrant it — as already in place for Meta and Nvidia, these accounts an a exception will both report directly into the Vice President, North America." We'll keep. In responsibilities bullet about executive governance cadence: "running quarterly and executive business reviews with customer and Firmus leadership". Keep. In responsibilities bullet about leading a dedicated coverage pod: includes "(SDI/Network/Platform)". Keep. In responsibilities bullet about driving evolution: "following the model already established for Meta and Nvidia, which report directly into the Vice President, North America." Keep. Skills & Experience bullet: "10 + years". Keep. Skills & Experience bullet: "Direct experience selling, negotiating, or managing large-scale GPU/compute capacity contracts, ideally with a hyperscaler, neocloud, or AI infrastructure background." Keep. Skills & Experience bullet: "Demonstrated ability to manage $500M+ commercial relationships, ideally with exposure to Billion $ + scale accounts." Keep. Skills & Experience bullet: "Strong technical fluency in GPU infrastructure, able to speak credibly to customers on capacity planning, deployment timelines, networking architecture, and power and data centre constraints." Keep. Skills & Experience bullet: "Track record of operating with significant autonomy in ambiguous, high-growth environments." Keep. Skills & Experience bullet: "Comfort operating as an individual contributor initially, with the ambition and capability to build and lead a team as the function matures." Keep. Career Trajectory bullets: "Senior IC : direct ownership of multiple flagship strategic accounts, proving commercial and delivery execution." Keep. "The 1st podDirector (as book of business scales): expanded account portfolio, formal team-building mandate, and elevated executive visibility across Firmus leadership." Keep. Location & Reporting: "Location: San Francisco Bay Area, California, USA" and "Reporting to the Vice President, North America". Keep. Employment Basis: "Full-time". Keep. Now produce HTML. We'll wrap sections in maybe not needed. Just output headings and content. We'll do:

            About the role

            ...role summary...

            Responsibilities

            • ...
            ...

            Skills & Experience