Cherny's Five Archetypes
Boris Cherny (Claude Code's creator), 2026-06-28: as "engineering, product, design, DS, etc. melt into a new kind of role," the Claude Code team sorts not by job title but by five archetypes:
- Prototyper — comes up with brand-new ideas; churns out many, most of which don't ship.
- Builder — quickly turns a prototype/idea into production-grade product/infra.
- Sweeper — cleans up the UI, simplifies the code/system, unships, optimizes performance.
- Grower — takes a built product and iterates to improve product-market fit.
- Maintainer — owns a mature system: secure, reliable, fast, efficient as it scales.
People span 2–3 of these, and the archetype is not tied to job function — designers, engineers, PMs, DS each show up across categories. Healthy team mix depends on product stage:
- New / pre-PMF: 1+2+3 (prototype, build, sweep).
- Growing / found PMF: 2+3+4 and some 5.
- Strong PMF: 3+4+5 and some 2.
The closing question: maybe future product roles look like this, less like today's domain-specific titles.
Why it matters here
1. It names RDCO's operating model. The founder runs as a solo operator augmented by agents (Ray + the workflow fleet). Because the agents collapse the role boundaries, he spans all five archetypes in a single session — e.g. 2026-06-29 morning: Prototyper (the lift-over-base-model / agent-brigade ideas), Builder (wiring the execution-eval station), Sweeper (catching the grader fragility and hardening grading to fixed-schema output). Cherny's "roles melt into a new kind of role" is, for the agent-native solo operator, the present tense, not a forecast. Ties to [[2026-06-15-owner-mindset-vs-w2-compounding-reflection]].
2. It's a complementary lens for the agent brigade. The brigade decomposes work into stations — which is itself a role taxonomy. Rough mapping of Cherny's archetypes onto the brigade seats:
| Cherny archetype | Brigade station |
|---|---|
| Prototyper / Builder | spec-author + code-author (turn intent into a working artifact) |
| Sweeper | critic + execution-eval station (simplify, catch slop, prove lift, harden) |
| Grower | the regression-over-time loop (iterate a shipped skill, guard PMF) |
| Maintainer | the rail + regression baselines (own the mature catalog as it scales) |
The two taxonomies are different cuts of the same idea: work decomposes into archetypal roles, and in the agent-native world those roles are filled by stations/agents rather than people. See [[2026-06-28-agent-brigade-rough-edges-editor-pass]] and the skill-pipeline plan [[2026-06-27-skill-development-pipeline-plan]].
3. Staffing angle for CAF. The "archetype mix by PMF stage" rule is a useful frame for how to compose a delivery brigade per engagement maturity — a pre-PMF client build leans Prototyper/Builder/Sweeper; a scaled managed-service leans Sweeper/Grower/Maintainer. Worth carrying into CAF brigade-composition design.
Open thread
If the brigade is a role taxonomy made of stations, Cherny's five give a candidate vocabulary and a completeness check: does our station set cover Prototyper→Maintainer, or are we missing the Grower/Maintainer (post-ship iteration + scale) end? Current brigade is strong on 1–3 (build + sweep) and thin on 4–5 (grow + maintain) — the regression-baseline-on-the-rail work is the start of 5. Related: [[2026-06-04-agent-workflow-patterns-catalog]].