How to Ask for a Raise (Without It Feeling Like a Negotiation)

You schedule the 1:1. You rehearse your talking points. You walk in, say the words, "I'd like to discuss a raise," and your manager pauses, nods politely, and says some version of "Let me see what I can do."

Then nothing happens.

The problem isn't the script. There are a thousand articles that will give you a script. The problem is that by the time you're rehearsing what to say, you've already skipped the part that actually matters. Engineers who get the raise they ask for almost never describe a negotiation. They describe a conversation where the outcome already felt inevitable, because they spent months building the case before they ever brought up money.

Why the cold ask doesn't work

Most raise advice treats the conversation as the main event: prepare your talking points, pick the right time, use confident body language, don't blink first.

That framing is borrowed from job-offer negotiation, where it makes sense. You have leverage (a competing offer or the threat of walking away), the company has a defined budget, and both sides know the clock is ticking.

Asking your current manager for a raise is a fundamentally different situation. There's no external deadline. There's no competing offer (usually). And the person you're talking to isn't a recruiter with a budget to close a deal. They're someone who has to go argue for your raise to people above them, using evidence they may or may not have.

When you walk into that conversation cold, without months of groundwork, here's what your manager is actually hearing: "I want more money, and I need you to go fight for it in a room full of people who may not know my work."

That's a hard ask for anyone, even a good manager. Not because they don't believe you deserve it. Because they don't have the ammunition to win the argument.

What engineers who get raises actually do

The pattern across Reddit threads, Team Blind discussions, and engineering career forums is consistent. Engineers who get meaningful raises (not just the annual 3-4% cost-of-living bump) don't start with the conversation. They start 3 to 6 months earlier with three things that make the conversation almost unnecessary.

They document wins as they happen

Not in bulk the week before they ask. Throughout the year, as each win occurs.

This sounds obvious. Almost nobody does it. The Ebbinghaus forgetting curve shows that people forget roughly 70% of new information within a month without reinforcement. By the time you sit down to make your case, most of what you actually accomplished has faded, from your memory and your manager's.

Engineers who get raises keep a running log:

• What you did: the specific project, fix, or initiative
• What changed because of it: the measurable outcome (latency reduced, incidents prevented, revenue protected, team unblocked)
• Who saw it: which stakeholders, teams, or leadership were affected

This log isn't a performance review. It's the raw material your manager needs to make a case to their boss. Without it, they're reconstructing your contributions from memory, and memory is unreliable.

They have career conversations before asking for money

Understanding where you want your career to go, and what level you're building toward, shapes how you frame the raise conversation. Career pathing for software engineers helps you get that clarity before you walk into the room.

A 2023 survey by INTOO and Workplace Intelligence found that 46% of employees say their manager doesn't know how to help them with career development. That number gets worse when the conversation is specifically about compensation, because most managers are never trained to have it.

Before you bring up money, you need to bring up goals. Specifically:

• "I want to talk about what growth looks like for me on this team over the next year."
• "What would I need to demonstrate for you to feel confident advocating for a compensation adjustment?"
• "Can you help me understand how raise decisions get made here: who's involved, and what they look at?"

These conversations accomplish two things. First, they make your ambition visible. Your manager can't advocate for something they don't know you want. Second, they give you the actual criteria. The process for getting a raise is different at every company, and most engineers never ask how it works at theirs.

One Team Blind commenter captured the shift:

"The moment I stopped hinting and started asking direct questions about what it would take, my manager went from vague encouragement to actually mapping out a plan with me."

They build the case in their manager's head before the ask

By the time you say "I'd like to discuss a raise," your manager should already be thinking "Yeah, that makes sense." If it comes as a surprise, you've waited too long to start.

The mechanism is simple: in your regular 1:1s, you give your manager the framing they'll need to fight for you in the room where raise decisions happen. Not all at once. In small, specific updates over months.

"The migration I led finished ahead of schedule. It cut the team's deploy time from 40 minutes to 12. Want to make sure you have that context."

"The customer escalation last week: I handled the root cause analysis and the fix. Support confirmed the issue hasn't recurred."

Short and outcome-framed. You're giving your manager ammunition for the conversation they'll have on your behalf when the time comes.

The timeline: when to do what

Most engineers treat the raise conversation as a single event. It's a sequence.

3-6 months before you plan to ask:

• Start or intensify your win log. One entry per week minimum.
• Have the career conversation: what does growth look like, how do raise decisions work here, what criteria matter.
• If your manager can't articulate the criteria, that's important information. It means you may need to research it yourself through HR, internal documentation, or colleagues who've navigated it before.

