Two PMs. Same job title, same five years of experience, same domain. One ships every quarter, holds her own with engineering, and her CEO defers to her on roadmap calls. The other writes great PRDs and runs clean sprints, but every non-obvious decision gets escalated. Which one is the senior PM?
The framing of seniority as "years of experience" is so pervasive that even hiring teams use it as the primary lens. It's a proxy. And it's leaky enough that most companies end up with a few seniors who shouldn't be, and a few mid-levels who quietly are.
The real axis: decision scope you can own
The cleanest definition I've found is that a senior PM is someone whose company trusts them to make decisions of larger scope without escalation. That's it. Everything else, the writing and the frameworks and the stakeholder management, is in service of that trust.
Scope is three dials: how many people the decision touches, how hard it is to reverse, and how little data you have going in. Turn two of them down and most mid PMs are trusted to make the call. Turn all three up and you're describing a senior one.
What that looks like in practice
A mid PM owns a feature inside a roadmap somebody else set. They write the spec, run the sprint, ship the thing. The scope is clear and the bounds are visible. Somebody else defined the metric.
A senior PM owns the roadmap itself, or a domain inside it with enough latitude to set sub-strategy. A customer asks for X, and X conflicts with Y that's already committed. Who decides? Engineering says they can build A in two weeks or B in six, and somebody has to pick. Then the CEO asks what to do about competitor Z's launch, and a defensible answer is expected by morning.
None of that is about years. It's judgment under uncertainty, calibrated through enough reps that people are willing to bet on it.
How seniority compounds (and how it stalls)
The PMs I've watched move fastest from mid to senior do two things. They take decisions one bracket above their pay grade, on the implicit deal that they'll either nail it or escalate before there's damage. And they write the trade-offs down. Every decision, so a skip-level reading the notes sees the reasoning and not just the outcome.
The ones who stall do the opposite. They wait for the next decision to be assigned, and they ship outcomes with no reasoning trail behind them. Neither habit leaves leadership anything to inspect. Trust gets extended against things you can inspect.
The leaky proxy of "years"
Years matter. They matter because they correlate with reps, and the correlation is loose. A PM with 6 years across three companies has seen more decision contexts than one with 6 years on the same product. A PM with 4 years who's run two zero-to-one launches has more relevant judgment than a PM with 8 years maintaining something mature.
If you're hiring, look at decision scope in the candidate's last role. Not "what did you ship". Anyone can answer that. Ask "what decision did you make in the last quarter that you would've escalated a year earlier?" The answer tells you where they actually sit on the seniority axis.
If you're being hired, the same prompt works on yourself. The trajectory you want is the one where last quarter's hardest call would have been an escalation two quarters ago.
