Cluster Deployment Engineer

<div class="content-intro"><h2><strong>About Anthropic</strong></h2> <p>Anthropic’s mission is to create reliable, interpretable, and steerable AI systems. We want AI to be safe and beneficial for our users and for society as a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems.</p></div><h2><strong>About the role</strong></h2> <p>As a Cluster Deployment Engineer, you will own how large-scale AI compute clusters physically come together inside our datacenter fleet. You will set the deployment-engineering strategy for cluster build-out — how racks are organized into pods, halls, and sites; how compute, network, power, and cooling systems interface at the rack boundary; and how deployment scope flows cleanly from hardware specification to facility delivery to a running cluster. This role is focused on deployment engineering, not on datacenter network or systems design — your scope is making sure clusters land cleanly and predictably, not designing the fabrics or facilities themselves.</p> <p>This is a senior individual-contributor role with broad technical influence. You will work across hardware, networking, facilities, supply chain, and construction to ensure that every generation of accelerator we deploy lands in a datacenter that is ready for it — on schedule, at full density, and with every piece of required infrastructure accounted for. You will be the person who sees around corners: anticipating how next-generation rack designs will stress our facilities, where our deployment model will break at scale, and what needs to change now so that the next cluster turn-up is faster and more predictable than the last.</p> <p>You will operate at the intersection of engineering strategy and execution discipline, partnering with internal research and systems teams, external developers, engineering firms, and OEM partners to deliver cluster capacity at the speed the frontier demands.</p> <h2><strong>Responsibilities&nbsp;</strong></h2> <ul> <li> <p><strong>Own cluster-level deployment strategy</strong> — define how AI compute clusters are organized across the floor, how racks interconnect, and how cluster topology requirements translate into facility and deployment scope across a portfolio of sites.</p> </li> <li> <p><strong>Set rack interface standards</strong> spanning power, network, mechanical, thermal, and spatial domains, and ensure that every deployment includes the complete set of infrastructure required to bring a cluster online.</p> </li> <li> <p><strong>Drive multi-threaded cluster bring-up programs</strong> across hardware, networking, power, and cooling — owning plans, dependencies, and critical paths from hardware specification through energization and turn-up.</p> </li> <li> <p><strong>Partner with internal engineering teams</strong> — research, systems, networking, and hardware — to translate cluster requirements into deployable facility scope, and to derisk onboarding of new hardware platforms well ahead of delivery.</p> </li> <li> <p><strong>Lead external partner execution</strong> with developers, engineering firms, OEMs, and construction teams, driving technical reviews, deviation management, and handoffs that keep deployments on schedule and within specification.</p> </li> <li> <p><strong>Improve cluster turn-up reliability and repeatability</strong> — identify systemic gaps in deployment scope, tooling, and partner interfaces, and drive durable fixes that reduce time-to-serve for new capacity.</p> </li> <li> <p><strong>Define and track deployment KPIs</strong> — cluster readiness, schedule adherence, scope completeness, time-to-first-packet — and use historical trends to forecast risk and inform capacity planning.</p> </li> <li> <p><strong>Coordinate cross-functional readiness</strong> across supply chain, security, operations, and construction to ship production-ready compute capacity.</p> </li> <li> <p><strong>Provide crisp executive visibility</strong> on deployment progress, tradeoffs, and risks across a portfolio of concurrent cluster programs.</p> </li> <li> <p><strong>Design cluster interfaces for durability</strong> — define rack and cluster-level interfaces that remain robust across hardware generations, so that facility scope and deployment models do not need to be reinvented every time the underlying hardware changes.</p> </li> <li> <p><strong>Build cl