Claim
Staff+ engineering is not one role. It splits into four archetypes: Tech Lead, Architect, Solver, and Right Hand. Solver and Right Hand are explicitly cross-functional — they bounce between problem areas or extend an executive's scope across the org. Treating "staff engineer" as a single shape misses that the role is plural and that two of the four shapes rotate.
Mechanism
A Tech Lead pairs with a manager on a single team; an Architect owns an area's technical strategy long-term. Both are stationary. A Solver is dispatched to whatever fire matters most that quarter; a Right Hand operates as a senior leader's IC partner across teams. Different archetypes need different review criteria, different scope contracts, and different career paths. Without the split, orgs default to Tech-Lead-shaped staff and lose the leverage of cross-cutting roles.
Conditions
Holds when:
- The org is large enough to need multiple staff+ engineers (typically 50+ engineers).
- Leadership maps each staff hire to a specific archetype rather than "senior senior".
Fails when:
- The org has only one staff role and treats it as Tech Lead by default.
- Solver/Right Hand archetypes are deployed without explicit executive-sponsor contracts — they end up homeless and lose impact.
Evidence
"Staff+ archetypes: Tech Lead, Architect, Solver, Right Hand. The Solver and Right Hand bounce from fire to fire, often having more transactional interactions with the folks they're working with on any given week. They're tightly aligned with executive priorities."
— Will Larson, Staff Engineer, 2021. https://staffeng.com/guides/staff-archetypes/
The Larson book pairs the archetype split with interviews of staff engineers from Stripe, Slack, Mailchimp, GitHub, and others to ground each archetype in a real job.
Signals
- Staff engineering postings name the archetype (or describe it concretely) rather than listing generic seniority traits.
- Solver and Right Hand engineers report to or pair with named executive sponsors.
- Promotion criteria differ by archetype — Solvers reviewed on cross-team impact, Architects on long-arc technical bets.
Counter-evidence
Smaller companies (under ~30 engineers) cannot sustain four archetypes. The framework over-fits at scale and can introduce title proliferation. Also, the Solver and Right Hand archetypes can mask an org that should have hired a manager — they are not substitutes for missing director-level coverage.
Cross-references
- A principal IC is a force multiplier — not a more-senior senior — Botros on the role's people-shape; Larson adds the archetype split.
- Glue work is technical leadership, not a tax on the IC — Reilly on the work itself; Larson on the role shape.