The moment everything changes
There comes a point in your career where the next step is no longer obvious. Being a Senior Engineer means mastering your craft. But after that, the road forks: you can become a Staff Engineer or an Engineering Manager.
Both are leadership roles. Both multiply the team’s impact. But the way they do it is fundamentally different.
Staff Engineer: technical leadership without people management
As a Staff Engineer, you remain an Individual Contributor. Your value lies in technical depth, in the architectural decisions that unblock others, in raising the team’s bar through mentoring and standards.
- You define the long-term technical vision
- You solve the problems no one else can solve
- Your influence is horizontal, not hierarchical
Engineering Manager: leadership through people
As an Engineering Manager, your code is no longer your main contribution. Your contribution is the team itself: its growth, its well-being, its ability to deliver.
- Your calendar fills up with 1:1s and planning sessions
- You navigate organizational politics to protect the team
- You measure your success by the success of those you lead
The relevance of the IC in modern teams
High-performing teams need both profiles. The Staff Engineer brings the technical clarity that prevents months of rework. The Engineering Manager builds the environment where that talent can thrive.
Without strong senior ICs, teams lose technical direction. Without good managers, talent burns out and leaves. The balance between both roles is what makes teams truly scale.
What nobody tells you
For me, walking this path has been deeply rewarding. Seeing how a well-thought-out architectural decision unblocks an entire team, or how a difficult conversation with an engineer helps them grow — these are moments no successful deploy can match.
The impact becomes less visible but exponentially greater. And that, although sometimes lonely, is what makes it worth it.
The key is choosing the path that aligns with what energizes you: solving complex technical problems, or building teams that solve them.