/Tech5h ago

Claude Code creator Boris Cherny says five execution-based archetypes are replacing traditional siloed engineering and product roles

Story Overview

Boris Cherny, who leads Claude Code at Anthropic, has mapped five execution-focused archetypes that emerged on his own team and appear to be dissolving the old walls between engineering, product, design, and data science. Rather than fixed job descriptions, these patterns—Prototyper, Builder, Sweeper, Grower, and Maintainer—describe what actually gets done at different moments in a product’s life.

6238.4K902#1 BOOKMARKED8.4K786.4K

6238.4K9028.4K786.4K

#369

Original post

Boris Cherny@bcherny#369inTech

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:

1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales

Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.

A healthy team needs a mix of these, depending on the product:

- A product that is new and pre-PMF needs people that are strong at 1+2+3 - A product that is growing and has found PMF needs 2+3+4 and some 5 - A product that has strong PMF needs 3+4+5 and some 2

Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

4:45 PM · Jun 28, 2026 · 807.8K Views

Team Composition

Product stage dictates which archetypes dominate

New work before product-market fit leans on Prototyper plus Builder plus Sweeper energy. Once traction appears, the mix tilts toward Builder, Sweeper, and Grower with some Maintainer support. Mature systems that already have strong fit keep Sweeper, Grower, and Maintainer at the center while still borrowing Builder skills when needed.

Open Question

Many people already juggle two or three of these patterns

Cherny notes that individuals routinely span multiple archetypes and that the mix is deliberately adjusted as the product matures; the lingering uncertainty is whether future hiring and org charts will stop anchoring on domain titles altogether and organize around these execution styles instead.

Sentiment

Sentiment building, check back later.

Cluster Engagement

Digg Deeper

No Digg Deeper questions have been answered for this story yet.

Posts from X

Most Activity

VIEWS23.4KBOOKMARKS27LIKES183RETWEETS4

Kun Chen@kunchenguid

i never quite liked the idea of defining archetypes, because it's easy for people to look at it and think "ah that's who i am" and never question themselves again

in reality, a person's role often needs to evolve along with the project. when i'm starting a new project i'm a prototyper and builder, but very soon i become a sweeper when rough edges become the bottleneck. then i become a grower and maintainer as the project becomes more mature. if i box myself into a particular role, i would have to give up the project somewhere along the way

and increasingly, when we juggle between multiple projects at the same time, we need to be able to play different roles in different places. categorizing ourselves into certain archetypes often prevent people from expanding their ambition

so my advice - stay flexible and be obsessed with whatever is important for achieving your goal, and care less about the boundaries of roles that will continue to blur over time

4h23.4K18327

REPLIES5

Boris Cherny@bcherny

@kunchenguid Totally agree. Roles often change over time/project

4h16.7K774

rahul@0interestrates

4. Grower 5. Shower

1h3K7910

Nikhil Krishnan@nikillinit

@bcherny I'm a grower, not a shower/prototyper

4h2K681

ZOYAN@MEM00063

This role structure maps naturally to a brain-inspired, multi-brain architecture: specialized systems for prototyping, building, simplifying, growing, and maintaining. But the deeper question is what happens when models have absorbed most of the recurring patterns these roles provide, and only a small number of people can still contribute genuinely novel signal. At that point, the challenge is no longer how humans adapt to new role categories. It is how the organization functions when far fewer humans are needed to keep teaching and advancing the system.

4h17686

Boris Cherny@bcherny

@richardt830 When I look at Anthropic, we have a mix of DS archetypes also. Some DS are really good at zero-to-one projects, some are great at optimizing mature systems, etc. What is interesting is these archetypes do not seem to be specific to engineering.

4h9K263

Richard Tang@richardt830

@bcherny Curious how DS is fitting into the archetypes? Is it mostly 4? at other companies where those roles were more compartmentalized, I feel like DS’s role is increasingly reduced to “data folks” whom can be replaced with self-serve analytics.

5h11.7K93

Nik@mycomradio

@bcherny This model is still valid

4h591133

Boris Cherny@bcherny

@pachu2120 Claude can help with all of these to varying extents, and will improve over time. Agree that Sweeper/Builder Claude is quite good at today.

4h9.1K102

Pete Hunt 🚁@floydophone

@bcherny the a-team (1983) gave us the architecture for the modern ai-enabled software delivery team - the leader (col hannibal smith) - the face (lt tempelton peck) - the muscle (sgt ba baracus) - the wildcard (capt murdock)

kids these days just keep reinventing management!

4h61092