Promotion

The staff engineer level is one of the most misunderstood in software engineering. Engineers trying to get there often frame it as “more senior” — more experience, better code, harder problems. That framing produces confusion and frustration, because the staff transition isn’t primarily about doing more of what made you senior. It requires a different way of thinking about what your job is. This isn’t a semantic distinction. It matters because the skills you need to develop, the evidence you need to build, and the way you should spend your time are genuinely different at the two levels. Optimizing the wrong things — spending years getting better at code quality when the lever you actually need is organizational influence — produces a plateau that is difficult to diagnose. ...

There is a common failure mode for engineers who are doing promotion-worthy work but not getting promoted: they believe the work speaks for itself. It doesn’t. The work gets you to the starting line. The promotion case is a separate thing — a curated, evidence-backed narrative about impact, scope, and judgment that your manager and a promo committee can evaluate without direct exposure to your day-to-day. Building that case is a skill, and most engineers have never been taught it. ...