Staff Software Engineer, Billing Platform

About 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

Anthropic exists to ensure the world safely navigates the transition through transformative AI. That work is funded by commercial revenue — and every dollar of it runs through Billing Platform. We build and operate the infrastructure that turns product usage into revenue across everything Anthropic ships: Claude.ai , the Developer Platform, Claude Code, and whatever comes next. The faster we can price it, charge for it, and account for it correctly, the faster Anthropic can fund the mission.

We’re looking for a software engineer to join Billing. Depending on where you land, you might be building the integration contracts product teams plug into so they can launch a paid SKU without becoming billing experts, automating the quote-to-cash lifecycle so enterprise deals don’t bottleneck on manual ops, or building the reconciliation and data foundations that keep every revenue number trustworthy at audit time. This is production-critical infrastructure where correctness is non-negotiable — a rounding error here is a revenue discrepancy somewhere else — and you’ll work closely with Finance, Product, Sales, and Accounting to build systems that scale with the business.

What you’ll do

Design and ship billing capabilities end to end — pricing primitives, payment flows, contract and entitlement models, revenue data pipelines — depending on the surface area you own.

Build for correctness first. Billing data is financial data; you’ll develop the instincts for where idempotency, reconciliation, and audit trails matter and where they don’t.

Own the interfaces. Whether it’s the billing API a product team integrates against or the revenue dataset Finance closes the books on, you’ll design contracts that hide the complexity and hold up under change.

Make build-vs-buy calls. We lean heavily on third-party billing, payment, and tax platforms, and you’ll decide where to extend them and where to build our own primitives around them.

Own the payments stack. Authorization rates and retry logic so a good card doesn’t silently decline, processing cost as a real number you drive down, automated dispute response, and fraud controls that stop bad actors without blocking real customers.

Drive down the manual work. Enterprise contract amendments, pricing config changes, billing support escalations — a lot of it is still human-in-the-loop, and closing that gap is a direct line to scale.

Operate what you ship. You’ll own SLOs on customer-facing flows, instrument the revenue pipeline so discrepancies surface be