Twitter/X

@bcherny (2026-06-28) identifies five archetypes on the Claude Code team…

2026-06-28 · 23:45 UTC ·@bcherny ·1 min read

Brief

@bcherny maps five product-role archetypes he sees on the Claude Code team—Prototyper, Builder, Sweeper, Grower, Maintainer—and argues people often span 2–3 archetypes. He notes these archetypes cross engineering, design, PM and DS functions and recommends specific mixes (1+2+3, 2+3+4+some5, 3+4+5+some2) depending on product stage.

Why it matters

@bcherny (2026-06-28) identifies five archetypes on the Claude Code team: Prototyper (many new ideas, most don't ship), Builder (turns prototypes into production), Sweeper (cleans UI/code, unships, optimizes), Grower (iterates to improve PMF), and Maintainer (owns mature system reliability/efficiency).

Key details

  • He observes individuals commonly span 2–3 of these archetypes and that the archetypes cut across job functions — designers, engineers, PMs, and data scientists at Anthropic map to different archetypes rather than fixed roles.
  • He prescribes role mixes by product stage: pre-PMF products need archetypes 1+2+3; growing/early-PMF products need 2+3+4 with some 5; mature, PMF-strong products need 3+4+5 with some 2.
Source evidence

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?