The Staff Engineer Mindset
The jump from senior to staff isn't about writing better code. It's about changing your entire definition of output. Here's the mental shift that actually matters.
Your Output Changes Completely
Senior engineers are measured by what they ship. Staff engineers are measured by what the team ships. That's a profound difference. Your code contribution might actually go down — and that's the sign you're doing it right.
Technical Strategy as a Skill
Staff-level work is writing the architecture doc that prevents a year of wrong decisions. It's the RFC that aligns five teams on a shared pattern. It's identifying the constraint that's slowing everything down and removing it.
Influence Without Authority
You rarely have the authority to mandate technical decisions across teams. You earn influence by being right consistently, communicating clearly, and making it easy for people to agree with you. Persuasion is a technical skill.
The Glue Work That Gets Overlooked
Writing runbooks. Improving onboarding. Fixing the flaky test suite that everyone ignores. This work doesn't show up in sprint velocity, but it's often what separates high-functioning teams from dysfunctional ones.
Knowing When to Code Yourself
There's a trap where staff engineers stop coding entirely and lose touch with ground truth. I try to stay hands-on with at least one meaningful technical project per quarter. It keeps me honest and earns credibility with the team.
Writing as Leverage
A well-written design doc reaches 20 engineers asynchronously. A Slack message disappears. A meeting scales to 6 people. Writing is the highest-leverage communication tool available to a technical leader — invest in it seriously.
