Staff Engineer Archetypes

Staff engineer is not one role — it is four distinct archetypes that organizations need at different stages and scales. Understanding which archetype fits your strengths and your organization’s needs is the difference between thriving and struggling at the staff level.

---

The Four Archetypes

Tech Lead:
  Scope: Single team
  Focus: Team delivery, technical direction, mentoring
  Influence: Direct (writes code, reviews PRs, sets standards)
  Common in: Most organizations, most common archetype

Architect:
  Scope: Multiple teams, organization-wide systems
  Focus: Technical vision, system design, cross-cutting concerns
  Influence: Strategic (writes design docs, not much production code)
  Common in: Large organizations, complex systems

Solver:
  Scope: Wherever the hardest problem is
  Focus: Deep technical problems that block the organization
  Influence: Targeted (solves specific problems, then moves on)
  Common in: Organizations with diverse technical challenges

Right Hand:
  Scope: VP/CTO's priorities
  Focus: Whatever the engineering leader needs done
  Influence: Delegated authority (acts on behalf of leadership)
  Common in: Organizations with strong VP/CTO who needs leverage

---

How Each Archetype Operates

Tech Lead

Day-to-day:
  - 30% coding (critical paths, unblocking work)
  - 30% code review and standards
  - 20% project planning and coordination
  - 20% mentoring and growing the team

Success looks like:
  - Team ships consistently, high quality
  - Team members are growing and getting promoted
  - Technical debt is managed, not ignored
  - Team's systems are reliable and well-documented

Failure mode:
  "Still the best individual contributor on the team"
  → Team depends on you, not growing

Architect

Day-to-day:
  - 40% design documents and technical strategy
  - 25% stakeholder alignment across teams
  - 20% reviewing designs from other teams
  - 15% prototyping and proof of concepts

Success looks like:
  - Organization makes coherent technical decisions
  - Cross-team projects succeed without constant intervention
  - Technical strategy is clear, documented, and followed
  - Disaster cases avoided through proactive architecture

Failure mode:
  "Ivory tower architect who designs but doesn't ship"
  → Designs don't survive contact with reality

Solver

Day-to-day:
  - 60% deep technical work (debugging, performance, migration)
  - 20% knowledge transfer to team owning the area
  - 10% documenting approach and patterns
  - 10% identifying next high-priority problem

Success looks like:
  - Organization's hardest problems get solved
  - Solutions are sustainable (team can maintain them)
  - Knowledge is transferred, not hoarded

Failure mode:
  "Hero who solves the problem but nobody else can maintain it"
  → Creates dependency on the solver

---

Choosing Your Archetype

Ask yourself:
  Do you love leading a team?           → Tech Lead
  Do you love system design?            → Architect
  Do you love hard technical problems?  → Solver
  Do you love organizational impact?    → Right Hand

Ask your organization:
  Team needs technical leadership?      → Tech Lead
  Organization needs technical vision?  → Architect
  Organization has blocking problems?   → Solver
  VP/CTO needs strategic leverage?      → Right Hand

---

Anti-Patterns

Anti-Pattern	Consequence	Fix
Wrong archetype for the org	Impact doesn’t match needs	Align archetype to org’s biggest gap
Tech Lead who doesn’t delegate	Bottleneck, team doesn’t grow	Shift from doing to enabling
Architect disconnected from code	Ivory tower designs	Regular prototyping, real system work
Solver who doesn’t transfer knowledge	Bus factor of 1	Documentation + pairing + handoff period
Right Hand without explicit authority	Influence without power	Clear sponsorship from VP/CTO

Staff engineering is not about being the best coder — it is about having the largest positive impact on your engineering organization. The archetype determines how you deliver that impact.