Boris Cherny, the creator of Anthropic's Claude Code, just dropped a framework that's making rounds in tech circlesβ€”and it's got nothing to do with code completion or model benchmarks. In a post on X, Cherny argued that traditional job titles like "software engineer," "product manager," and "designer" are dissolving into something more fluid. His own team at Claude Code operates on five distinct archetypes that blur the lines between disciplines.

The Five Archetypes

The first type is the Prototyperβ€”workers who generate new ideas, many of which never ship to production. These are the people throwing spaghetti at walls and documenting what sticks. Next up is the Builder, who transforms those raw prototypes into production-grade products that can actually handle real traffic. Then there's the Sweeper, whose job is cleaning, simplifying, and optimizing performance once the product exists. The last two archetypes focus on iteration and stability. The Grower expands existing products and iterates based on market feedback, while the Maintainer keeps systems secure, reliable, fast, and efficient as they scale. Here's the kicker: Cherny notes that many of his employees span multiple archetypes simultaneously, and a healthy team requires a mix of all five typesβ€”but the balance shifts depending on how mature the product is.

Industry-Wide Reckoning

Cherny isn't alone in questioning the org chart's future. Figma CEO Dylan Field said back in October that job titles are merging, declaring that "everyone is becoming a product builder." Other executives are ditching the term "manager" altogether, replacing it with labels like "player-coaches" and "org leads." The traditional hierarchy is getting flattened by AI tools that let smaller teams move faster.

The Flexibility Question

Not everyone's buying into archetypes as permanent identity markers. Kun Chen, a veteran from Meta and Microsoft, pushed back on Cherny's post, arguing that labeling workers lets them pick one archetype and then "never question themselves again." His advice? Stay flexible. Cherny agreed, noting that roles often change over time or project phase.

Can Claude Replace These Roles?

One commenter asked the obvious question: could AI replace the Builder and Sweeper archetypes entirely? Cherny's answer was measured but revealing. "Claude can help with all of these to varying extents, and will improve over time," he wrote. That's a candid admission from someone who literally builds AI coding tools for a living.

Key Takeaways

  • The Prototyper β†’ Builder β†’ Sweeper pipeline is one way to think about product development in an AI-augmented world
  • Most Claude Code employees span multiple archetypes, suggesting the future isn't about specialists but adaptable generalists
  • Traditional job titles like "engineer" and "PM" may become obsolete as roles merge around workflow stages

The Bottom Line

Cherny's framework is less a prediction than an observation from inside one of AI's most important companies. If the people building these tools are already abandoning traditional org charts, the rest of the industry should pay attention.