2026-05-09
May 9, 2026
The promotion is the wrong unit of career progress in a year when mid-management is being compressed and job postings sit 36% below their 2020 baseline. The right unit is which of Will Larson's Staff+ archetypes you're growing into next — and whether your work this quarter proves it.
When a senior TPM or tech leader asks "what's my next move?" they almost always mean a title — Senior to Staff, Staff to Principal, Director to Senior Director, VP to SVP. The implicit ladder is so well-rehearsed that it shapes how you spend your week: which projects you take, which 1:1s you cancel, which RAIDs you let slip because they aren't on the promo packet.
In 2026, this is the wrong unit. The external market is soft for senior eng leaders — ~128,000 tech layoffs year-to-date by early May, AI cited as the primary driver for roughly a quarter of them, overall US tech postings 36% below their February 2020 baseline. Internally, the layer being compressed is mid-management. "Manager of engineering managers" is shrinking; "manager of agents" is being invented. The promotion ladder you knew is bent.
What's stable is scope — the size and nature of the problem you own. Today's deep dive is the case for organizing the next 18 months of your career around archetype shifts, not title shifts.
In Staff Engineer, Will Larson and Tanya Reilly describe four Staff+ archetypes: Tech Lead, Architect, Solver, Right Hand. The model was written for ICs but maps cleanly onto staff/principal TPMs and tech leaders. Each archetype defines a different relationship to scope: Tech Lead owns one team's execution; Architect owns the direction of a critical area; Solver bounces from hotspot to hotspot wherever leadership points; Right Hand extends an executive's attention into terrain the executive can't personally cover.
Title says nothing useful about which of these you actually do. Two Staff TPMs at the same company at the same level can be running fundamentally different jobs — and the one whose archetype matches the company's current need will be the one still in the room after the next reorg.
Why archetypes outperform titles as a unit of progress. Titles are settlement events: someone, eventually, ratifies the work you've already been doing. They lag by 6-18 months. Archetypes are forward-looking: which problem are you choosing to be the person for? You can decide today and start producing the artifact tomorrow. Titles also don't compose. Two promotions in a row to "Senior X" and "Senior Senior X" leave you in the same archetype with a different paycheck. Two archetype shifts in a row — Tech Lead → Architect → Right Hand — change what you can be hired to do, anywhere, by anyone, forever.
The mistake most senior people make. They try to operate at the same archetype with a bigger title. The Senior Staff Tech Lead doing the same Tech Lead job they did two levels ago. The Director of Engineering still acting as the most senior individual contributor. The org gets nothing new from the promotion. Worse: the person now occupies headcount that was supposed to absorb the next layer of complexity, and the next reorg notices.
Where the macro intersects the personal. Larson's argument that the Right Hand archetype is the most defensible to AI compression — the work is correlated with the seniority of the executive you serve, not the headcount of the org you coordinate — is now load-bearing. Routine TPM work (sprint coordination, RAID upkeep, dependency graphs, status doc maintenance) is exactly what agentic tools are eating. Architect work is partly defensible — the synthesis of customer, technical, and organizational constraints into a direction is hard to automate, but it's also the layer most closely watched in cost-driven reorgs. Tech Lead work is the most exposed: the team-level coordination overhead is what AI assistants compress fastest.
This doesn't mean everyone should sprint to Right Hand. It means everyone should know which archetype the next 18 months of the org needs more of, and whether you're a credible candidate to provide it.
Internal lateral mobility beats external promotion in 2026. This is the line that surprises people most. Switching companies for the same archetype + 15% comp is a treadmill — your scope resets to zero on day one, your political capital resets to zero on day one, and the new logo on your résumé doesn't change what you can credibly own. Switching teams internally to take on a Right Hand role for an executive who previously didn't know your name is, by contrast, transformative. You keep the relationships. You keep the context. You add a new archetype.
The case for jumping is strongest when the move expands your archetype set in a way the current org structurally can't. The case against jumping is strongest when you'd land in the same archetype with a bigger title — that's a calorie burn disguised as growth.
The diagnostic question. Before any career conversation in the next quarter, ask yourself: if the promotion never came, would I still want this work? If yes, you're in the right archetype and the title is downstream. If no, the title is the wrong target — and the question to bring to your manager isn't "what's my path to Principal?" but "what would it take to move me into Architect work for the platform org?"
The senior TPM and tech leader who survives the next reorg isn't the one with the freshest title. It's the one who can name, today, which archetype they're growing into next, and whose calendar — not their narrative deck — already reflects the shift.
Try this week. Pick which of the four Staff+ archetypes — Tech Lead, Architect, Solver, Right Hand — best describes the work you're paid for today. Pick the one you want to be paid for in 18 months. Write one paragraph for each: name a specific, concrete artifact you'd produce in the new archetype that you don't produce now (a strategy memo, an org-wide RFC, a recurring exec briefing, a tech-debt-payoff plan that survives a leadership change). Send the two paragraphs to your manager as your H2 development goals. If the response is a shrug, that's the data point.
What it is. Kurt Lewin's diagnostic for any change initiative: any present state is held in place by two opposing sets of forces — driving forces pushing toward change, restraining forces pulling toward the status quo. Make them visible, weight them, and act on the highest-leverage restraining force rather than just adding more drive. Originally developed for organizational change at MIT in the 1940s; today the cleanest application is to your own career, where you have the most data and the most leverage.
When to use it. Stay-or-leave decisions. Accept-the-promotion-or-decline-it. Pick-an-archetype deliberations. Internal lateral moves where the right answer isn't obvious. Anything where your gut is screaming one direction and your spreadsheet says the other.
How to run it:
When NOT to use it. Reversible, low-stakes choices. Save the exercise for moves you can't easily undo — job changes, archetype shifts, geographic moves, declining a promotion that won't be re-offered.
Lewin's original use was for change inside organizations, but the model travels: you are the smallest organization you'll ever lead.
Camille Fournier joins CoreWeave as VP Engineering, Common Services — A clean illustration of the archetype-over-title argument: a senior leader (ex-CTO Rent the Runway, ex-MD JPMorgan, ex-Two Sigma platform lead) takes a VP role at a hypergrowth AI-infrastructure company. The title is smaller than her last; the archetype, scope, and market window are all larger.
Tech layoffs climb in 2026 with AI as the top driver — April alone: 83,387 announced cuts, up 38% month-over-month, ~21,500 explicitly AI-attributed. Bifurcation is sharper than the headline: ML engineer postings up 59% over the same period US tech postings sat 36% below their 2020 baseline. The "tech jobs are down" narrative and the "AI hiring is up" narrative are both true. Read your own role against both.
Lenny's Podcast Network adds The Skip with Nikhyl Singhal — The community of choice for VPs and CPOs working on the next archetype shift. Worth knowing about even if you don't subscribe — when one of your peers brings a Skip framework into a leadership review, you should recognize it.
"We need a new metaphor for careers. Careers used to be like an escalator: you got on, and the system carried you along. Now careers are more like a startup."
— Reid Hoffman, The Start-up of You
Don't miss what's next. Subscribe to Critical Path: