What "Senior Developer" Actually Means

Open any "Senior Software Engineer" posting and you'll find a wishlist of eighteen cutting-edge technologies the candidate must have mastered. Not one item on that list tells you whether the person is actually senior. We've all agreed to use the word, and we've quietly agreed not to define it, which works fine right up until you have to decide whether someone deserves it, or whether to trust the one who already has it.

What this is not

Senior is not years on the clock. I've worked with people who'd been writing code for two and a half decades and still had the toolkit of someone fresh out of their first tutorial, because they'd done year one twenty-five times. I've also worked with developers barely out of university who could see three moves ahead. Time served buys you stories, not seniority.

It is not a tour of technologies at Hello World depth, either. If you've never read past the opening example, never hit a problem where even the internet has only unanswered questions, you don't know the thing. You've met it. A CV with twenty logos on it usually means twenty introductions, not twenty masteries.

It is not the engineer who collects patches and workarounds while quietly terrified of refactoring, because the patches are job security and the refactor is risk. And it is certainly not whoever has the highest salary in the room. That one needs no explanation.

What it actually is

If I'm allowed only one word: problem-solver. Since I'm not limited to one, here's the rest.

A senior owns a feature end to end, and "end to end" is the part that matters: not just writing it, but planning it, testing it, keeping it alive in production long after the demo, and arguing with the stakeholder about whether it should exist at all before a line gets written. They understand the business well enough to push back on it, which juniors rarely can and seniors are negligent not to.

They carry risk on design decisions like it weighs something, because it does. There is always a gap between the design on the whiteboard and the live system it has to survive inside, full of moving parts that have never read your diagram, and a senior feels that gap before they ship into it. On a good day the junior and the senior produce nearly identical code. The tell is what happens on a bad one: the requirements are vague, the system is misbehaving in a way nobody's seen, and there is no answer to look up. That's where the title is earned or exposed: a senior keeps moving through that fog, makes a defensible call without all the information, and absorbs the ambiguity so the people around them can keep working instead of freezing.

Doing it for the people around them is the thing I'd refuse to compromise on, and it has an edge that people hate: the indispensable hero is not senior. The engineer who fixes everything because only they can, who looks heroic precisely because the bus factor is one, is a liability with tenure and good intentions. The fake-senior hoards the knowledge that makes them necessary; the real one gives it away as fast as they can and goes looking for the next hard thing.

There's a quieter version of the same judgment in how they decide. A senior knows which calls are cheap to reverse and which ones aren't. The reversible stuff they decide fast and fix later if it's wrong. The one-way doors, the schema you'll be stuck with for five years, the data migration with no undo, they slow down for, force the conversation on, and own personally when they go ahead anyway, because those decisions quietly set the ceiling on everything built after them. That instinct, for which mistakes are recoverable and which are load-bearing, is most of what experience actually buys.

Underneath all of it is the part no competency grid can score: someone who's made peace with not having superpowers, who can say "I don't know" at no cost to their ego, and who measures people by what they can build rather than by their age, their accent, or who they pray to. So the word will keep meaning whatever the person using it wants it to mean, and the only real protection is to watch what someone does the next time nobody knows the answer.