Negotiating your first raise: scripts and timing

You’ve been at the job a year. You’ve shipped real work. You’ve heard the words “great job” a few times. Nothing has happened to your paycheck.

A raise rarely shows up because you deserve one. It shows up because you asked at the right time, with the right framing, in the right room.

The framing that wins

A raise is not a favor. It’s a decision your manager has to justify upward — to their manager, to HR, to a budget. Your job is to make that justification easy.

The raise conversation is not “here’s why I deserve more.” It’s “here’s the business case my manager can forward.”

When to ask

Three windows work. Everything else is a coin flip.

1. The formal review cycle. If your company has one, that’s the window. Asking outside of it usually means “we’ll consider it at the next review,” which is a polite no.
2. After a visible win that changed something. You shipped the thing. A metric moved. A VP noticed. Ask within two to four weeks. Memory fades.
3. When you take on scope that was above your level. You backfilled a role. You led a project that used to be your senior’s. The gap between your work and your title is the argument.

Bad timing: right after a bad quarter, during layoffs, the week your manager is underwater, or before you’ve accumulated six months of work they can point at.

The prep

Walk into the conversation with three things.

1. A short list of your contributions, in outcomes. Not “I worked on X.” “I shipped X. It did Y. The impact was Z.”

Five to eight bullets. Keep each one under a line.

2. A benchmark. What are people at your level, at comparable companies, in your market, making? Levels.fyi, Glassdoor, the 2024 or 2025 salary thread in your industry’s subreddit, a trusted peer at a competitor. You don’t need a perfect number. You need a defensible range.

3. A specific ask. Don’t say “more.” Say “$X” or “a Y% increase.” Specific asks get specific answers. Vague asks get deferred.

The conversation

Do this in a scheduled 1:1, not a drive-by. Email the subject line a day or two before:

“For our next 1:1, I’d like to talk about my compensation. Wanted to flag it so you have context going in.”

That’s it. Don’t explain in email. The conversation is the point.

The opening script

“I’d like to talk about my comp. I’ve been at [role] for [time]. Over the last [period], I [two or three biggest wins, in outcomes]. Given the scope I’m now carrying, I’d like to discuss a base increase of $X / Y%.”

Three parts: context, evidence, ask. In that order. Short.

Now stop talking.

A lot of people ruin the ask by filling the silence with hedges. “I know budgets are tight…” “I don’t want to make this awkward…” Don’t. Let your manager respond. Their job now is to think.

What you’ll hear, and how to respond

“Let me look into it.” Good. Close the loop:

“Thanks. When can we follow up — next 1:1, or two weeks?”

Make it a commitment, not a vibe.

“The budget is set for this cycle.” Fine. That’s an answer, not the end.

“Understood. What would it take to be considered in the next cycle? A specific project, a title change, a scope expansion — I’d like to know what to aim at so we’re aligned.”

“I can’t do the full amount. I can do half.” That’s a yes. Take it, and anchor the rest:

“I appreciate that. Can we put the remaining gap in writing as part of the next review, tied to [specific outcome]?”

“This isn’t the right time.” Translate that. “Not the right time for you,” or “not the right time for me”? Ask:

“Is that about company budget, or about where I am in the role? If it’s about me, I’d like to understand what would change that.”

Silence. If you don’t hear back in two weeks, bring it up again. Once. Not every 1:1.

The answer you can’t let slide: a polite no without a path

If your manager tells you no and won’t give you a path — no timeline, no metric, no scope change that would trigger a yes — they’re telling you something about the ceiling of this job. That’s a data point. File it.

Give it three to six months. If the ceiling holds, start looking. The biggest comp jumps in early career come from switching jobs, not from waiting.

What new grads get wrong

Asking in a group setting. Comp is a 1:1 conversation. Always.

Leading with personal finance. “Rent went up” is not an argument. Your manager isn’t setting your pay against your expenses.

Threatening to leave without being ready to leave. If you float a counter-offer, be ready to take it. Once you’ve said “I might leave,” the relationship changes.

Apologizing for asking. Don’t. You’re running your career.

Asking for a title change as a substitute for money. Titles are cheap. Make sure the title comes with the money, or at least a clear path to it.

If you’re the manager on the other side

The best thing you can do for a junior’s career is give them the truth. If the raise isn’t possible, say why, and tell them what would change that. If they’re not ready yet, tell them exactly what “ready” looks like. A vague “we’ll see” is the worst outcome — it trains them not to trust you, and not to negotiate elsewhere either.

Edge cases

• Unionized roles or fixed pay bands: the conversation is about moving bands or hitting the top of your band early. Ask what the criteria are, in writing.
• Startups with equity-heavy comp: push on refreshers, not just base. A grant from two years ago is already vesting; you want new paper tied to current scope.
• You got promoted but the raise was small: fine to say so. “I appreciate the promotion. The comp increase feels below market for the new scope. Can we revisit?”

Do this today

Open a doc. Write down your five biggest contributions in outcome form (what shipped, what moved, what the impact was). If you can’t fill five, you’re not ready yet — build the case for another quarter.

If you want the weekly habit that builds a raise case without anyone noticing, use the Status update template. For the calibration conversation that precedes the raise conversation, steal the Manager 1:1 agenda.