This post is the first in a series expanding on the conference talks I have given this year about the path to Staff Engineer and beyond. These talks have resonated with a lot of people who feel stuck between senior engineering and management, unsure of what comes next. Over the next few posts, I will break down what Staff means, how to grow into it, and how to lead without giving up the craft.
If you have been around long enough as an engineer, you have probably felt it: that invisible ceiling. You start as an engineer, move to senior engineer, and then what? The org chart points one way: management.
For some, that is a great path. Management is a real career, with its own skills and rewards. But here is the secret no one tells you when you are staring at that ceiling: being a manager is a completely different job.
When I first stepped into a Tech Lead Manager role, I thought I would pick up the management side easily. It turns out it is it’s own unique skill. Some engineers thrive in it. Some do not. And plenty of brilliant engineers get pushed into it simply because they want to “advance”, not because they want to manage.
The result is predictable. Burnout. Frustration. Or simply losing great technical talent to roles they never really wanted in the first place.
That is where the Staff Engineer role comes in.
What Staff Engineer Really Means
At its core, Staff Engineer is not “Senior Engineer, but more senior.” It is a shift in scope and impact.
Senior engineers deliver projects. Staff engineers shape direction.
- Seniors think about the sprint. Staff think about the next year.
- Seniors solve problems. Staff find the problems worth solving.
- Seniors optimize their team’s velocity. Staff shape systems so multiple teams can move faster.
And crucially, Staff Engineers do all of this without authority. You are not someone’s boss. You do not run performance reviews. But you still need to move the organization forward.
That is why Staff Engineer exists as a parallel track. It is not a consolation prize for people who do not want to manage. It is a recognition that technical leadership is real leadership.
Staff vs Manager: Parallel Paths
Here is how I think about it.
- Managers lead through people. Their tools are hiring, performance reviews, org design, and team health.
- Staff Engineers lead through systems. Their tools are architecture, technical direction, influence, and long-term vision.
Both roles require leadership, communication, and trust. But they operate differently.
At mature organizations, these two tracks are treated as equal, not as rungs on a ladder where one outranks the other. Staff is not a stepping stone to management. It is a destination in its own right.
Not every company has caught up to this idea. Some still treat management as the only “real” path to leadership. But that is changing, and we as a community need to keep pushing for that recognition.
Because the truth is simple: you can be a leader without managing people. Staff Engineer is proof of that.
The Takeaway
If you are staring at that ceiling and wondering if management is the only way up, it is not. There is another path. And if what you care about is shaping systems, influencing technical direction, and multiplying the impact of everyone around you, then Staff Engineer might be exactly where you belong.
Next time, I will dig into the biggest mindset shift you need to make if you want to get there: moving from being a problem solver to becoming a problem finder.
This post is adapted from my talk, “The Path to Staff Engineer and Beyond”, delivered at PSU Mac Admins 2025 and MacDevOps YVR 2025. It is part of a series exploring the journey from senior engineer to staff and beyond.