The Archetypes

Documentation

The Archetypes

Not all Staff Engineers look the same, and they shouldn’t. The role takes different shapes depending on the problems you’re solving, the team you’re embedded in, and the organizational context around you. What remains constant is the expectation of impact at the Staff level — what varies is the form that impact takes.

Will Larson identifies four common archetypes of Staff-plus roles in Staff Engineer. These aren’t job titles or career tracks — they’re patterns. Most Staff Engineers will recognize themselves primarily in one, with elements of others showing up depending on the season. Understanding which archetype fits your current scope helps you read the rest of this guide through the right lens, and helps you and your manager calibrate expectations for what “good” looks like in your specific context.

Tech Leads guide the approach and execution of a team or a small cluster of teams. They partner closely with their engineering manager, carry the team’s technical context, and maintain the cross-team relationships the team depends on. Earlier in their career, they would have been the person implementing the hardest problems. Now, they default to delegating that work — both to grow their teammates and because the team’s impact grows as the Tech Lead’s coding blocks shrink.

This is the most common archetype, and for many engineers, it’s the first shape their Staff role takes. The day-to-day is the most similar to Senior-level work, which makes it an intuitive transition — but the trap is assuming that continuing to do Senior-level work at a higher quality is sufficient. The shift is from doing the work to making the work go well for the whole team.

Architects own the direction, quality, and approach within a critical technical domain — API design, data infrastructure, frontend architecture, cloud strategy. For a domain to warrant an Architect, it must be both complex and enduringly central to the company’s success.

The toxic version of this archetype designs systems in isolation and hands them off. The effective version maintains an intimate understanding of the business’s needs, the users’ goals, and the relevant technical constraints — and uses that understanding to advocate for approaches that hold up over time. Architects who work well stay close enough to the code and the teams to have credibility, even if they’re not writing production code daily.

Solvers are trusted agents who go deep into knotty problems until they’re resolved. They’re typically directed toward problems that leadership has already identified as critical — problems that lack a clear approach or carry high execution risk.

Where most Staff-level roles require significant organizational wrangling, Solvers generally operate on problems that are already understood as priorities. The trade-off is transience: they stop working on problems once they’re contained, which can create a feeling of never finishing anything and requires care to avoid frustrating the teams left behind to maintain the “solved” problem.

The Right Hand extends an executive’s attention, operating with borrowed authority to handle problems that span the intersection of technology, business, people, and process. This archetype typically emerges only in organizations with hundreds of engineers.

The defining discipline of the Right Hand is deep alignment with the leader they serve. Because they operate with that leader’s authority, they must internalize that leader’s worldview thoroughly enough to give the same answer the leader would give — even when the leader isn’t in the room. The joy is that you only work on essential problems. The cost is that you’re always on to the next one before the current one is truly finished.

At a Glance

Archetype	Focus	Scope	Relationship to teams
Tech Lead	Execution and delivery	Single team or small cluster	Deeply embedded, daily collaboration
Architect	Technical domain ownership	Cross-team within a domain	Close but advisory, not embedded
Solver	Hard problem resolution	Wherever the problem is	Temporary, moves between teams
Right Hand	Executive extension	Organizational	Broad but shallow, moves frequently

Which Archetype Are You?

Start by reflecting on the kinds of work that energize you. Tech Leads and Architects tend to work with the same people on the same problems over long periods, building deep team relationships and shared purpose. Solvers and Right Hands move from problem to problem, often working with different people each week, tightly aligned with executive priorities.

Your archetype may also be shaped by what the organization needs more than by personal preference. That’s fine — and over the course of a long career, you’ll likely spend time in more than one.

What matters is that you’re honest with yourself and your manager about which archetype you’re currently operating in. The responsibilities described in this guide apply to all four, but they get weighted differently depending on the shape of your role. A Tech Lead embedded in a single team will naturally have a different profile across the five core dimensions than an Architect operating across a platform. Evaluate yourself against the scope of the role you’re actually in, not an idealized universal template.

Further Reading

The archetype framework comes from Larson’s Staff Engineer, which includes interviews with engineers operating in each pattern — reading the stories that match your archetype is one of the fastest ways to calibrate. Reilly also references these archetypes in The Staff Engineer’s Path (Chapter 1) and adds practical advice on aligning your scope, shape, and primary focus.

The Identity Shift