I've been in SRE for about 10 years. Started as a junior, made my way through mid, senior, and now staff levels. Here's what I learned about growing in this career path.
Junior → Mid
The main shift: learn to operate without constant guidance.
As a junior, you'll be handed tickets and shown how to handle them. Your job is to do them well and ask questions. At mid-level, you should be able to take an ambiguous problem and produce a reasonable first attempt without help.
Signs you're ready to move up:
- You can handle a routine on-call shift without senior help
- You can write a post-mortem that doesn't need major revisions
- You're improving your team's processes without being asked
What I wish I'd focused on: fundamentals. Linux, networking, the tools your team actually uses. Not the fancy stuff. The boring deep knowledge pays off forever.
Mid → Senior
The main shift: from executing well to choosing well.
Mids know how to solve problems. Seniors know which problems to solve. You stop asking 'how do I implement this' and start asking 'is this the right thing to implement.'
Signs you're ready:
- You're turning down work that doesn't make sense, with good reasons
- Other engineers come to you for design input
- You're anticipating failures, not just responding to them
- You own an area of the system without anyone telling you to
What I wish I'd focused on: writing and communication. The best senior SREs are also the best writers. Not fancy writing. Clear, boring, structured writing. It's the highest-leverage skill at this level.
Senior → Staff
The main shift: from individual contribution to organizational leverage.
Seniors ship features. Staff engineers ship teams. At staff level, your biggest impact is making other engineers more effective — through design leadership, process improvements, mentorship, and systems thinking.
Signs you're ready:
- You spend more time in strategic work than tactical work
- Your ideas show up in other teams' roadmaps
- You're the person leadership asks to sanity-check big decisions
- You own organizational problems, not just technical ones
What I wish I'd focused on: saying no gracefully. Staff engineers who can't say no get pulled into everything. Staff engineers who can say no with good reasons become force multipliers.
The whole journey
Here's the pattern: every level up is about expanding scope and reducing supervision. Junior: small scope, lots of help. Mid: medium scope, less help. Senior: large scope, peer-level. Staff: org-wide scope, shaping others.
The biggest mistake is trying to be promoted by working harder at the current level. You get promoted by demonstrating the next level's behavior before you're asked to.
The quiet truth
Most SRE career growth doesn't come from learning new technology. It comes from learning people, communication, and judgment. The technical floor gets you to mid-level. Everything above that is about humans.
If you're stuck at senior and wondering why you're not hitting staff, it's almost certainly not a technical gap. It's a leverage or communication gap. Work on that. It changes everything.
Written by Dr. Samson Tanimawo
BSc · MSc · MBA · PhD
Founder & CEO, Nova AI Ops. https://novaaiops.com
Top comments (0)