What Are the Five Archetypes Boris Cherny Observed?
Boris Cherny, the creator of Claude Code, looked at his own team and said what separates people is not job function but five ways of working. The first is the Prototyper, who never stops throwing out rough ideas. Nine out of ten may never ship, and that is fine, because their job is discovery, not success. The second is the Builder, who takes what the Prototyper throws out and turns it into something you can actually serve to a customer, hardened enough that it does not collapse under thousands of users.
The third is the Sweeper. They tidy the interface, simplify tangled code, remove unused features, and speed up the slow parts. They rarely get the spotlight, but without them a product quietly grows heavier until it seizes up. The fourth is the Grower, who tends an already-built product like a plant, improving it by roughly one percent a day until it takes root in the market. The fifth is the Maintainer, who quietly keeps a finished system running the way a building manager keeps a building running -- invisible until the day they are gone and everything suddenly breaks.
Why Are Archetypes Different From Job Titles?
The point of these five archetypes is that they have nothing to do with job titles. Two people who both carry the title "designer" can work in completely different ways -- one like a Prototyper, another like a Sweeper. The same is true for engineers, PMs, and data scientists. Same title, entirely different texture of work.
And most people don't stay in just one archetype. They move across two, sometimes three, at once. Cherny himself says he is a Builder and a Grower. He found it hard to describe himself by job title, but once he switched to archetypes, describing himself became both more accurate and more comfortable.
How Should Team Composition Change With Product Stage?
The framework earns its keep because it pairs with product stage. A new product that hasn't yet found product-market fit (PMF) needs a team strong in Prototyper, Builder, and Sweeper -- survival hinges on a fast loop of throwing out ideas, building them, and refining them.
Once a product has found PMF and is growing, the center of gravity shifts to Builder, Sweeper, and Grower, with a growing share of Maintainer. Once PMF is firmly established, Sweeper, Grower, and Maintainer take the center, and Builder recedes into a supporting role. In other words, even on the same team, the archetype mix that matters keeps shifting as the product matures.
Why Does This Framework Matter for AX Consulting?
In AX consulting work, most teams that wobble after adopting AI are not actually short on headcount -- they are missing the way of working their current stage demands. A team full of strong Prototypers that enters a growth phase will immediately feel the absence of Growers and Sweepers as stalled momentum.
This diagnosis matters even more now that AI tools let one person cover several archetypes at once. In an era where someone can prototype, ship, and analyze the data alone, hiring should no longer start from "one frontend engineer" -- it should start from asking which archetype is missing from the team right now.
How Do You Apply This to Your Team Today?
Applying this is simple. Start by having each person write down what they actually did over the past month and self-diagnose which archetype it resembles. Then check which stage your product is actually in -- pre-PMF, growing, or established -- and overlay the archetype mix that stage needs onto your current team.
Wherever you find an empty archetype, that is where your next hire or development priority belongs. Rather than inventing a new job title, it is far faster to recognize the archetype people are already good at and place them there.