Claude Code’s creator maps five future job archetypes

five future – Boris Cherny, creator of Claude Code, says engineering, product, and design are starting to “melt into one,” and his team sees five recurring role archetypes: Prototyper, Builder, Sweeper, Grower, and Maintainer. The framework has sparked debate with leaders w

The job titles that used to feel fixed are starting to feel temporary. In the AI era, some roles now sound more like verbs than functions—“builder” instead of a single specialty, or “forward-deployed” added to a résumé as work changes shape.

Boris Cherny, the creator of Claude Code, has been watching that shift closely. On X, he wrote that fields like engineering, product, and design are all “melting into one,” and that his own team could offer a lens into “what roles might look like in the future.”

His team outlined five archetypes. First is the “Prototyper,” described as someone who creates new ideas, “many of which don’t ship.” Next comes the “Builder,” the worker who turns a prototype into a “production-grade product.” Then the “Sweeper,” who cleans, simplifies, and optimizes performance.

Cherny’s fourth archetype is the “Grower,” focused on expanding and iterating on existing products so they fit the market better. The fifth is the “Maintainer,” who keeps an existing product “secure, reliable, fast, and efficient as it scales.”

Cherny said many Claude Code employees span multiple archetypes. He added that a healthy team should have a mix of all five, while the balance may depend on the product’s maturity and scale.

The question underneath the post was blunt. “Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?” Cherny asked.

His argument lands in a wider conversation among tech leaders about how AI will reshape organizational charts. Figma CEO Dylan Field said in October that job titles were merging and that everyone was becoming a “product builder.”

Across the industry, others are also moving away from the term “manager.” Some have chosen alternatives such as “player-coaches” and “org leads,” as the language of leadership adapts to how teams deliver work.

But not everyone liked Cherny’s five-part framing. Kun Chen, a Meta and Microsoft alum, commented that he didn’t like archetypes because they allow workers to pick one and then “never question themselves again.” Chen’s advice was to stay flexible.

Cherny responded, agreeing with the warning. “Totally agree. Roles often change over time/project.”

The discussion also reached a practical fear: whether AI could replace the very people doing the most hands-on parts of the cycle. One commenter asked whether AI could replace the “builder” and “sweeper” roles. Cherny replied that Claude’s power extended beyond those two archetypes.

“Claude can help with all of these to varying extents, and will improve over time,” he wrote.

The sequence in Cherny’s post is clear even as the reaction fractures: first he breaks work into five repeatable patterns, then he insists that real teams won’t stay in only one pattern, and finally he points to Claude’s expanding usefulness across them all.

Claude Code Boris Cherny AI era job archetypes Prototyper Builder Sweeper Grower Maintainer Dylan Field Figma org chart product builder Meta Microsoft