Five archetypes for a post-role team

Five Archetypes for a Post-Role 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. ...

June 29, 2026 · 14 min · James M
The architect vs builder split in AI-assisted development

The Architect vs The Builder: Redefining Engineering Roles in 2026

TL;DR AI has collapsed the middle rungs of the engineering ladder by automating execution - the junior-to-architect progression no longer works the way it did The emerging split is two human roles: Architects who decide what to build and why, and Builders who turn architectural decisions into precise, testable specifications Neither role exists to write code - code-writing is incidental to both, and AI handles the bulk of implementation The two paths require genuinely different skills that do not build cleanly on each other; taste for architectural judgment and clarity for specification are separate capabilities If you are a junior engineer in 2026, you need to choose your path now - the traditional ladder is a trap, and “I write good code” is no longer a sufficient value proposition For forty years, the engineering career ladder has looked like this: ...

April 6, 2026 · 7 min · James M