Director, Platform Engineering (EMEA)

Job description

About Volta Volta is the category-defining, fully vertically integrated AI infrastructure platform – from capital to clusters to software, under a founder-led enterprise. Our mission is The Utility of Compute™: AI infrastructure as dependable and available as electricity, for every organization that needs it. Launched with a $10B strategic partnership with one of the leading frontier AI labs, a Series A led by Andreessen Horowitz, and a $5B AI Infrastructure Fund, Volta is building the infrastructure layer of the AI era from the ground up. We are 100+ people across London, Palo Alto, and New York, with rapid growth expectations to hundreds. About The Role Volta builds and operates large scale GPU compute infrastructure for frontier AI customers. The software that turns racks of GPUs into a usable platform is its own product. You will lead Platform Engineering across EMEA and act as deputy to the VP, Platform Engineering, who is based in Palo Alto. You own the European teams and their delivery, and you partner with the VP closely enough that the two of you run one organization across two continents. This is a building role. Volta already has platform engineers in Europe, today managed from the US, and bringing them into a local structure is your first priority before growing the region into several teams. It is a software leadership role, but not an abstracted one. Our platform sits directly on GPU hardware, fabric, and physical sites, and it only works if it stays coherent with them. What You Will Be Doing Lead the EMEA platform engineering teams and own their delivery against the platform roadmap you set with the VP. Bring the platform engineers already in Europe into the EMEA structure in a way that keeps continuity for both the people and the work. Grow the region across multiple capability teams, build the team lead layer beneath you, and own hiring in region without lowering the bar. Act as the VP's deputy: represent Platform Engineering in EMEA, step in when they are unavailable, and keep the two regions aligned so the platform stays coherent. Stay hands-on enough to lead architecture and design reviews and to call the right answer when a technical debate needs one. Own reliability and operational quality for what the region ships, including on-call practice, incident response, and closing structural gaps after incidents. Own the boundary between the…