How to Ask for a Raise: Scripts, Timing & What Actually Works

Most people ask for raises wrong. They wait too long, say too little, or lead with the one argument that managers are trained to deflect: "I need more money." The result is an awkward conversation that ends with "let me think about it" and nothing changes. This guide is the antidote. Whether you're a senior engineer eyeing a principal title bump or a mid-level contributor who hasn't seen a meaningful raise in two years, the mechanics here apply. Follow them and you'll walk into that conversation with evidence, timing, and language that actually works.

The Single Biggest Mistake: Asking at the Wrong Time

Timing is not a soft variable. It is probably the highest-leverage factor in whether your ask succeeds, and most people get it completely wrong by treating it as an afterthought.

Here's when raises actually get approved:

• During or just before performance review cycles. Most companies have a fixed compensation budget that gets allocated during review season. If you ask after that budget is already committed, your manager is literally unable to help you without going through an exception process that almost nobody does.
• Right after a visible win. You just shipped something that moved a real metric, saved real money, or unblocked a major initiative. Your value is at its most concrete and recent. Strike within 2–4 weeks.
• When you have a competing offer. The nuclear option. It works, but read the section below before you use it.
• When the company is doing well. Asking for a raise during a hiring freeze or after a bad earnings call is not impossible, but you're fighting the current. Ask when budgets are expanding.

The worst time to ask: the week before a review cycle ends, when budgets are already locked; during a team reorg; or immediately after a high-profile incident your team owns.

If you're at a company like Amazon, Google, or Microsoft, find out when the compensation planning window opens — usually 6–10 weeks before reviews are delivered — and have your conversation before that window closes. Your manager needs time to advocate for you inside the system.

Build the Case Before You Open Your Mouth

Your manager does not decide alone. They write a case that goes to their manager, sometimes to HR, and sometimes to a calibration committee. Your job is to make their job easy. Give them the ammunition.

The evidence that actually moves the needle, ranked:

1. Quantified business impact. "I reduced infrastructure costs by 20% through auto-scaling optimization" is a raise argument. "I worked on the infrastructure team" is not. Put numbers on everything you can. Revenue influenced, cost saved, latency reduced, incidents prevented, users unblocked.
2. Scope expansion. Are you doing work that's above your current level? Mentoring engineers, leading cross-functional projects, making architecture decisions that used to belong to someone more senior? Document it explicitly.
3. Market data. Levels.fyi, Glassdoor, Blind, and LinkedIn Salary are your friends. Come in with a range for your title, level, and geography. In Vancouver doing remote U.S.-company work in 2026, know both the CAD and USD comps for your role.
4. Peer comparisons (use carefully). "I know people at my level are making X" works if you have real data. It backfires if you sound like you're complaining about a colleague's salary.
5. Competing offers. Real, usable offers. Not "I'm interviewing" — actual numbers on paper.

Build a one-page brag document before the conversation. Bullet points, numbers, dates. You don't hand it to your manager, but you use it to prepare, and you can follow up with it in writing after the verbal conversation.

The Script That Actually Works

Stop improvising. The conversation you've been rehearsing in your head — where you wait for the right moment and it organically comes up — doesn't happen. Schedule it explicitly. Send a calendar invite titled "Career Development Discussion" or "Compensation Check-In." Don't ambush your manager at the end of a 1:1.

Here's a script you can adapt:

"I wanted to have a direct conversation about my compensation. Over the past [X months/year], I've [2-3 specific accomplishments with numbers]. I've also taken on [expanded scope — mentoring, architecture decisions, cross-team leadership]. Based on what I know about the market for senior engineers at this level in [your location/remote context], and the scope I'm operating at, I think my current comp is below where it should be. I'd like to discuss a [specific number or percentage] increase. I want to be a long-term contributor here, and I think getting this aligned is important for that."

Four things this script does that most people skip:

• It opens with intention, not with an apology or a hedge.
• It leads with value delivered, not personal need.
• It anchors to a specific number (say it — don't make your manager guess).
• It closes with commitment, not a threat.

"The biggest mistake engineers make is asking for a raise without a number. Vague asks get vague answers. Say the number out loud."

When they say "let me think about it" — which they will — you say: "I appreciate that. Can we schedule a follow-up in two weeks to close the loop?" Get a specific date. Ambiguous timelines are where raise conversations go to die.

What to Do When They Say No

A no is not the end of the conversation. It's the beginning of a negotiation about what a yes requires.

The right response to a no:

1. Don't accept it passively. Ask: "I appreciate the honesty — can you help me understand what's driving that? Is it timing, budget, or scope?"
2. If it's timing or budget: "What would the timeline look like if we revisit this in Q2?" Get a specific commitment.
3. If it's scope: "What would I need to demonstrate over the next six months to make this a clear yes?" Make them define the criteria explicitly. Then send a follow-up email summarizing what they said. This creates accountability.
4. If it's a pattern: Three nos with no clear path forward is information. Your compensation ceiling at this company may be lower than your market value. Start interviewing.

The one thing you should not do after a no: go quiet, feel demoralized, and wait for the next review cycle with no changed strategy. That's how engineers end up 30% below market and wonder how it happened.

The Competing Offer Play: Powerful but Risky

A real competing offer is the single most effective raise lever that exists. Companies that won't move on comp for internal reasons will find budget when retention is on the table. This is a real dynamic, not a myth.

But it has costs:

• You must be willing to take the offer. If you bluff and they call it, you either leave or you've permanently damaged trust with your manager. Only use this when you have a real offer at a real number you'd actually consider.
• Your manager's perception may shift. Some managers see it as loyalty leverage. Others see it as a signal that you're already mentally out the door. Know your manager.
• Counter-offers are short-term patches. Data consistently shows that people who accept counter-offers leave within 12–18 months anyway, because the underlying dynamic that put you below market hasn't changed.

If you use the competing offer play, frame it constructively: "I've received an offer for X. I'd rather stay here — I'm invested in this team and this work. Is there a path to getting close to that number here?" That's not a threat. It's information delivered professionally.

Equity, Bonuses, and Total Comp: Don't Negotiate in a Silo

Base salary is not the whole game, especially in tech. If your company can't move base salary — common in large companies with rigid bands — push on:

• Equity refresh grants. Amazon, for example, caps base salary and leans heavily on RSUs. If you're due for a refresh, make the case explicitly. A well-timed equity ask can easily be worth more than a base raise.
• Signing bonus equivalents / retention bonuses. Not common, but real. If a company can't adjust your band, sometimes they'll offer a one-time payment.
• Accelerated vesting or grant cliff adjustment. Rare, but worth asking if you're pre-cliff.
• Title bump without immediate comp change. If you're operating at principal level, getting the title first unlocks the comp band. Sometimes the title move is the negotiation.
• Non-cash levers: additional PTO, remote work flexibility, conference budget, professional development stipends. These have real dollar values.

Know your total comp number before you walk in. Stock value at current price, expected bonus, benefits. You need to know your all-in number to negotiate intelligently.

How Senior Engineers Should Think Differently About This

If you're at the senior or staff level, the raise conversation works differently. You're not just demonstrating output — you're demonstrating organizational impact and leverage.

At senior+ levels, the arguments that work are:

• You're operating above your level. If you're a senior engineer doing principal-level work — leading architecture decisions, mentoring multiple engineers, driving cross-org initiatives — document that and make the case for a title upgrade with comp to match. Scope is the argument, not tenure.
• You're absorbing risk. Senior engineers who own critical systems, who are the single point of expertise on high-traffic infrastructure, or who have been the de facto tech lead without the title have real leverage. Make that leverage explicit.
• You're a flight risk. This is the honest version of the competing offer argument. You don't need to have an offer in hand to note that you're being approached regularly. You can say: "I want to be direct — I'm getting recruiting interest at the [principal/staff] level, and I think it's worth having this conversation before it becomes a real decision."

For engineers targeting principal or staff roles in 2026: total compensation benchmarks in the $300K–$500K+ USD range (including equity) are realistic at top-tier tech companies for the right scope. Don't undersell. Levels.fyi is your ground truth.

Next Steps

Don't let this guide become content you consumed without acting on. Here's what to do in the next seven days:

1. Identify your asking window. Find out when your company's compensation planning cycle opens. If you don't know, ask your manager directly: "When is the window when comp decisions get made for the next review period?" You need this date.
2. Build your brag document. Spend 45 minutes writing down every quantifiable win from the last 12–18 months. Revenue impact, cost savings, latency improvements, incidents resolved, engineers mentored. Use numbers. Date everything.
3. Do your market research. Pull comp data from Levels.fyi, Blind, and Glassdoor for your exact title, level, and work location context. Know the 25th, 50th, and 75th percentile. Come in with a specific target number.
4. Schedule the conversation. Send the calendar invite this week. "Career Development Discussion" with your manager, 30 minutes, two weeks out. Don't wait for the right moment — create it.
5. Prepare your follow-up plan. Decide in advance what you'll do if the answer is no. Are you willing to interview? What's your walk-away number? Having this clarity before the conversation means you won't get caught flat-footed and make a decision you regret in the moment.

Related guides

• Visa-Sponsor Comp Negotiation — H-1B, O-1, Green-Card Timing, and the Leverage You Actually Have — Visa-sponsored candidates do have leverage, but it is different from standard offer leverage. This guide covers how to negotiate compensation, immigration support, green-card timing, and written protections without bluffing or risking the offer.
• Bootcamp Grad Salary Negotiation — What’s Actually Negotiable When You Have No Leverage — Bootcamp grads can negotiate, but the playbook is different. Learn what to ask for, what not to bluff, and how to improve an entry-level offer without risking it unnecessarily.
• Competing Offers Negotiation Playbook — Exact Scripts That Lift Your TC by 20-40 Percent — A tactical competing-offers negotiation playbook with exact scripts, sequencing, offer comparison rules, counteroffer structure, and red flags for lifting total compensation without burning trust.
• The Counter-Offer Email: Templates & Scripts That Work in 2026 — Stop leaving money on the table. Here are the exact counter-offer email templates and scripts that land higher salaries in 2026's market.
• Negotiation Scripts That Work in 2026 — Exact Phrasing Recruiters Respond To — Use these recruiter-tested salary negotiation scripts for 2026 offer calls, counteroffers, competing offers, base-versus-equity asks, signing bonuses, deadlines, and lowball packages.