Software Engineer, Beneficial Deployments

About the Role:

At Anthropic, we're building AI systems that are safe, beneficial, and transformative. Our mission is to develop AI that benefits humanity, and we believe the most powerful capabilities emerge when we thoughtfully bridge the gap between research breakthroughs and real-world applications.

Many of the people who could gain the most from Claude are the least able to buy it the usual way. A teacher often pays for tools out of pocket. A small nonprofit has no procurement team. A university lab that wants to use Claude has to go through funding, an IT office, and a purchasing department at once. Beneficial Deployments works to reach them, through programs like Claude for Teachers and Claude for Nonprofits and through our work with researchers.

What stands between those people and Claude is rarely the model. It's proving they qualify, getting the right price, buying in a way their institution allows, and landing in the right organization with the right permissions. Those steps run through identity, billing, provisioning, and fraud systems that were built for commercial customers. Our Access team makes them work for everyone else.

We're looking for engineers who find it deeply satisfying to remove the one thing stopping thousands of teachers or scientists from getting started. You'll work in other teams' codebases as often as our own, and much of the job is earning the trust of the engineers, accountants, and safety reviewers who own those systems. This role's focus is access. Experience with billing or identity is a big plus. What matters most is that you finish hard things that cross team lines, get the details right when money and trust are involved, and care about who is on the other end.

Core Responsibilities:

• Own programs like Claude for Teachers or Claude for Nonprofits from design through launch, operation, and support
• Support the verification lifecycle: how educators, nonprofits, and research labs prove eligibility, get reviewed at scale, renew, and are removed fairly when they no longer qualify
• Build pricing, billing, and provisioning that understands programs, including discounts, usage caps, credits, tax exemption, and self-serve purchase, so the next program is configuration rather than a project
• Build safe paths for organizations to move between their available plans and manage their teams, without losing data, seats, or history
• Work directly in partner teams' systems, such as billing, identity, and Safeguards
• Design for trust, with controls and audit trails that stand up to financial audit and student-privacy requirements
• Turn manual review, one-off fixes, and hand-run testing into tools that support, sales, and finance can use themselves
• Share on-call for program issues, and use what you see there to decide what to build next

You might be a good fit if you:

• Have 6+ years of experience building software, with strong backend or full-stack skills and solid grounding in data modeling, APIs, and databases
• Have owned systems where mistakes are expensive, such as billing, payments, identity, entitlements, provisioning, or eligibility
• Have a track record of finishing work that depended on several teams, without formal authority over any of them
• Are comfortable in a large codebase you don't own, and learn the rules its owners care about
• Sweat correctness and edge cases, and can say clearly what you tested and what you didn't
• Enjoy unblocking people and closing things out, and leave the underlying system better each time
• Prioritize well when demand is larger than capacity, including saying no and explaining why
• Communicate clearly across engineering, finance, sales, and support, and care about the societal impacts of your work

Strong candidates may also:

• Experience with subscription or usage-based billing, quote-to-cash, tax, or revenue systems, such as Stripe, Metronome, or Salesforce CPQ, or with building under SOX controls
• Experience with verification, KYC, fraud, or trust and safety systems
• Experience with enterprise identity and administration, such as SSO, SCIM, or large account and data migrations
• Experience building for schools, nonprofits, research institutions, healthcare, or government, or working with FERPA or similar privacy rules
• Experience launching in new countries, including currency, tax, language, and local eligibility
• Experience building products with large language models, or using coding agents heavily in your own engineering work

Deadline to apply: None. Applications will be reviewed on a rolling basis.