Giving a Promotion That Actually Sticks

The worst promotion I ever handed out looked perfect on paper. Strong engineer, three years of shipping, well-liked, ready for the title. I gave him the Senior label in a Friday one-on-one, we shook hands, and eleven weeks later he resigned. When I asked why, he said the promotion had felt like the finish line, and once he crossed it nothing was different except a slightly bigger number and a lot more people expecting things he had never been taught to do.

That stung, because it was my failure, not his. A promotion is not a reward you staple onto someone at the end of a good year. It is a change in what the organization asks of a person, and if you do not actually change the work, the support, and the story around them, the title peels off within a quarter. Here is what I have learned about making one stick.

A Promotion Should Confirm, Not Predict

The single biggest mistake I see, and one I made for years, is promoting someone into a level they have not yet demonstrated and hoping the title pulls the performance up behind it. It almost never works. You are asking someone to grow under the glare of a new set of expectations, in public, with an audience that now assumes they already operate at that level. That is a terrible place to learn.

My rule now is simple and slightly unpopular: by the time I promote you, you should have been doing the job for a few months already. The promotion ratifies a reality that your peers have quietly noticed. When I made a mid-level engineer a tech lead last year, she had already been running our payments reconciliation project standups, unblocking two other engineers, and catching a subtle idempotency bug in a refund flow that would have double-credited merchants. The title was a formality. Nobody blinked, because the room already treated her that way.

This is harder than it sounds because it requires you to give people stretch work before there is a title attached to it, and to protect them if the stretch goes sideways. But the alternative, promoting on potential and hope, is how you end up with the Friday handshake and the eleven-week clock.

Write Down What Changes, Concretely

Most people cannot tell you the difference between a mid-level and senior engineer at their own company. Ask ten engineers and you will get ten answers, most of them about years or vague words like "ownership." If the person being promoted cannot articulate what is now different, the promotion is decorative.

Before I promote anyone, I sit down and write, in plain language, the three or four behaviors that define the new level and are genuinely different from the old one. Not "more ownership." Something like: leads the design review for changes that touch the ledger, is the person on-call escalates to at 2am, mentors at least one junior through a full feature. Then I read it out loud to the person and we talk about which parts they already do and which parts are the growth edge.

The clearest sign a promotion will stick is that the person can repeat back, in their own words, exactly what they are now on the hook for. If they can only repeat the title, you have given them a hat, not a job.

The Money Matters, But It Is Not the Message

Let me be blunt about compensation, because a lot of leadership writing tiptoes around it. A promotion with a trivial raise is an insult dressed as a gift. I have seen companies hand out Senior titles with a two percent bump and then act surprised when the newly minted seniors start interviewing elsewhere. If the market pays a senior engineer meaningfully more than a mid-level one, and it does, then your raise has to close a real part of that gap or the title is just extra work at the old price.

That said, money alone does not make a promotion feel real either. I have watched engineers get a genuinely good raise and still feel hollow about it, because nothing about their days changed. The compensation confirms that the company is serious. The change in work confirms that the promotion means something. You need both. When I fixed our process, I started aligning every promotion to a compensation band we published internally, so the number was defensible and not a negotiation about who complained loudest.

Tell the Team, and Tell Them Why

A promotion delivered in a private one-on-one and never mentioned again is a promotion the organization does not know happened. That matters more than it should, because a title change is partly a social contract. The team needs to know that when they escalate something to this person, they are escalating to someone with a mandate.

So I announce promotions, and I say specifically what the person did to earn them. Not "please join me in congratulating," which is corporate wallpaper. Something concrete: she rebuilt our webhook retry logic and cut failed merchant notifications by roughly eighty percent, and she has been the calm one in three incident bridges this quarter. Two things happen when you do this. The promoted person feels genuinely seen, and everyone else gets a real, legible example of what the bar looks like. That second effect is worth as much as the first.

Engineer the First Ninety Days

The window where a promotion sticks or slides is the first three months. This is where my Friday-handshake engineer was failed most badly. I gave him the title and then vanished, assuming that a senior engineer, by definition, did not need help. That is exactly backwards. The moment someone steps up a level is the moment they need the most scaffolding, because everything they are doing is new to them even if it looks routine to everyone else.

Now I treat the first ninety days as a deliberate ramp. A few things I do without fail:

• Hand them one visible, bounded piece of the new-level work in week one, so the promotion becomes real through action, not memory of a conversation.
• Increase our one-on-one frequency for a while, rather than decreasing it, and use that time to coach the new behaviors specifically.
• Publicly route the kind of work that fits the new level toward them, so the rest of the team recalibrates who does what.
• Warn them, in advance, about the specific way people at this level tend to stumble, so the first hard moment feels expected instead of like proof they were not ready.

None of this is expensive. It is mostly attention. But attention is the thing leaders quietly withdraw right when a promoted person needs it most, because we have mentally filed them under "handled."

Do Not Promote a Great Engineer Into a Job They Never Wanted

One of the most expensive mistakes in our field is assuming the reward for being an excellent engineer is to stop being one. I have watched brilliant builders get pushed into management because it was the only path with a bigger title and more money, and within a year we had lost a great engineer and gained a miserable, mediocre manager. Two failures for the price of one.

If you want promotions to stick, you need a technical track that goes as high as the management track, with the same pay and the same status, and you need to genuinely mean it. A Staff or Principal engineer should be able to out-earn a line manager without apology. When someone comes to me about their next step, my first question is not "are you ready" but "which kind of harder do you actually want," because deep technical work and people leadership are different jobs, not different rungs of one ladder. Promoting someone sideways into work they resent is a promotion that unravels slowly and painfully.

Resist the Panic Promotion

Here is a scenario every leader knows. A strong engineer gets an offer elsewhere, or drops a hint that they might, and suddenly a promotion that was "not quite yet" a month ago materializes overnight. I understand the impulse. Losing good people hurts, and it is expensive. But promotions handed out under duress corrode the whole system, because everyone learns that the fast path up is to threaten to leave.

I am not saying never move quickly. Sometimes a counteroffer is genuinely the right call because you were slow and the market corrected you. But the discipline is to ask whether this person had already earned the level or whether you are buying a few months of retention with a title you will regret. If it is the latter, you are better off matching compensation as a retention move and keeping the promotion honest for when it is actually deserved. I have paid to keep someone without promoting them, told them exactly why, and had it land as more respectful than a hollow title would have.

Separate Performance Reviews From Promotion Decisions

When promotions get bundled into the annual review cycle, they turn into a rushed negotiation happening under a pile of other conversations about goals and ratings and next year's objectives. The promotion, which deserves the most careful thought, gets the least, because it is competing with a dozen other agenda items and a calendar deadline.

I pulled promotion decisions out of the review cycle entirely. We discuss readiness continuously, and we act when someone is genuinely operating at the next level, whatever month that happens to be. This has two benefits. Promotions land close to the work that earned them, so the connection is obvious to everyone. And I am never in the position of promoting someone in December because the window is closing rather than because they are ready. A promotion timed to a calendar is a promotion timed to the wrong thing.

The Word Is the Easy Part

I still think about the engineer who quit after eleven weeks. He was right to leave. I had handed him a word and called it a promotion, and a word cannot teach you to run a design review or hold your nerve on an incident bridge at 2am. The scaffolding I skipped was the actual gift, and I kept it in my pocket while congratulating myself on my generosity.

Here is what I would tell the version of me standing there after that Friday handshake, feeling like a good boss. A promotion you can deliver in five minutes is almost always a promotion that will fail. The five minutes are the ribbon. Everything that makes it real happens in the months on either side, and most of that work is quiet, unglamorous, and easy to postpone because nobody will notice you skipped it until the resignation lands. Give someone the job first, then the word, then a year of actually showing up for the harder version of it. Do it in that order and the title becomes the least interesting thing in the room, which, oddly enough, is the surest sign you did it right.