1-2 months before:

• Compile your evidence. Three to five of your strongest wins from the past six to twelve months, each framed as an outcome with a measurable result.
• Research market data. Levels.fyi, Glassdoor, and Blind compensation threads give you a realistic picture of what your role pays at your level and location. This isn't to wave at your manager as a threat. It's to ensure you're asking for something reasonable and defensible.
• Test the water in a 1:1: "Based on the work I've been delivering and where I sit relative to market, I'd like to have a conversation about my compensation in the next few weeks. Would that be appropriate timing?"

The conversation itself:

• Lead with impact, not need. "Over the past year I led the payments migration and the alerting overhaul, which cut deploy time by 70% and reduced on-call noise. Based on that and where market rates are for this role, I'd like to discuss a compensation adjustment."
• Your manager's response will tell you where you stand. If they agree and commit to next steps, you did the groundwork right. If they say "let me see what I can do," ask the follow-up: "What would make this easier for you to take forward? And what timeline should I expect?"
• If the answer is no, ask what would need to change. A clear no with specific criteria is more useful than a vague maybe that goes nowhere.

Raise vs. promotion: know what you're actually asking for

Engineers regularly conflate these, and it matters.

A raise is a pay increase within your current role and level. It's typically justified by market data, increased scope, or sustained performance above expectations. At most tech companies, there's a compensation band for each level, and a raise moves you higher within that band.

A promotion is a level change: new title, new scope expectations, and a compensation adjustment that comes with it. Promotions are decided through calibration and typically require evidence that you're already operating at the next level.

The distinction matters because at many companies, especially larger ones, there's a ceiling on how much you can earn at a given level. If you're already near the top of your band, the answer to "can I get a raise" might genuinely be "not without a promotion." In that case, the conversation you actually need to have is a different one: about what's keeping you at your current level and what demonstrating the next level looks like.

If you're not sure which conversation you need, ask your manager or HR: "Am I near the top of the compensation band for my level?" The answer will clarify whether you need a raise conversation, a promotion conversation, or both.

What trips engineers up

Asking based on tenure instead of impact. "I've been here for three years" is not a case for a raise. It's context. The case is what you've delivered, what changed because of your work, and why the company should invest more in retaining you. Time served without documented impact is the weakest possible position to negotiate from.

Comparing yourself to a coworker. Even if you know someone at your level is making more, leading with "So-and-so makes more than me" puts your manager in an awkward position and shifts the conversation away from your value. Make the case on your own merits. Market data is fine. Individual comparisons are not.

Waiting for your manager to bring it up. According to a survey published by Fast Company, 58% of employees are afraid to ask for a raise. The most common reasons: they don't know how to start the conversation (32%), they're afraid of hearing no (28%), and they're worried about job security (22%). Meanwhile, research consistently shows that no one gets fired for asking. What happens when you don't ask is that your compensation quietly drifts below market while your employer assumes you're satisfied.

Threatening to leave without meaning it. If you have a competing offer and you're genuinely willing to walk, that's leverage. If you're bluffing, your manager will eventually call it. And once you've played that card and stayed, your credibility in future conversations drops significantly.

Asking without knowing how the process works. Raise decisions at most companies don't happen in a vacuum. There are budgets, approval chains, and timing windows. If you ask at the wrong time (right after a budget cycle closes, or during a hiring freeze), even a supportive manager may not be able to do anything. Ask how the process works before you ask for the outcome.

The real leverage isn't a competing offer

The most effective raise conversations don't feel like negotiations because they aren't. They feel like the obvious next step after months of documented impact and a manager who already knows what you've done.

The engineer who walks in cold and asks for 15% is making a bet. The engineer who has spent six months building a case their manager can't ignore is collecting on a bet they already won.

Research backs this up: 66% of people who negotiate their compensation get what they ask for. But that number obscures an important detail. The people who succeed aren't smoother talkers. They walk in with six months of documented wins and a manager who already agrees.

If you're sitting there thinking "I deserve more but I don't know how to ask," the honest answer is that asking is the easy part. The hard part is the months of groundwork that turn a request into a formality.

---

CareerClimb tracks your wins throughout the year and builds your case automatically, so by the time you're ready to ask for a raise, you have the evidence to back it up. Your AI coach Summit helps you prepare for the conversation and frame your impact in terms that resonate with decision-makers. Download CareerClimb