Boris Cherny, who leads Anthropic's Claude Code team, argues that longstanding craft-based job categories are dissolving. Roles that used to be distinct — engineering, product, design, data science — are increasingly overlapping. Looking at his own team, Cherny identifies five archetypal instincts that replace conventional job titles.
The five archetypes
- Prototyper: generates many ideas and prototypes quickly; most concepts die but the volume yields learning.
- Builder: turns prototypes into production-ready products and ships them.
- Sweeper: deletes, simplifies, and removes unnecessary complexity from systems.
- Grower: focuses on chasing product-market fit and scaling adoption.
- Maintainer: keeps mature systems running reliably at scale over the long term.
Cherny notes these archetypes ignore traditional functions: some designers act as prototypers, some engineers act as sweepers.
How this maps to reality
For decades organizations arranged people by craft on org charts: engineers over here, designers there, product managers in between. That model worked when execution was the bottleneck and each craft was a scarce skill. The shift Cherny highlights is that AI has dramatically collapsed the cost of execution: anyone can now generate a prototype or ship production code with an agent.
As a result, the scarce capability is no longer the craft itself but the ability to recognize which phase a product is in and to have the instinct appropriate to that phase. Cherny’s five types are best understood as five instincts, and a healthy team is a mix tuned to the product’s maturity rather than a roster of fixed job functions.
Implications
The key takeaway is that when AI can perform many crafts, it matters less what you are good at and more when you are good at it. Organizations and leaders therefore need to assemble teams based on the product lifecycle and the instincts required at each stage, not only by traditional role definitions.
Summary
In Cherny’s view, AI-driven reductions in execution cost are reshaping how work is organized: functions give way to phase-aligned instincts. Team composition should follow product maturity and the necessary instincts rather than the historic job-title model.
