Goodbye Title, Hello Archetype: The Five Profiles Melting IT Roles Together

For nearly thirty years, walking into a systems team was like reading an org chart carved in stone. There was Frontend and there was Backend. There was the Designer, who didn't touch code, and QA, who arrived at the end. There was Full Stack, proud to cross the border; Cybersecurity, who said no to almost everything; Product, owner of the "what," and the Project Manager, owner of the "when." Each with a box, a promotion ladder, and a tribe.

In June 2026, Boris Cherny —head of Claude Code at Anthropic, the person who built the tool millions of developers use today— posted a short reflection that put that org chart in doubt. He didn't announce a model or sell a framework. He wrote, almost thinking out loud, that "as engineering, product, design, etc. melt into a new kind of role," the old titles start to look like a poor way to describe people. And he proposed another: look at people not by their title, but by five archetypes.

Five ways to create value

The five archetypes don't describe departments. They describe how someone contributes across a product's lifecycle: from the initial spark to the mature system that needs care. Here they are, in Cherny's own words:

• Prototyper — the one who ignites. Comes up with brand-new ideas and churns out many, most of which never ship. The value isn't being right every time, but generating a volume of options.
• Builder — the one who materializes. Quickly turns a prototype or an idea into production-grade product or infrastructure. The bridge between "we could" and "it exists."
• Sweeper — the one who cleans up. Cleans up the UI, simplifies the code and the system, unships what's unneeded, optimizes performance. Creates value by removing, not only by adding.
• Grower — the one who fits the market. Takes an already-built product and iterates on it to improve its product-market fit. Lives in the gap between "it works" and "people want it."
• Maintainer — the one who sustains at scale. Owns a mature system and makes it secure, reliable, fast, and efficient as it scales. Their terrain is scale and continuity.

The sharpest observation isn't the list, but the line that comes after. Cherny notes that these archetypes "are not really tied to job function": at his company, some designers match archetype 1, others 2, others 3; and the same goes for engineers and product managers. The archetype is a dimension separate from the title. And plenty of people span two, sometimes three.

I see it all blending into one thing. Call it a builder, call it an engineer, call it a product manager — I don't know what the title is, but the role is changing.

Why now? Because the task that for decades separated an engineer from a designer —writing the code— weighs less and less in the total work. "Coding is a small percentage" of engineering, Cherny says; the rest is "talking to users, brainstorming, debugging, thinking through how something works, planning." When the machine writes the code, what distinguishes one person from another is no longer whether they can code, but what they bring to the product. And that —igniting, materializing, cleaning up, growing, sustaining— never respected the boundaries of the org chart.

Where each IT role lands

Here's the interesting exercise. If archetypes cut across titles, where does each classic role in a development team tend to land? None lives in a single column —that's precisely the thesis— but each has a center of gravity: the lifecycle phases where it has historically contributed most. This map makes it visible.

Intensity: ● core, where it shines most · ◕ frequent · ◔ occasional · ○ rare. Read each row left to right: it's a role's journey through the product lifecycle.

The map tells three stories at a glance. First: the Prototyper concentrates where you'd expect —Product, Full Stack, Design— but belongs exclusively to no one. Second: the Maintainer is the natural home of Backend, QA, DevOps, and Security; the crafts that always thought about scale, failure, and the long run. And third, the most revealing: the Sweeper column is lit up in almost every row. Cleaning up, simplifying, removing turns out to be the most widely shared skill and, as we'll see, the scarcest.

Role by role: what dissolves and what remains

Frontend and Backend stop being a border and become an emphasis. When the agent writes the CRUD and the component, what's left of frontend is product judgment —Prototyper, Sweeper of the interface— and what's left of backend is judgment about systems at scale —Maintainer. Full Stack, once the awkward generalist, becomes the most natural profile of all: the only one already used to crossing columns.

The Designer is perhaps the biggest winner. Freed from wrestling the tool to "deliver specs," their real archetype —Prototyper of experiences, relentless Sweeper of on-screen clutter, Grower who tunes the fit— can finally be practiced by building, not documenting. On Cherny's team, he says, "PRDs are dead: prototypes replaced them."

QA, DevOps, and Cybersecurity share one center of gravity —the Maintainer— and there lies both their strength and their warning. Their value doesn't disappear: in a world where anyone generates code by the truckload, whoever guarantees that code is reliable, secure, and sustainable at scale becomes more necessary, not less. But it's a value exercised late in the cycle, and whoever can only inhabit that column will stay far from where the product is decided.

Product and Project separate cleanly in this frame. The Product Manager is pure Prototyper and Grower —living in "what do we invent" and "how do we make it fit." The Project Manager, by contrast, gravitates toward the end of the cycle: coordinating, holding the pace, getting things across the line. Two crafts that habit lumped together under the word "management," and that the archetypes reveal as near opposites.

The mix changes with the product's maturity

Cherny adds a second idea, as important as the first: there's no "ideal" team in the abstract. The healthy team is the one with the mix of archetypes right for the product's moment.

• New product, before it finds its market — strong in Prototyper + Builder + Sweeper. Everything is exploring fast, building, and pruning; sustaining isn't the problem yet.
• Growing product that has found its market — Builder + Sweeper + Grower, with some Maintainer. Inventing is no longer enough: you must build well, tune the fit, and start caring for what works.
• Mature product with a consolidated market — Sweeper + Grower + Maintainer, with some Builder. The center of gravity moves to sustaining, growing, and simplifying; inventing from scratch weighs less than caring for what exists.

Read together, the three stages say something uncomfortable and useful: the same talent that gets a product off the ground is rarely the one that keeps it healthy years later. Not because one person is worth more than another, but because the product asks for different things at each moment. The brilliant Prototyper suffocates in a mature system; the excellent Maintainer smothers a product that still needs chaos.

What it means for your career

If this way of seeing spreads, the most honest career question stops being "am I backend or am I a PM?" and becomes "in which part of the cycle do I really contribute: do I ignite, materialize, clean up, grow, or sustain?" The answer is portable across jobs, companies, and industries. The title on the card, less and less.

There's one archetype worth a second look: the Sweeper. Almost everyone wants to be a Prototyper —ideas— or a Builder —building. Far fewer people enjoy removing: simplifying, unshipping, deleting code, shrinking a system's surface. On the map it's lit up in nearly every row, and in the team mix it's present in all three stages. In a world where generating code and features becomes cheap, whoever knows how to subtract with judgment is probably the most undervalued profile on the market.

There's a second clue, and it comes straight from Cherny: "the people who are best with today's tools aren't necessarily the ones who'll be best with tomorrow's." The advantage isn't in mastering a specific tool —a framework, a language, an IDE— but in the fluency to adopt the next one. The archetype, the way you create value, outlives the tools; mastery of one particular tool expires.

A word of caution, though: don't overreach. Cherny describes a particular team —Claude Code, at an AI company, with deliberately flat titles and a product in full explosion— and he frames it all as a hypothesis: "maybe the roles of the future will look more like this." A team pulled by different forces won't follow the same rules, and the stone of the org chart doesn't dissolve overnight. But as a lens for looking at a team and thinking about a career, the five archetypes have a rare virtue: they describe what a person actually does far better than the word printed on their title.

The org chart won't disappear. It will turn liquid. And whoever knows how to name their own archetype —and move it to where the product needs it— will travel much farther than whoever stays clinging to the box they were handed on day one.