Product Manager, New Markets and Monetization

The shape of it

In the posting’s own words

We're hiring the founding product managers onto this team, and this posting covers all of them. You will own one of the areas below outright, work day to day with a dedicated engineering lead and designer, and be measured on numbers that are company-level goals for the half. Almost none of this exists yet, so most weeks you will be the person defining the problem rather than receiving it.

What it asks for · 7

• Have owned a developer platform, API, billing or money-movement product, or self-serve growth product end to end, and were the person accountable for its revenue or activation number (for most people this means five or more years as a PM, but we care about the ownership, not the years)
• Have built with or shipped on top of large language models, and have a view on what changes about billing, identity, or distribution when the customer is sometimes an agent
• Are technically fluent: you read API docs, work through a billing, identity, or attribution design with engineers, and make calls on platform primitives yourself
• Pull your own data: SQL or equivalent, to define a metric, build a funnel, or size a market
• Have negotiated pricing, revenue share, or program terms with Finance, Legal, or Business Development counterparts
• Write clearly enough that an engineer, an executive, and an external partner can each see the tradeoff you're making
• Care about Anthropic's mission, and specifically about growing this platform in a way where the people building on it share in the upside

Also a plus

• 8+ years of product management experience
• Worked on metering, usage attribution, reseller or cloud-marketplace channels, or enterprise spend management
• Taken a developer platform into a new industry, or built product in healthcare, life sciences, financial services, or another regulated industry
• Grown a developer product's self-serve or startup business, including its pricing and packaging
• Built account, identity, or subscription systems that span more than one product
• Taken a product from zero to one, where the users, the product, and the economics all had to be worked out at once

What the job covers

• Partner and platform billing. How usage that reaches Claude through a partner, reseller, or another platform is metered, attributed, and billed, and the program terms that go with it, so indirect volume can grow without our risk growing with it.
• Spend observability and controls. Giving enterprise buyers a precise view of what they spend and where, and turning that into limits and controls they can enforce, including programmatically.
• One account, and the startup path built on it. One login and one wallet across the API and Claude's subscriptions, so a builder's first commit, first production call, and first invoice are on a single plan.
• A vertical. The platform strategy for a particular industry: what builders there need that the platform doesn't yet do, which bets to make, and shipping them with the vertical's own product and go-to-market partners.

Tools and skills named

Words the posting leans on

• platform15×
• product10×
• claude8×
• partner8×
• business6×
• startup6×
• api5×
• billing5×
• build5×
• industry5×
• built4×
• identity4×
• revenue4×
• attribution3×
• builders3×
• building3×

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.

More open at Anthropic

• Account Executive, AI NativeNew York City, NY; San Francisco, CA | New York City, NY
• Account Executive - DNBSingapore
• Account Executive, Public SectorSydney, Australia
• Account Executive - Public Sector (ASEAN)Singapore
• Accounting, Revenue Internal ControlsSan Francisco, CA | Seattle, WA
• AI Fluency Education LeadSan Francisco, CA | New York City, NY