Chapter 1 Flashcards — What Would You Say You Do Here?
flashcards tsep staff-engineer role-definition scope archetypes
What are the five axioms of the staff engineer role?
?
- Not a manager, but still a leader — authority comes from expertise, not org chart
- Technical role — genuine technical depth is required, not just soft skills
- Operates with autonomy — doesn’t wait for permission to act
- Sets technical direction — creates and communicates a path forward
- Communicates well — can explain things at multiple levels to multiple audiences
What are Will Larson’s four staff engineering archetypes?
?
- Tech Lead — leads a team or cluster of teams; deeply embedded in day-to-day work; most common archetype
- Architect — owns technical direction for a broad domain; defines interfaces and constraints others build within
- Solver — parachutes into difficult problems no one else can solve; moves from crisis to crisis
- Right Hand — senior technical advisor extending a VP/CTO’s reach; requires total trust and comfort with extreme ambiguity
What are the four disciplines of staff-level work (Yonatan Zunger)?
?
- Core technical skills — deep knowledge of systems, ability to evaluate options, designing at scale
- Product management — understanding user needs, prioritizing work, navigating technical vs. business trade-offs
- Project management — keeping work moving, managing dependencies, scoping, estimating
- People management — helping individuals grow, handling interpersonal issues, ensuring psychological safety — without formal authority
What does “scope” mean in the context of a staff engineer role?
?
Scope is the organizational width of a staff engineer’s influence — measured by what breaks if they stop doing their job. Scope can be: one team only, a cluster of related teams, a department, or the whole engineering organization. Staff engineers are characterized by broad scope, not just technical depth.
What are the signs of scope that is too narrow for a staff engineer?
?
- Nobody asks your opinion on projects outside your immediate team
- Your influence ends at your team boundary
- You’re spending all your time on implementation work
- You’re doing senior engineer work, not staff engineer work
What are the signs of scope that is too broad for a staff engineer?
?
- You’ve stopped going deep on anything
- You’re called into every meeting but add little value
- You feel like a generalist without enough domain knowledge to be useful
- You can’t complete any significant project because you’re spread too thin
What is a role description document and why write one?
?
A 1–2 page document that captures: what your organization needs from a staff engineer in this role, your scope, the shape of your week, your 3–5 key accountabilities, and what you’re explicitly not responsible for. It’s most valuable when shared with your manager — it surfaces misalignments before they cause problems and gives you something concrete to reference when the role drifts.
What is the most important diagnostic question for a staff engineer evaluating their role?
?
“What does my organization need that only a staff engineer can provide?” This question cuts through debates about what staff engineers “should” do by anchoring to what the specific organization actually needs. If the answer is unclear or the answer is “not much,” there’s likely a scope or role alignment problem.