AI Infrastructure Operations, Demand Planning

Overview

About Anthropic 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.

What you'll do

• Capacity Engineering owns the data, tooling, and systems that let Anthropic plan, measure, and maximize utilization of that fleet: we partner on supply deals, wire telemetry from day zero, own the canonical capacity data layer, and build the planning and enforcement tools every research and product team relies on.
• This role sits in the Planning pillar, on the Demand Planning team, and works daily with research engineering, pretraining, inference, compute supply, finance, and external vendors.
• The job has two halves that feed each other.
• Upstream, you take the Demand Planning forecast and turn it into per-tranche requirements, shape, interconnect, region, supporting resources, date, and carry those into sourcing negotiations and data center build reviews so we contract for capacity we can actually use when we need it.
• Downstream, you own the integrated schedule and system of record for every tranche in flight, from contracted through reserved, ingested, in-cluster, healthy, and occupied, and you drive the owners of each hop to their dates.
• Every slip you see downstream becomes a contract-language fix, an automation, or a correction fed back to the forecast.
• What you'll do Turn the forecast into per-tranche requirements.
• Take the Demand Planning forecast plus direct input from research, pretraining, and inference planners, and convert it into concrete accelerator, interconnect, region, supporting-resource, and date requirements for each tranche.

Requirements

• Downstream, you own the integrated schedule and system of record for every tranche in flight, from contracted through reserved, ingested, in-cluster, healthy, and occupied, and you drive the owners of each hop to their dates.
• Every slip you see downstream becomes a contract-language fix, an automation, or a correction fed back to the forecast.

Skills