---
title: Staff Archetypes
synced_from_vault: true
vault_source: 03-living-docs/patterns/Staff-Archetypes.md
public: true
type: pattern
category: engineering-culture
tags:
  - pattern
  - engineering-culture
  - career-ladder
  - staff-engineer
  - leadership
created: 2026-03-08T00:00:00.000Z
origin: 'staffeng.com, ''Staff Archetypes'''
source: >-
  ~/Library/Mobile
  Documents/iCloud~md~obsidian/Documents/Zettelkasten/Readwise/Articles/Staff
  Archetypes.md
---

| | |
|-|-|
| **Category** | Engineering Culture |
| **Origin** | Will Larson, [staffeng.com](https://staffeng.com/guides/staff-archetypes/) |
| **Surfaced in OS** | Mar 8, 2026 |

---

## Core Concept

Career ladders apply better against populations than people. The Staff-plus engineer title encompasses at least four distinct archetypes, each with different responsibilities, skills, and organizational contexts. Understanding which archetype a person embodies -- or which one your org needs -- is essential for leveling, hiring, and career development.

---

## The Four Archetypes

### Tech Lead
Guides the approach and execution of a particular team. Carries the team's context, maintains cross-team and cross-functional relationships. Close partner to the product manager. Defines the team's technical vision and builds alignment on complex issues. The team's impact grows as the Tech Lead's coding blocks shrink. **Ratio: ~1 per 8 engineers** -- the most common archetype.

### Architect
Responsible for the direction, quality, and approach within a critical technical domain (API design, frontend stack, storage strategy, cloud infrastructure). The domain must be both complex and enduringly central to the company. Effective Architects maintain intimate understanding of business needs, user goals, and technical constraints. Their authority comes from demonstrated consistently good judgment -- not from ivory-tower design.

### Solver
A trusted agent who goes deep into arbitrarily complex, knotty problems. Deployed on work that is critical and either lacks a clear approach or has high execution risk. Solvers generally stop working on problems once they're contained, which creates transience -- and requires a soft touch to avoid infuriating the teams left to maintain the "solved" problem.

### Right Hand
Extends an executive's attention, borrowing their scope and authority to operate complex organizations. Acts as a senior organizational leader without direct managerial responsibilities. The problems are never purely technical -- they involve the intersection of business, technology, people, culture, and process.

---

## Why It Matters

When you're building an engineering ladder for a team with no management layer and multiple people already in Staff-plus roles, understanding which archetype each person embodies helps you:

1. **Level correctly** -- avoid the trap of one-size-fits-all Staff descriptions
2. **Hire for gaps** -- if you have Architects but no Tech Leads, the team structure will suffer
3. **Develop careers** -- help ICs see multiple paths to impact beyond "become a manager"
4. **Set expectations** -- each archetype contributes differently; evaluate accordingly

The toxic preconception warning is important: Architects who design in isolation and hand off to implementers are anti-patterns. Real Architects earn authority through demonstrated good judgment.

---

## Related Patterns

- Developer Fungibility -- the opposite of archetypes; treating all engineers as interchangeable
- Challenge as Compensation -- Staff engineers need challenge; the archetype determines what kind
- [Right Problem Leverage](/patterns/right-problem-leverage) -- Solvers and Architects both operate through problem selection

---

## Cross-References