The Five New AI-Era Team Roles Redefining Software Development
Amid the rise of agent coding, Boris Cherny outlines five behavior‑based roles—Prototyper, Builder, Sweeper, Growth, and Maintainer—that blur traditional job boundaries and suggest teams should focus on the lifecycle stage a person can advance rather than fixed titles.
Five behavior‑driven roles
The Prototyper – generates large numbers of disruptive ideas and rough concepts, focusing on quantity and novelty rather than immediate delivery.
The Builder – converts scattered ideas or early prototypes into production‑ready products or high‑availability infrastructure, bridging the jump from a 0.1‑level prototype to a full‑scale service.
The Sweeper – performs "subtraction" by trimming bloated code, simplifying user interfaces, and refactoring chaotic architecture to improve performance and maintainability.
The Growth – takes an already built product and iterates quickly to improve market fit, user retention, and overall necessity, blending product sense, data analysis, and experimentation.
The Maintainer – oversees long‑term operation of mature systems, emphasizing security, reliability, efficiency, and resilience under extreme load.
These roles are not tied to traditional job titles; individuals often span multiple roles. For example, a designer may act as both Prototyper and Sweeper, an engineer as Builder and Maintainer, a product manager as Growth and Prototyper, and a data scientist may combine analysis with Growth and Sweeper tasks.
Role fluidity in practice
Kun Chen (kunchenguid) described his own workflow: at the start of a new project he functions as Prototyper and Builder; when rough edges become bottlenecks he shifts to Sweeper; as the product matures he moves to Growth and Maintainer. He warns that fixing oneself to a single role can block progress.
A data scientist reported frequently doing Sweeper work while applying a data‑science perspective to product building, questioning whether this makes them a "2+3" type.
Stage‑based composition of roles
A brand‑new product seeking market fit benefits from people who excel in roles 1 (Prototyper), 2 (Builder), and 3 (Sweeper).
A product that has found market fit and is growing needs roles 2 (Builder), 3 (Sweeper), and 4 (Growth), with some support from role 5 (Maintainer).
A mature product with strong market fit requires roles 3 (Sweeper), 4 (Growth), and 5 (Maintainer), while retaining a few role‑2 (Builder) contributors.
AI assistance and remaining human value
Some commenters questioned whether AI‑generated code eliminates the need for Builders and Sweepers. Boris Cherny replied that Claude already assists with these tasks and will continue to improve, but human guidance, refinement, and maintenance of AI‑generated output remain essential.
Reference links:
https://x.com/bcherny/status/2071379474277613732
https://x.com/kunchenguid/status/2071382977628795289
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
