Staff Software Engineer, Developer Productivity (CI/CD) - Claude Code
AnthropicAbout 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.
About the role
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.
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.
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.
Key responsibilities
-
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
-
Drive down and defend "time from push to healthy in prod" as a core engineering metric
-
Design and tune AI-assisted code review so confidence-to-land scales with PR volume
-
Build the deploy and release path — canary, progressive rollout, health checks, automated rollback — in partnership with the platform teams who own the underlying substrate
-
Improve test reliability by quarantining, root-causing, and retiring intermittent failures
-
Shape CI and repository topology (build graph, test targeting, scope boundaries) to match how the company actually ships
-
Partner with platform, delivery infrastructure, and security te