The 5 New Job Roles Emerging on the Claude Code Team | Aravind Arumugam
ai5 min read
The 5 New Job Roles Emerging on the Claude Code Team
Boris Cherny, an engineer on Anthropic's Claude Code team, recently shared a reflection on X about how job roles are changing. His argument is simple: as engineering, product, design and data science melt into "a new kind of role", what people actually do is captured better by five recurring roles than by their job title. He names them Prototyper, Builder, Sweeper, Grower and Maintainer — five new job roles he sees forming on his own team — and suggests they may be what the roles of the future look like. Here is what each one means, and how a healthy team mixes them by stage.
This is one practitioner's view of his own team, not an official Anthropic job ladder. It is worth adding that at Anthropic most technical staff share a single title, "Member of Technical Staff", which is part of why role and job title have come apart in the first place.
What are the five new job roles?
Cherny describes five roles (he calls them archetypes) that he sees across the Claude Code team. He is careful to note they are not tied to job function: a designer, engineer, product manager or data scientist can fall into any of them, and many people span two or even three.
Prototyper — comes up with brand-new ideas and churns out many of them, most of which never ship.
Builder — quickly turns a prototype or idea into a production-grade product or piece of infrastructure.
Sweeper
— cleans up the UI, simplifies the code and system, unships features, and optimises performance.
Grower — takes a product that has been built and iterates on it to improve product-market fit.
Maintainer — owns a mature system and keeps it secure, reliable, fast and efficient as it scales.
What does a Prototyper do?
The Prototyper generates brand-new ideas at high volume. In Cherny's description, most of these ideas never ship — and that is by design. The role is about exploring the solution space quickly and cheaply, so the few ideas that do have legs can be found without over-investing in the ones that do not.
What does a Builder do?
The Builder takes a rough prototype or raw idea and turns it into something production-grade, fast. This is the role that moves work from "it demos" to "it ships and holds up" — the product and the infrastructure behind it.
What does a Sweeper do?
The Sweeper improves what already exists. Cherny lists four activities: cleaning up the UI, simplifying the code and the wider system, unshipping things that no longer earn their place, and optimising performance. It is the role that fights complexity and entropy.
What does a Grower do?
The Grower takes a product that has already been built and iterates on it to improve product-market fit. Where the Builder gets a product live, the Grower makes it fit its market better over time.
What does a Maintainer do?
The Maintainer owns a mature system and keeps it secure, reliable, fast and efficient as it scales. This is the role that carries the long-term health of a system once it is load-bearing.
How should a team mix these roles?
Cherny's point is that a healthy team needs a mix, and the right mix depends on where the product is:
New and pre-product-market-fit: lean on Prototyper, Builder and Sweeper (1 + 2 + 3).
Growing, with PMF found: Builder, Sweeper and Grower, plus some Maintainer (2 + 3 + 4 and some 5).
Strong PMF: Sweeper, Grower and Maintainer, plus some Builder (3 + 4 + 5 and some 2).
The Sweeper appears at every stage — a reminder that simplifying and unshipping is not a one-off clean-up but continuous work.
Are these roles tied to job titles?
No, and this is the part Cherny stresses most. The roles cut across traditional functions. Across Anthropic, he notes, some designers match the Prototyper role, some the Builder, some the Sweeper — and the same is true for engineers, product managers and data scientists. The suggestion is that the domain-specific job titles of today may give way to roles defined by what someone does, not which department they sit in.
Summary
Boris Cherny of Anthropic's Claude Code team describes five new job roles — Prototyper (new ideas), Builder (ships them), Sweeper (simplifies and unships), Grower (improves product-market fit) and Maintainer (keeps mature systems healthy). They are not tied to job titles, many people span two or three, and a healthy team blends them differently depending on the product's stage: 1+2+3 before product-market fit, 2+3+4+5 while growing, and 3+4+5 once fit is strong. It is one engineer's lens on his own team, but a sharp one for thinking about the job roles of the AI era.
