Head of Infrastructure scope at a GPU cloud

At an early GPU cloud, the job is getting delivered hardware burned in, scheduled and billable. At growth stage it is hiring the platform, SRE and networking leads. At scale it is capacity planning against power and supply, plus the unit economics of the fleet.

Someone who fits one stage may be a poor fit for another. An operator who built a fleet from empty racks may not want to run budget models, and a platform executive from a large cloud may never have owned an RMA queue.

• ●Early stage: fleet operations, deployment, first scheduling and telemetry
• ●Growth stage: org building across platform, SRE, networking and MLOps
• ●Scale stage: capacity planning, power-constrained growth, unit economics
• ●Every stage: credibility with both hardware operations and software teams

There are few candidates and you can name them: infrastructure leaders at GPU clouds and neoclouds, hyperscaler capacity and fleet teams, federal lab computing facilities, and AI labs that built their own clusters. Most are not job hunting, so the outreach has to describe a specific scope they would want to own.

• ●Writing the role as 'everything infrastructure' with no priority order, which tells candidates the company has not decided what it needs
• ●Competing with model labs on cash instead of ownership and hardware access
• ●Running interviews without a technical interviewer the candidate respects

Senior infrastructure candidates judge the company by who is on the panel.