Staff+ Software Engineer, ML Sampling Path

Anthropic · San Francisco, CA · Safeguards (Trust & Safety) · listed September 9, 2026

The shape of it

Seniority
Staff
Experience asked
8+ years
Where
Hybrid
Stated pay
$320,000 – $485,000 USD
Requirements listed
4
Length
969 words

In the posting’s own words

The Safeguards ML Sampling Path team builds and operates the production services that power Claude's safety systems. These services sit on the token generation path across every platform Claude runs on: every request must pass through them, and each millisecond of added latency is wait time for our users. You’ll keep p99 latency flat as traffic grows, build for robustness as dependencies time out or partially fail, and ship changes safely to a system that cannot go down.

What it asks for · 4

  • Have designed, built, and operated high QPS systems at global scale, and were accountable for them in production: incident response, outages, and postmortem-driven remediation.
  • Have a strong foundation in distributed systems: replication, consistency tradeoffs, failure modes, and SLO management under load.
  • Design systems for graceful degradation: you plan for a slow dependency, a dropped stream, or a half-rolled-out deploy before it happens, and build so the system degrades predictably instead of failing.
  • Have successfully shipped broad or all-encompassing changes to mission critical systems (e.g., database migrations, interface changes, rewrites).

Also a plus

  • 8+ years of industry software engineering experience.
  • Familiarity with LLM inference systems and transformer-based models (not required, but a plus).

What the job covers

  • Design, build, and operate the backend systems that process every token on the generation path for Claude requests, including the streaming contract with the API and inference engines.
  • Own latency and reliability end to end: define and maintain SLOs and error budgets for added latency, time-to-first-token, and availability, and lead incident response and postmortem follow-through.
  • Ship changes to the hot path rapidly but safely — canaried and gradual rollouts, error budget and latency gating, fast rollbacks — and drive per-token performance: chase tail latency and keep cost flat as traffic, models, and checks per request grow.
  • Set technical direction for the sampling path: lead design reviews, make latency, reliability, and cost trade-off calls with the inference and research teams, mentor engineers, and raise the operational bar for the wider Safeguards organization.

Tools and skills named

Models & research
  • Inference3×
  • LLM
  • Machine learning
Cloud & infra
  • Distributed systems
Product & design
  • Design systems

Words the posting leans on

  • systems9×
  • latency7×
  • path5×
  • build4×
  • changes4×
  • claude3×
  • design3×
  • every3×
  • inference3×
  • request3×
  • added latency2×
  • budget2×
  • cost2×
  • end2×
  • error2×
  • flat traffic2×

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