Career path
Become staff
Build influence beyond your own team.
Technical leadership, ownership, RFCs, architecture reviews, cross-team alignment and decision making.
Senior engineers trying to cross the staff/principal gap without becoming managers.
Are you on this path?
Signs you are here
- Your technical depth is real, but your scope is invisible.
- Your impact lives in your commits, not in other engineers' work.
- You keep solving problems privately instead of durably.
- You are clearly senior, but the staff bar feels undefined.
Staff work is influence made visible.
This path is for senior engineers whose technical depth is real, but whose scope needs to become legible across teams.
- 1
Pick problems that affect more than one team.
- 2
Use RFCs and architecture reviews to make judgement durable.
- 3
Mentor through systems, not only private advice.
- 4
Show how your decisions improve the work of other engineers.
Books for this path
Senior engineers trying to cross the staff/principal gap without becoming managers. Technical leadership, ownership, RFCs, architecture reviews, cross-team alignment and decision making. Every book here is written from the hiring side, from 500+ technical interviews, and each book page shows what is inside and who it is for.
Free resources
Free checklists, cards and templates for the become staff path. Each one is short enough to use on the problem you have this week, and each works on its own, before or without a book.
Template
Mobile architecture RFC and design doc template
A mobile architecture RFC and technical design doc template that makes the decision show constraints, rejected options, rollout risk, ownership and rollback.
Checklist
Staff iOS engineer scope map
A scope map for checking whether your work reads as senior, staff or architect-level impact, using evidence instead of job-title vibes.
Writing for this path
Staff engineering
Staff engineer vs senior engineer: what changes in scope, decisions and evidence
Most comparisons say staff means bigger scope and more influence. From the hiring side the difference is narrower and easier to test: a senior engineer moves the problem, a staff engineer moves the decision around it. What changes in scope, decisions, influence and evidence, how interview loops and promotion committees read it, and the senior-plus trap.
15 min read
Staff engineering
Staff engineer 30/60/90 day plan: map the decisions, then move one
The usual 30/60/90 template plans activities. A staff role is judged on decisions. A week-by-week plan for a new staff engineer: map the hidden decisions and power, pick one stuck outcome, run Surface, Shift and Secure on it, and leave evidence a reviewer can open.
13 min read
Staff engineering
Staff engineer promotion packet: the evidence a calibration committee needs
The review that decides your level is mostly over before you walk into it. What a calibration committee can read, the evidence ledger that turns staff work into proof while it is happening, and the one field that keeps a promotion packet from reading as inflation.
13 min read
Staff engineering
Staff iOS engineer is not senior plus
The staff role means owning scope and decision quality across teams, and making other engineers more effective.
6 min read
Staff engineering
Staff Android engineer is not senior plus
Staff Android work means owning build speed, app health and device fragmentation, and making thirty engineers faster.
6 min read
Staff engineering
Staff engineers change the decisions a team can make
The platform changes. The staff transition does not: your work must improve decisions beyond the feature and beyond your own presence.
3 min read
Career growth
Everyone is coding. Nobody is talking.
The problem with faster code generation isn't only what gets shipped. It's what engineers stop learning from one another.
5 min read
Resume
Staff software engineer resume
Staff is not Senior with more technologies. A Staff resume has to show decisions that changed how other teams work, and most Staff candidates bury exactly that under a list of features.
6 min read
Resume
Principal software engineer resume
There is no universal definition of Principal. There is a common thread: your decisions set the technical direction for more than one team, and the resume has to prove that without a list of titles doing the work.
5 min read
