Senior Is a Skill Level. Staff Is a Different Job
The move from senior to staff engineer confuses almost everyone, because the thing that got you there stops being the thing you are measured on. What changes, what a staff or principal engineer does all week, and how to tell if you would even enjoy it.
On this page
For the first several years of an engineering career, the game is clear. Get better at building things. Take on harder tickets. Become the person who can be handed a difficult problem and trusted to return a good solution. Do that long enough and someone calls you senior.
Then you aim for the next level, do more of the same, and nothing happens.
It took me a while to understand why. Senior is the top of one ladder. Staff is the first rung of a different one. You do not get there by being a faster senior engineer, in the same way that being an excellent player does not make you the coach.
Think of a kitchen. A senior engineer is the best cook in it. Hand them any order and it comes out perfect.
A staff engineer is the person who notices the kitchen is laid out badly, so every cook walks twice as far as they need to. They redesign it, persuade the owner it is worth closing for a day, and then every cook gets faster.
They may cook less. The restaurant serves more.
What actually changes
From answers to questions. A senior engineer is given a problem and solves it. A staff engineer is given a mess and works out what the problem is. “Our users keep leaving at checkout” is not a ticket. Somebody has to turn it into one, or into five, or decide it is the wrong thing to fix.
From your output to everyone’s. Your impact is no longer what you ship. It is what gets shipped because of you: the decision you unblocked, the design you improved, the engineer you taught.
From one team to several. The interesting problems at this level sit between teams, where nobody owns them.
From code to writing. Proposals, design documents, strategy, post-mortems. If you cannot write clearly, your ideas travel only as far as your voice.
From being right to being effective. Having the best idea is worth nothing if nobody adopts it. A large part of the job is persuasion.
That last one surprises people who chose the technical track to avoid politics. I have bad news.
What the week looks like
It varies, but a realistic mix:
- Clarifying. Taking a vague goal from leadership and turning it into something a team can start on.
- Deciding. Making or guiding the calls that are hard to reverse. I describe my process in how I make technical decisions.
- Reviewing. Designs more than code. Catching the expensive mistake before it is built.
- Connecting. Noticing that two teams are solving the same problem, or about to collide.
- Translating. Explaining engineering reality to product and business people, and business reality to engineers.
- Mentoring. Deliberately making others better, including handing them the work you would enjoy.
- Building. Still writing code, but choosing carefully: the prototype that proves a direction, the risky core, the thing nobody else can do yet.
When I proposed a single shared widget at Avail, so that teams would stop rebuilding the same swap and deposit screens, most of the work was not the code. It was noticing the duplication, making the case, and designing it so that teams with different needs could each adopt it. The coding came after.
The uncomfortable parts nobody mentions
The feedback loop gets slow. A merged pull request feels good the same day. A good technical direction pays off in a year, and sometimes nobody remembers it was yours.
You will feel unproductive. A day of conversations and one document does not feel like work to someone who used to ship features. It usually was the most valuable day of the week.
You have responsibility without authority. Nobody reports to you. You cannot tell anyone what to do. You have to convince them.
It can be lonely. There are few peers at this level in most companies.
You have to let go. The hardest habit to break is fixing it yourself because it is quicker. It is quicker once. It does not scale, and it takes the learning away from someone else. A mistake I made early in my career was saying yes to every “quick fix”. Learn to say “after Friday”.
Staff and principal
Titles differ between companies, so do not over-read them. Roughly: a staff engineer’s scope is a group of teams or a large product area. A principal’s scope is the whole engineering organization, and sometimes the industry. The work is similar. The blast radius grows.
In a small startup, these titles often mean “the most experienced engineer, who does everything”. That is fine. The work described here still needs doing, whatever it is called.
How to tell if you are already doing it
- People from other teams ask your opinion without being told to.
- You are handed problems, not tasks.
- You have written something that changed what the team builds.
- Someone you mentored now does a thing you used to do.
- You have talked the team out of building something.
- When something is unclear, people look at you.
If several of these are true, you may already be doing the job without the title. That is how it usually works: the role comes first and the promotion follows.
How to move toward it
- Find the problem nobody owns and take it. They are usually between teams, and usually boring.
- Write. A one-page proposal for something you think should change. Then another.
- Finish things. A reputation for closing is worth more than one for starting.
- Learn the business. Know how the company makes money and what worries the founders.
- Make others successful and be seen to do it.
- Say what you think, clearly and early. I wrote a whole post on disagreeing with leadership.
Is it for you?
It is fine if the answer is no. Some of the best engineers I know want to build all day, are exceptional at it, and would be miserable in a job made mostly of documents and persuasion. A strong senior engineer who loves the craft is not a failed staff engineer.
Ask yourself what a good day looks like. If it is solving a hard technical problem alone, stay close to that. If it is a room of people leaving with clarity they did not have before, you will probably like this job.
With AI taking over more of the typing, I think this second kind of work is where much of the profession is heading anyway. I make that case in AI will replace coders, not software engineers.
Questions people ask
What is the difference between a senior and a staff engineer?
A senior engineer is trusted to deliver complex work well within a team. A staff engineer is responsible for outcomes across teams: choosing the right problems, setting technical direction, and making other engineers more effective. The scope changes from your own output to the organization's.
What does a staff engineer do day to day?
Less coding than you might expect. Typical work includes writing proposals and design documents, reviewing designs across teams, removing ambiguity from unclear projects, mentoring, representing engineering in product and business decisions, and still writing code where it matters most.
Do you have to become a manager to keep growing as an engineer?
No. The staff and principal track exists so engineers can grow in scope and influence without managing people. It is not easier than management, though. It requires just as much communication and persuasion, without the formal authority.