Your role isn't your title: five archetypes for agent-augmented teams
When the agent absorbs execution, what sets you apart stops being your title —engineer, design, PM— and becomes your posture in the product lifecycle.
Boris Cherny, who leads Claude Code at Anthropic, looked at his team and didn’t see engineers, designers, and PMs: he saw five archetypes —Prototyper, Builder, Sweeper, Grower, Maintainer— and one detail that throws you: none of them is tied to a title (via X). A designer can be a Prototyper; an engineer, a Sweeper; a PM, a Maintainer.
The underlying idea is this: when the agent eats the mechanical execution —writing the code, running the tests, opening the PR—, what sets you apart stops being your title and becomes your posture in the product lifecycle. Not “I’m an engineer,” but “I’m prototyping” or “I’m maintaining.” It’s worth looking at all five before deciding who does what.
The five archetypes aren’t five titles
Most people span two of these five postures, sometimes three, and they rarely match their title. Boris names five, not five job titles: the Prototyper churns out brand-new ideas and assumes most won’t ship; the Builder takes that prototype and quickly turns it into production-grade product or infrastructure; the Sweeper cleans up the UI, simplifies the code and the system, removes what’s surplus, and optimizes performance; the Grower takes something already built and iterates on it to improve Product-Market Fit (PMF); the Maintainer owns a mature system and keeps it secure, reliable, fast, and efficient as it scales.
What matters is that the posture doesn’t track with the title. At Anthropic, Boris says, some designers fit the first, others the second, others the third —and the same goes for engineers, PMs, or data scientists—.
In practice: tag your next task with the archetype it calls for —prototype, build, sweep, grow, maintain— in the ticket itself, not in your head, right next to your title. You’ll see you usually hop between two.
A healthy team shifts its mix by stage
A team’s composition isn’t “3 engineers and 1 designer.” It’s which mix of archetypes the product’s stage calls for, and Boris lays it out in three recipes: a new, pre-PMF product needs people strong at Prototyper + Builder + Sweeper (1+2+3); one that has found PMF and is growing needs Builder + Sweeper + Grower plus some Maintainer (2+3+4 + some 5); one with strong PMF needs Sweeper + Grower + Maintainer plus some Builder (3+4+5 + some 2).
The mechanism is that each stage rewards a different posture. Put five Maintainers on a pre-PMF product and caution kills it; put five Prototypers on a mature system and they break it. The mismatch between the mix you have and the stage you’re in is the bug, not the people.
In practice: at your next retro, build an archetype × person table —five columns, one row per member— and mark each person’s dominant posture. Compare the most-repeated column against your product’s actual stage: if Sweeper, Grower, and Maintainer fill up and no one prototypes on something still pre-PMF, that gap is your next hire.
Why titles decouple
A recent paper —The End of Software Engineering, arXiv, June 2026— measures how far this goes: multi-agent coordination cuts debugging time by 93% in its tests (arXiv). When executing is nearly free, writing code becomes a commodity and —the paper argues— the human differentiators shift to articulating intent, architectural oversight, and quality calibration.
That’s the mechanism. The boundary that separated titles was who can implement; if implementing stops being the bottleneck, that boundary dissolves and what’s left —generate, build, simplify, grow, maintain— cuts across job titles. The paper organizes roles by when the decision happens in the process, not by the function of whoever makes it: it’s Boris’s observation seen from academia.
In practice: in your next hiring or review cycle, swap the by-function rubric —“frontend / backend / PM”— for a posture question: where in the lifecycle —generate, build, simplify, grow, maintain— does this person actually excel? That’s what now predicts the outcome.
The FDE already lives on the ladder
There’s one role that already hops between archetypes for a living: the Forward Deployed Engineer (FDE). FDE postings went from 643 to 5,330 in a year —a +729% year-over-year jump from April 2025 to April 2026 (Exponent, a directional figure from an interview-prep platform)—. That the boom coincides with capable agents isn’t a coincidence: the FDE is the most mobile of the five archetypes.
The mechanism: an FDE starts glued to the customer-zero prototype (1+2), hardens the deployment in production at the client’s site (2), and sometimes maintains it afterward (5) —all in the same week, without handing off to another team—. It’s the generalist-across-the-lifecycle turned into a job: the fluidity Boris describes, but as a paid role.
In practice: if you’re an FDE —or want to be—, log which rung you touched on each delivery, from 1 to 5. After a month you’ll have your real archetype profile —it rarely matches the title— and you’ll know which posture you need to practice.
Watch which archetype the work calls for, not your title
Prototyper, Builder, Sweeper, Grower, Maintainer: five postures toward the work, none tied to a title. When the agent takes over mechanical execution, the title —engineer, designer, PM— becomes a poor predictor of what you actually do on any given Tuesday. The archetype doesn’t.
It’s not that titles vanish tomorrow; it’s that they stop being the useful unit for dividing work, building a team, or understanding what you’re good at. The question stops being “what am I” and becomes “what posture does the thing in front of me call for.”
Which archetype did the last task you finished call for —and does it look like what’s on your title?