The engineering problem
Senior individual-contributor roles are often described through level expectations while the work itself varies widely. StaffEng's archetypes explain four recurring shapes—Tech Lead, Architect, Solver, and Right Hand—making it easier to discuss what leverage the organization actually needs.
The approach
The archetypes distinguish leadership by operating mode. Tech Leads guide a team or area, Architects shape direction across an important domain, Solvers attack unusually difficult problems, and Right Hands extend an executive's reach. The framework is most useful as a conversation about context, not identity.
Tradeoffs
Each mode carries failure risks. A Tech Lead can become a bottleneck, an Architect can lose contact with implementation, a Solver can accumulate heroic dependencies, and a Right Hand can operate through opaque authority. Healthy organizations pair scope with sponsorship, decision rights, succession, and feedback.
What generalizes
Technical leadership should be evaluated by leverage: clearer decisions, stronger systems, improved standards, reduced coordination cost, and capabilities that persist beyond one person. The role needs an explicit problem statement as much as a system does.
What is context-dependent
Titles, reporting lines, and archetype prevalence differ by company stage and structure. People also move between modes. Treating the four labels as a promotion checklist would flatten the framework's central insight.
Architecture review questions
- What organizational constraint requires Staff-plus attention?
- Which decisions belong to this role, and which do not?
- How does the work create capability rather than dependency?
- What evidence will show that influence is working?
The four archetypes come from StaffEng; the operating risks and review questions are my synthesis.