How to Ask for a Promotion When You Are Already Doing the Job

"I feel like I'm ready for the next level."

It is the most common opening line in a promotion conversation, and it gives the decision away in eight words. You have asked your manager to rule on how you feel about yourself. They can agree, disagree, or say the level takes time, and all three cost them nothing.

Readiness is an opinion, and opinions get postponed. What is harder to postpone is a fact: the work you are doing now sits at the next level, and your title has not caught up.

That is the argument. The rest is how to make it out loud, to a person who then has to repeat it in a room you will never sit in.

A promotion is not a raise with a better title

They feel like the same conversation. They are not, and treating them as one is how good cases die.

A raise is an argument about price: the market pays a number for the job you do, and you are under it. It gets settled between you, your manager and a budget line. Asking for a raise is a two-person negotiation that ends in a figure.

A promotion is an argument about scope, and it is not decided in your one-on-one. Your manager leaves your meeting and walks into a different one: a calibration, a leveling review, a skip-level and an HR partner comparing you against every other candidate. You are not there. Your case gets made in four minutes, from memory.

So you are not really persuading your manager. You are writing the four minutes they deliver without you.

Ask before you feel ready

Most people wait for a feeling that never arrives on schedule, then ask two weeks before promotions are announced, which is two weeks after they were decided.

Look at the real timeline. You ask. Your manager checks the ladder and writes the case up, a couple of weeks in a good month. Calibration runs on the company's calendar, not yours. A yes usually takes effect at the start of the next cycle. Three to six months from your sentence to your title is normal.

So ask while you still feel slightly short of the bar. The gap between "I could do that job" and "I have visibly been doing that job" is about the length of the process anyway.

The people who get promoted are rarely the ones who were most ready on the day. They are the ones whose manager had been arguing for them for two cycles.

The evidence: three pieces of work that belonged to the next level

Your evidence is not a list of accomplishments. A list of accomplishments proves you are good at your current job, which is an argument for leaving you in it.

You need three examples, and each one has to be work that belonged to the level above yours. One is an anecdote, two is a coincidence, five stops being memorable.

Something you owned end to end that nobody assigned you. Scope you took, not tasks you finished. "The vendor migration had no owner in January. I ran it, including the legal review, and it shipped in March."

A judgment call you made above your level, that held. The next level is mostly deciding without asking. "When the client changed the spec in week six I cut the reporting module rather than move the date. They signed off. I didn't escalate it."

Something that moved other people. Above your level the work happens through other people: a standard you set in reviews, a process two teams now use, an engineer who is better because you insisted.

Then say the level in your company's own words. If the ladder says a senior "leads work across team boundaries," use that phrase and hang an example on it. Your manager is arguing against a written rubric: hand it over already filled in.

Your manager has to argue this without you in the room

Once you know the decision happens elsewhere, the goal of the meeting changes. You are not there for a verdict. You are recruiting an advocate, and an advocate needs supplies. Three things, in a form they can carry.

• The three examples, on one page. Sent after the meeting, short enough to read in the two minutes before calibration, with the exact title you want at the top.
• The counterargument, answered. Every case has a weak spot and your manager will hear it in that room. Name it first: "The obvious pushback is that I haven't run anything with a hard external deadline. The vendor migration is the closest, and I'd take the next one."
• A comparison. Who already at that level does work that looks like yours? Naming a peer feels risky. It is also the most useful thing you can hand somebody about to sit in a comparison meeting.

The script

Book it as its own meeting, with a subject line that says what it is. "Career conversation, 30 minutes." Not the last five minutes of your regular one-on-one.

Four moves, under two minutes.

The third move does the work. "Will you put me forward?" is answerable and creates a record. "Do you think I'm ready?" turns your manager into a judge, and the cheap answer for a judge is "let's keep developing that."

The three answers you will get

"Not this cycle"

Usually true and usually not about you: headcount, a cap on promotions per team, somebody ahead of you in the queue. Take it at face value and spend the rest of the meeting on the next cycle.

Send three lines by email that afternoon confirming what you asked for and the date you agreed. Not pressure, a record. Teams get reorganized, and the version that survives is the written one.

"You are not there yet"

"Not there yet" is not feedback. It is a summary of feedback that was never said out loud. Your job for the next four minutes is to turn it into a specification: a named gap, a picture of what closing it looks like, and a date.

If the gap is a named piece of work, ask for that work in the same meeting. If it is "presence" or "maturity" or "more visibility," push once: "What would I be doing differently on a Tuesday?" If nothing concrete arrives after a week, you have learned something unpleasant and useful. The ceiling here is not about your performance.

The vague positive

"You're absolutely on the radar." "This is definitely on my mind." "Keep doing what you're doing."

Dangerous because it feels like a yes. It commits nobody, it dies quietly, and six months later you find out it was never written down. Convert it before you leave the room.

If the answer is yes, you have something to confirm in writing. If it softens into "let's see how the quarter goes," the real answer was "not this cycle," and you can work that branch instead.

The offer you should not lead with

The temptation, especially right after a no, is to add weight. "I should mention I've been approached by a couple of companies."

Do not, for a mechanical reason more than a moral one. A promotion needs somebody to argue for you warmly, in a room, weeks after you left it, and an implied threat does not produce that. It produces a retention decision: sometimes money, rarely a level, always a quiet note that you are a flight risk. Flight risks do not get the stretch project, and the stretch project is how the next case gets built.

If you are bluffing, the reply is "oh, who?" There is no good version of the next ten seconds.

If the offer is real and you would take it, it is not leverage, it is news. Give it its own conversation, with a number, a deadline and no theater. Settle the title on its own evidence and handle the money as its own negotiation.

This does not work if the level you want does not exist yet. Asking for a title that has no headcount attached puts your manager in the position of arguing for a new box on an org chart, which is a different conversation and a much slower one. Ask first whether the role exists, then whether you are the candidate.

Why this is harder out loud

All of this reads as obvious sitting down. It is different at 2:40 on a Thursday, when a slot has opened up and your director says "so, what did you want to chat about?"

What goes wrong is not the content. It is that "I want to talk about moving to senior" comes out as "I wanted to maybe start a conversation about where I'm heading." The hedges arrive on their own, because naming the level to the person who decides it is a claim about yourself, and claims about yourself are uncomfortable at normal volume.

More preparation does not fix that. Having said the sentence before does. Out loud, to somebody who pushes back, enough times that it comes out flat instead of tilting up at the end like a question. In your head your manager nods, and you never have to produce the third example while somebody looks unconvinced.