"Staff Engineer" book notes
Published at 2024-10-24T20:57:44+03:00
These are my personal takeaways after reading "Staff Engineer" by Will Larson. Note that the book contains much more knowledge wisdom and that these notes only contain points I personally found worth writing down. This is mainly for my own use, but you might find it helpful too.
,.......... ..........,
,..,' '.' ',..,
,' ,' : ', ',
,' ,' : ', ',
,' ,' : ', ',
,' ,'............., : ,.............', ',
,' '............ '.' ............' ',
'''''''''''''''''';''';''''''''''''''''''
'''
Table of Contents
The Four Archetypes of a Staff Engineer
Larson defines four archetypes. You'll probably recognize yourself in one (or a mix):
- Tech Lead: You own the technical direction of a team. Architecture, quality, keeping everyone aligned.
- Solver: You get thrown at the hard cross-team problems. Basically a firefighter for gnarly stuff.
- Architect: Long-term technical vision. Standards, system design, things that need to last.
- Right Hand: Trusted technical advisor to leadership. Strategy, org politics, the stuff nobody else wants to touch.
Influence and Impact over Authority
You won't have direct authority over most people or teams you work with. Influence is the actual tool here. You have to persuade, align, sometimes just nudge people in the right direction. No one reports to you, but you still need to drive outcomes.
Breadth and Depth of Knowledge
You need to know a bit about a lot of things (infra, security, product, etc.) but still be able to go deep in a few areas. The tricky part is keeping that breadth current without spreading yourself too thin.
Mentoring is obvious -- help people grow technically and career-wise. But sponsorship is the one that surprised me: actively advocating for people, creating opportunities for them, pushing them forward. It's not just answering questions, it's putting your reputation behind someone.
Managing Up and Across
You have to manage up (set expectations with leadership, advocate for technical needs) and across (work with peer teams, build alignment). Basically a lot of communication and relationship building. Easy to underestimate this one.
Strategic Thinking
Senior engineers focus on execution. Staff engineers need to think about what happens months or years from now. That means sometimes pushing back on short-term pressures in favor of longer-term architectural decisions. Not always a popular move.
Emotional Intelligence
The higher you go, the more soft skills matter. Building relationships, resolving conflicts, reading the room. I think this catches a lot of engineers off guard -- you can't just be the smartest person technically anymore.
Navigating Ambiguity
A lot of the problems you deal with are poorly defined. Nobody knows exactly what the problem is, let alone the solution. You have to be comfortable operating in that fog and still making progress.
Visible and Invisible Work
A huge chunk of Staff Engineer work is invisible. Aligning teams, influencing decisions, resolving conflicts -- none of that shows up as commits. Larson says you need to get comfortable with that, which I think is genuinely hard for engineers who are used to shipping things.
Scaling Yourself
You can't do everything yourself anymore. Write things down, build repeatable processes, mentor others, automate what you can. The goal is to make teams more effective even when you're not in the room.
Career Progression and Title Inflation
"Staff Engineer" means wildly different things at different companies. Titles don't always match actual responsibility or skill. Focus on the work and impact, not the title.
Some of the above is less about technical chops and more about the strategic and interpersonal side of things. Anyway, here are some more concrete takeaways:
Not a faster Senior Engineer
- A Staff engineer is more than just a faster Senior.
- A staff engineer is not a senior engineer but a bit better.
It's important to know what work or which role most energizes you. A Staff engineer is not a more senior engineer. A Staff engineer also fits into another archetype.
As a staff engineer, you are always expected to go beyond your comfort zone and learn new things.
Your job sometimes will feel like an SEM and sometimes strangely similar to your senior roles.
A Staff engineer is, like a Manager, a leader. However, being a Manager is a specific job. Leaders can apply to any job, especially to Staff engineers.
The Balance
The more senior you become, the more responsibility you will have to cope with them in less time. Balance your speed of progress with your personal life, don't work late hours and don't skip these personal care events.
Do fewer things but do them better. Everything done will accelerate the organization. Everything else will drag it down—quality over quantity.
Don't work at ten things and progress slowly; focus on one thing and finish it.
Only spend some of the time firefighting. Have time for deep thinking. Only deep think some of the time. Otherwise, you lose touch with reality.
Sebactical: Take at least six months. Otherwise, it won't be as restored.
More things
- Provide simple but widely used tools. Complex and powerful tools will have power users but only a very few. All others will not use the tool.
- In meetings, when someone is inactive, try to pull him in. Pull in max one person at a time. Don't open the discussion to multiple people.
- Get used to writing things down and repeating yourself. You will scale yourself much more.
- Title inflation: skills correspond to work, but the titles don't.
E-Mail your comments to paul@nospam.buetow.org :-)
Other book notes of mine are:
2025-11-02 'The Courage To Be Disliked' book notes
2025-06-07 'A Monk's Guide to Happiness' book notes
2025-04-19 'When: The Scientific Secrets of Perfect Timing' book notes
2024-10-24 'Staff Engineer' book notes (You are currently reading this)
2024-07-07 'The Stoic Challenge' book notes
2024-05-01 'Slow Productivity' book notes
2023-11-11 'Mind Management' book notes
2023-07-17 'Software Developers Career Guide and Soft Skills' book notes
2023-05-06 'The Obstacle is the Way' book notes
2023-04-01 'Never split the difference' book notes
2023-03-16 'The Pragmatic Programmer' book notes
Back to the main site