Walk into most engineering orgs and "senior" means one thing: years since the first job offer. Not judgment under uncertainty. Not the ability to say no to a bad architecture in a room full of people who want to hear yes. Just time served.

That's the fiction. Years correlate with skill early on, then the correlation collapses, and the title stops meaning anything.

Two engineers, both titled senior, five years in. One has shipped the same CRUD app with a different framework five times. The other has debugged three production outages at 3am, made the wrong call twice, and changed how they approach systems because of it. Same title. Different engineer.

What actually separates them isn't the five years. It's what happened during those five years — specifically, how many times they were wrong in a way that cost something, and what they did with that.

A junior engineer writes code that works. A senior engineer writes code that keeps working after they stop thinking about it — after the team scales, after the requirements shift, after someone else has to touch it at 2am without them in the room. That's not a skill you accumulate by writing more code. It's a skill you accumulate by watching code fail and tracing the failure back to a decision you made.

The real distinction is judgment under ambiguity — knowing which problems deserve three hours of upfront thinking and which ones deserve to be shipped rough and fixed later. Juniors either over-engineer everything out of fear or under-engineer everything out of confidence. Both come from the same place: no track record of consequences to calibrate against.

Give a junior and a senior the same vague ticket — "improve checkout conversion." The junior asks what to build. The senior asks what's actually broken, whether the metric is even the right one, and whether this is worth building at all. That instinct doesn't show up in a title. It shows up in the fourth question they ask before writing a line of code.

None of this requires a decade. Some engineers hit that judgment at three years because they sought out the hard problems, took ownership of things that could fail publicly, and paid attention when they did. Some engineers never hit it at twelve years because every job stayed comfortable enough to avoid being wrong at scale.

This matters beyond semantics. Companies that promote on tenure end up with senior engineers who've never made a consequential call, and staff-level engineers doing the actual judgment work three levels below their title. The org chart lies. The work doesn't.

If you're hiring, stop trusting the title on the resume. Ask what they were wrong about, and what changed after.

If you're the one with five years and a senior title, the question isn't whether you've earned it. It's whether you've been wrong about something that mattered, and whether you'd make the same call again.

The title is a proxy. Stop optimizing for the proxy.