AI Infrastructure Operations, Demand Planning

Anthropic · San Francisco, CA | New York City, NY · Software Engineering - Infrastructure · listed August 11, 2026

The shape of it

Seniority
Not stated
Where
Hybrid
Stated pay
$320,000 – $405,000 USD
Requirements listed
1
Length
1,258 words

In the posting’s own words

You own the tranches. 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 it asks for · 1

  • A degree in a technical field or an equivalent engineering track record.

Also a plus

  • Reserved-capacity onboarding, private offers, or capacity commitments with cloud or neocloud providers.
  • Enough demand-planning exposure to challenge a forecast, translate it into per-tranche requirements, and feed delivery variance back into it.
  • Data center or colocation delivery: power and space planning, network turn-up, site acceptance, vendor management.
  • Accelerator health and burn-in, collective-communications sanity testing, or fleet-health SLOs — and a rigorous definition of "healthy."
  • Systems of record or lifecycle services for infrastructure assets.
  • Onboarding a new hardware generation into an existing scheduler and observability stack.

What the job covers

  • 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. Represent those in sourcing negotiations and data center build reviews, including which contractual terms actually move delivery dates.
  • Qualify tranches for deliverability before signature. The Capacity Planner signs fit-to-forecast; you sign whether the shape can land schedulable, healthy, and instrumented in that region on that date, with storage, egress, identity in place.
  • Close the delivery loop. Track forecast-versus-delivered on shape, region, and timing for every tranche; publish the variance; and feed it back to Demand Planning and into the next contract.
  • Own the bring-up system of record. Define the canonical contract-to-occupied state machine with explicit entry and exit criteria per stage, and make it a first-class object in the capacity data layer so every downstream tool sees in-flight capacity, not only what has landed.
  • Run a portfolio of bring-ups in parallel — new cloud regions, on-prem sites, neocloud blocks — with one integrated schedule spanning provider milestones, cluster creation, network turn-up, storage readiness, health burn-in, and first-workload landing.
  • Drive readiness automation: All capacity systems are fully integrated for all new capacity, from contracted through ingested, automated and scaled.
  • Instrument and publish the numbers that matter — time-to-occupied and paid-idle dollars per tranche — with executive-level reporting on status, tradeoffs, and risk across the portfolio.

Degree language

  • A degree in a technical field or an equivalent engineering track record.

Tools and skills named

Languages
  • Python
  • SQL
Models & research
  • Inference2×
Cloud & infra
  • Observability
Frameworks
  • Node.js
Operations & finance
  • Vendor management
Ways of working
  • Testing

Words the posting leans on

  • capacity9×
  • planning8×
  • data6×
  • region6×
  • systems6×
  • tranche6×
  • accelerator5×
  • date5×
  • every5×
  • forecast5×
  • build4×
  • cloud4×
  • delivery4×
  • demand planning4×
  • record4×
  • back3×

Counted from the posting after the mission statement and the legal notices are set aside. The ones near the top are the ones a screener is looking for.

The posting, your resume, and the gaps between them. One click loads all three.

More open at Anthropic

every open role at Anthropic

How this page was made

An automated read of a public job posting, fetched August 24, 2026 and last changed by Anthropic on August 21, 2026. Every list above is pulled from the posting’s own sentences — nothing rewritten, nothing added, no judgment about the role or the company. Counts and seniority are read off the text by rule, so they can be wrong where the posting is unusual. The original is the only thing that binds. Openings close without warning; check the source before spending an evening on it.