Team

TL;DR Boris Cherny, who built Claude Code at Anthropic, posted a short framing: as engineering, product, design, and data science melt into one role, he sees five archetypes on his team The five are Prototyper, Builder, Sweeper, Grower, and Maintainer - and crucially, none of them map cleanly to a job title The interesting claim is not the list, it is the decoupling: the archetype is a description of what energy you bring to a system, not what your contract says you do I think the framing is genuinely useful as a self-diagnostic, and quietly radical for how teams get staffed and rewarded Where it leaves me unsure: it describes a steady-state team that already exists, and says less about how you grow people into these shapes, or what happens to the people who do not fit any of them A short post on X has been rattling around my head for a few days. Boris Cherny, who built Claude Code at Anthropic, was reflecting on what happens to roles when the old functional boundaries stop meaning much. His observation: when he looks at the Claude Code team, he does not really see engineers, designers, PMs, and data scientists. He sees five archetypes that cut across all of them. ...