Staff Software Engineer, Developer Productivity (CI/CD) - Claude Code

About this role

<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 class="heading">About the role</h2> <p>Every engineer at Anthropic depends on the path from pull request to production. The Developer Productivity team owns that path end to end — review automation, CI, the merge queue, the deploy pipeline, and the policy that gates each step. These pieces exist today; the opportunity is to integrate them into a single fast, predictable system that scales with the volume of code shipping into Claude and our research infrastructure.</p> <p> </p> <p>In this role, you'll be responsible for making "time from push to healthy in production" a metric the whole company can rely on. You'll shape the CI and repository topology that best serves our velocity, build AI-assisted review that keeps confidence high as PR volume grows, and partner closely with platform, security, and delivery infrastructure teams on the substrate underneath. This is a tech-lead-scope IC role with broad cross-team influence — you'll represent Developer Productivity in org-wide pipeline decisions and help other teams adopt the standards you set.</p> <p> </p> <p>We use Claude heavily in our own development workflows, and this team is at the center of that: agentic coding is both how we work and part of what you'll be building.</p> <h2 class="heading">Key responsibilities</h2> <ul> <li> <p>Own the build, test, merge, and deploy pipeline end to end — what runs on each PR, what auto-approves, what gates merge, and how a change progresses to running healthy in production</p> </li> <li> <p>Drive down and defend "time from push to healthy in prod" as a core engineering metric</p> </li> <li> <p>Design and tune AI-assisted code review so confidence-to-land scales with PR volume</p> </li> <li> <p>Build the deploy and release path — canary, progressive rollout, health checks, automated rollback — in partnership with the platform teams who own the underlying substrate</p> </li> <li> <p>Improve test reliability by quarantining, root-causing, and retiring intermittent failures</p> </li> <li> <p>Shape CI and repository topology (build graph, test targeting, scope boundaries) to match how the company actually ships</p> </li> <li> <p>Partner with platform, delivery infrastructure, and security teams, and represent Developer Productivity in cross-org pipeline decisions</p> </li> <li> <p>Design processes (postmortem review, incident response, on-call) that help the team operate reliably and never fail the same way twice</p> </li> </ul> <h2 class="heading">Minimum qualifications</h2> <ul> <li> <p>Significant backend or developer-infrastructure engineering experience, with hands-on responsibility for a high-leverage CI/CD, merge queue, or land pipeline at scale</p> </li> <li> <p>Proficiency in Python and at least one statically-typed systems language (e.g., Go or Rust)</p> </li> <li> <p>Experience operating CI/CD or release systems through production incidents, including writing postmortems and driving remediations</p> </li> <li> <p>Demonstrated ability to work across team boundaries — building consensus with platform, security, and product engineering stakeholders</p> </li> <li> <p>Comfort using AI coding tools as a daily part of your workflow, with informed opinions on where they provide leverage</p> </li> </ul> <h2 class="heading">Preferred qualifications</h2> <ul> <li> <p>7+ years of backend or developer-infrastructure experience</p> </li> <li> <p>Experience with Bazel or similar build-graph / test-targeting systems at monorepo scale</p> </li> <li> <p>Experience with progressive delivery or release engineering at scale (canary analysis, automated rollback, health-gated promotion)</p> </li> <li> <p>A track record of leading — or making the well-reasoned case against — a repo split, monorepo extraction, or comparable scope-boundary migration</p> </li> <li> <p>A history of authoring engineering policy or paved-path tooling that other teams adopted voluntarily</p> </li> <li> <p>Familiarity with Kubernetes, Buildkite, GitHub Actions, or comparable CI/deploy substrates</p> </li> <li> <p>Interest in the safe and beneficial development of AI</p> </li> </ul> <h2 class="heading">Representative projects</h2> <ul> <li> <p>Reducing p50 merge-to-production time by re-architecting the merge queue and test selection strategy</p> </li> <li> <p>Building an AI-assisted review layer that auto-approves low-risk changes and routes high-risk ones to the right reviewers</p> </li> <li> <p>Designing a flaky-test quarantine and burndown system that returned CI signal to >99% reliability</p> </li> <li> <p>Standing up canary and progressive rollout for a service fleet, with automated rollback on health…