Research Engineer / Performance Engineer, RL Distributed Systems

Anthropic · San Francisco, CA | New York City, NY | Seattle, WA · AI Research & Engineering · listed September 29, 2026

The shape of it

Seniority
Not stated
Where
Not stated
Stated pay
$500,000 – $850,000 USD
Requirements listed
6
Length
1,350 words

In the posting’s own words

As a Research Engineer on the Distributed Systems team within RL Engineering, you'll work on whatever part of that system is the current limit. That might be scheduling and placement, data movement between components, running large numbers of sandboxed environments, storage and checkpointing, networking, fault tolerance, autoscaling, or the observability that tells us what a run is actually doing. We're looking for generalists: engineers who can move between these layers, reason from first principles about a system they haven't seen before, and pick the problem that matters most rather than the one closest to their prior experience.

What it asks for · 6

  • Strong software engineering skills in Python and at least one systems language such as Rust, C++, or Go
  • Experience designing, building, and operating large-scale distributed systems in production
  • Deep understanding of distributed systems fundamentals, including consistency, coordination, consensus, failure modes, and recovery
  • Ability to reason quantitatively about throughput, latency, and resource costs across compute, memory, storage, and network
  • Experience debugging complex failures across many hosts and services, including failures you can't reproduce locally
  • Strong written communication, including design documents and incident writeups

Also a plus

  • Experience running ML training or inference infrastructure at scale
  • Experience across several layers of the stack, such as scheduling, storage, networking, and orchestration
  • Experience building schedulers, autoscalers, or resource management systems
  • Experience with container orchestration such as Kubernetes, and with sandboxed or virtualized code execution at scale
  • Experience with high-performance networking, RDMA, or collective communication libraries
  • Experience building observability or automated remediation for large fleets
  • Experience with async Python frameworks such as Trio or asyncio
  • Familiarity with reinforcement learning or large language model training workloads

What the job covers

  • Design, build, and operate the distributed systems that run RL at scale, across training, sampling, and environment execution
  • Find and remove whatever currently limits the system, whether it's scheduling, data movement, storage, networking, or coordination
  • Build fault tolerance into every layer: failure detection, isolation, and recovery that keep long-running jobs making progress without human intervention
  • Design resource management and autoscaling so that compute follows demand as a run's needs shift
  • Build observability that makes it possible to understand what a run is doing and why it slowed down, stalled, or produced unexpected results
  • Build automation that detects and remediates common problems, and design interfaces that let engineers and automated tools operate runs safely
  • Work with researchers and performance engineers to make sure systems changes preserve training correctness and don't introduce subtle nondeterminism
  • Remove classes of failure at their source through incident review, testing, and redesign, and write clear design documents for what you build

Tools and skills named

Cloud & infra
  • Distributed systems5×
  • Observability3×
  • Kubernetes
Models & research
  • Machine learning2×
  • Reinforcement learning2×
  • Inference
  • LLM
Languages
  • Python2×
  • C++
  • Go
  • Rust
Ways of working
  • Testing

Words the posting leans on

  • system16×
  • experience11×
  • run11×
  • failure9×
  • design8×
  • build7×
  • training7×
  • large6×
  • distributed systems5×
  • scale5×
  • compute4×
  • data4×
  • engineers4×
  • execution4×
  • networking4×
  • recovery4×

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 September 29, 2026 and last changed by Anthropic on September 29, 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.