I Read 50 Senior Engineer Job Descriptions. Here's What They Actually Want.
When I started applying for senior roles, I did what any engineer would do: I reverse-engineered the requirements.
I collected 50 job descriptions for Senior, Staff, and Principal engineer roles at companies paying $180K-$350K. Here's what I found.
The Words That Appear in Every Posting
Some phrases show up so consistently they're basically table stakes:
- "Production systems" (47/50) — They don't want someone who builds tutorials. They want someone who's been paged at 2am.
- "Cross-functional collaboration" (44/50) — You'll work with product, design, data, and ops. Can you communicate outside your bubble?
- "Mentorship" (41/50) — If you can't teach, you're not senior. Period.
- "Architecture decisions" (39/50) — They want you to DESIGN systems, not just implement tickets.
- "Operational excellence" (35/50) — SLOs, monitoring, incident response. Building it isn't enough — can you run it?
The Words That Differentiate $180K from $300K+
The jump from senior ($180K) to staff ($250K+) is exactly this:
Senior: "Build features and maintain systems." Staff: "Define the technical direction and enable other engineers."
Practically, that means:
| Senior Engineer | Staff Engineer |
|---|---|
| Writes code | Writes code + decides WHAT to build |
| Reviews PRs | Defines code review standards |
| Fixes bugs | Prevents classes of bugs |
| Implements architecture | Designs architecture |
| Uses monitoring | Defines what to monitor |
| Follows processes | Creates processes |
What Most Portfolios Get Wrong
After looking at dozens of engineering portfolios (including my old one), here's the pattern:
What most people show: "I built X with React and Node.js." What hiring managers want: "I chose React over Vue because of X constraint, and here's the trade-off I accepted."
What most people show: "I have 95% test coverage." What hiring managers want: "I reduced production incidents by 60% by implementing targeted contract testing on our payment pipeline."
What most people show: A list of technologies. What hiring managers want: Evidence that you've operated systems at scale and made difficult decisions under constraints.
How I Restructured My Portfolio Based on This
After this analysis, I made three changes:
1. Added a Platform Engineering page. SLOs, incident drills, security receipts, reference architecture. This signals "I run systems, not just build demos."
2. Added case studies with "Challenges" sections. Not just what I built — what went wrong, how I diagnosed it, and what I learned. That's the operational experience signal.
3. Added a Services page with pricing. This sounds counterintuitive for job hunting, but it signals something powerful: "I'm not desperate. I have options. I'm choosing to work with you." Negotiation leverage is a real thing.
The Interview Signal Nobody Talks About
Here's something I noticed: at the $250K+ level, interviews are less about whether you CAN do the job and more about whether you THINK like someone at that level.
They're not testing "can you implement a linked list?" They're testing:
- When you describe a system, do you mention failure modes?
- When you discuss a decision, do you mention what you traded off?
- When something went wrong, do you take ownership or blame the tool?
- Can you explain a complex system to someone non-technical?
My portfolio now answers all four of those questions before the interview starts.
The Actionable Takeaway
If you're targeting senior+ roles, your portfolio should answer:
- What's the most complex system you've OPERATED (not just built)?
- What's a decision you made that had real trade-offs?
- What broke, and how did you fix it?
- Can you teach someone else what you know?
The technology stack matters less than you think. The operational maturity matters more than you think.