Quick Answer

At Google, a raise ask succeeds only when it sounds like a calibrated business case, not a plea for recognition. The manager is not deciding whether you worked hard; they are deciding whether your scope, level, and timing justify spending political capital.

1on1 Asking for Raise Script Template for Engineers at Google

TL;DR

The wrong move is to turn a 1:1 into an emotional audit of your effort. The right move is to make the ask narrow, time-bound, and legible: what changed, why it matters, what you want, and when you want an answer.

Use a script that forces a decision path. Not “do you think I deserve more,” but “is this a market adjustment, a promotion-track conversation, or a timing issue?”

Not sure what to bring up in your next 1:1? The 0→1 SWE Interview Playbook (2026 Edition) has 30+ high-signal questions organized by goal.

Who This Is For

This is for engineers at Google who already know they are underpaid, under-leveled, or carrying work that no longer fits their current package. It is also for the person who keeps waiting for the manager to notice, then gets trapped in polite ambiguity for another review cycle.

If you are an L4 acting like an L5, an L5 carrying L6 scope, or someone whose compensation lagged after a role expansion, this is your lane. If your last review was within 90 days and you still do not have a clean evidence trail, the ask is premature. If you can already name the work, the level mismatch, and the date you want a response by, you are ready.

What makes a raise conversation at Google different from a normal 1:1?

At Google, a raise conversation is not a casual check-in; it is a calibration request disguised as a conversation. In a Q3 debrief, the managers who get traction do not argue feelings. They bring interpretable evidence that survives comparison against level expectations and peer scope.

The system is not built around gratitude. It is built around defendable narratives. Not “I have been here a long time,” but “my scope changed in a way that maps to higher impact and higher leverage.” Not “I work hard,” but “I own the thing that failed if I was absent.” That distinction matters because comp decisions at Google are filtered through multiple people, not just your manager’s personal opinion.

The organizational psychology is simple. Managers protect their credibility by bringing proposals they can repeat without embarrassment. If your story sounds fuzzy in the room, it sounds even weaker in calibration. I have seen managers enter a compensation discussion wanting to help, then back away because the engineer could not articulate a clean level-to-scope mismatch in under a minute.

The first sentence should not be a justification dump. It should be a frame. Say, “I want to talk about compensation because my scope has changed materially this half.” That tells the manager this is not a mood. It is a business conversation.

When should I ask for a raise instead of waiting for review?

You ask when your evidence is stronger than the calendar. If you wait for the perfect moment, you usually get the slowest one. The better test is whether your scope change has already happened and whether you can describe it in one clean sentence.

A Google manager will usually take a raise ask seriously when one of three things is true: your ownership expanded across teams, your execution became a dependency for other people, or your role now matches a higher level pattern. If none of those are true, the ask sounds aspirational, not warranted.

Timing still matters. If you are within 30 to 60 days of a review, you can ask, but you should ask for a path, not force a verdict in the room. If your manager says they need to talk to comp or HR, that is normal. Give it 7 calendar days before you nudge. If you get two rounds of “let me check” with no date, treat that as a soft no.

The mistake is waiting for an annual ritual to validate a year of work. Not because the review is useless, but because it is already crowded with competing claims. The ask is easier when it is made after a concrete win, not after you have quietly absorbed resentment for six months.

I have watched this play out in manager conversations: the engineer who waited for “the right review cycle” lost leverage, while the engineer who asked right after shipping a visible scope expansion got a specific next step. The lesson is not to be impatient. The lesson is to ask while the evidence is fresh.

What exact script should I say in the room?

The best script is short, direct, and slightly uncomfortable. If you need to say more than 60 seconds to state the request, you probably do not yet have a sharp enough case.

Use this structure:

“I want to use this 1:1 to talk about compensation. My scope has expanded beyond my current level in three ways: [specific ownership], [specific cross-functional impact], and [specific risk or leverage I now carry]. I am not asking for an answer on the spot. I want to understand whether you see this as a market adjustment, a promotion-track conversation, or a timing issue.”

That script works because it does not beg. It names the category. It also gives the manager an easy way to answer without losing face. Managers at Google respond better when you let them choose the path they can defend.

If you want a number, make it a range, not a lone point. Example wording: “I’m looking for a $15K-$25K adjustment, or the equivalent level correction if that is the cleaner route.” The range is not the point. The point is that you sound like someone who understands comp as an organizational decision, not a bargaining game.

Do not over-explain your loyalty, your stress, or your personal circumstances. Not because those things do not matter, but because they weaken the signal if they become the center of the pitch. The problem is not your sincerity. The problem is your judgment signal.

How do I prove I deserve a raise without sounding emotional?

You prove it by talking in scope deltas, not self-esteem. In a calibration meeting, the engineer who wins is usually the one who can show that the work changed shape, not just that the hours were long.

Give three forms of evidence. First, name the responsibility you absorbed. Second, name the dependency you created for others. Third, name the cost of replacing or delaying your contribution. That is enough. Anything beyond that usually starts sounding like a memorial service for your effort.

Google managers are sensitive to stories that are easy to retell. The strongest comp cases sound like this: “This engineer now owns launch risk across two teams. They resolved the failure mode nobody else wanted. If they left, the team would need a replacement with a higher level of context.” That is not flattery. That is managerial language.

Not “I helped a lot,” but “I owned the bottleneck.” Not “people like me,” but “the team depends on my judgment.” Not “I’ve been busy,” but “my scope now maps to a higher level of accountability.” The more your language resembles an internal memo, the more likely it is to survive the room.

This is where many engineers fail. They present a list of wins that looks impressive in isolation but collapses under comparison. The manager does not need a heroic biography. They need a defendable reason to move compensation outside the default track.

What should I do after my manager says maybe?

You should force a date, or assume the answer is no. “Maybe” is often a polite buffer for a missing sponsor, a bad cycle, or a weak case. It is not a plan.

The right response is calm and specific: “What decision do you need to make, who do you need to consult, and when should I follow up?” That keeps the conversation in the realm of process instead of drifting into vague reassurance. If the manager cannot name the next step, they are not ready to advocate for you.

In real manager conversations, the people who move things forward do one thing well: they make ambiguity expensive. A vague ask can be deferred forever. A dated follow-up cannot. If they say they need to see more impact, ask which metric, which project, and by when. If they say budget is tight, ask whether this should be handled as a promotion case, a market correction, or a revisit next cycle.

Do not keep negotiating in circles. Not “let’s revisit sometime,” but “let’s revisit on May 31 after the launch.” Not “I’ll keep doing good work,” but “I’ll send you a one-page summary of the scope change by Friday.” The point is to turn a soft conversation into a tracked commitment.

If the manager keeps stalling after that, the issue is usually not your script. It is sponsorship. At Google, weak sponsorship is often the real reason raises die quietly. The system rarely says no in a dramatic way. It just stops moving.

Preparation Checklist

Write a one-sentence scope claim before the meeting. If you cannot describe the mismatch between your current level and your current work in one sentence, the ask will sound thin.
Bring three concrete examples from the last 60 to 90 days. Use launches, incidents, or cross-team ownership, not generic effort.
Decide your ask before you walk in. That means a timing request, a comp adjustment, or a promotion-track conversation. Do not improvise in the room.
Prepare one sentence for the likely objections: timing, budget, and “need to see more.” If you have no answer for those, you are not ready.
Send a short follow-up after the meeting with the decision path and date. Ambiguity survives in verbal conversations; it dies in writing.
Work through a structured preparation system (the PM Interview Playbook covers compensation calibration and scope framing with real debrief examples). That is the useful part, not the branding.
If you are aiming for a specific range, write it down privately first. A manager can feel when you are hiding your real number.

Mistakes to Avoid

BAD: “I’ve been doing a lot and I think I deserve more.”

GOOD: “My scope has expanded across X and Y, and I want to discuss whether my compensation still matches that level of work.”

BAD: “Can you talk to someone and get back to me whenever?”

GOOD: “Who do you need to consult, and can we set a follow-up date for next Thursday?”

BAD: “I’m loyal and I want to stay.”

GOOD: “I want to stay, and I want the package to reflect the level of responsibility I’m already carrying.”

The pattern is always the same. Weak asks sound emotional, vague, and reversible. Strong asks sound like decisions with a clock on them. Not a confession, but a calibration. Not a plea, but a proposal.

FAQ

Should I ask for a raise during performance review season?

Yes, but only if your evidence is already clean. Review season is crowded and political, so the ask needs a sharper scope story than usual. If you are still assembling your case, wait until you have a concrete milestone or launch.

Should I give a salary number in the first meeting?

Yes, if your manager asks for one. Use a range, not a single point, and tie it to scope or level correction. A hard number without a story sounds arbitrary; a number with no deadline sounds optional.

What if my manager says they need to check with HR?

That is normal, not bad. The mistake is treating it as a final answer. Ask for the next checkpoint, the decision owner, and the expected date. If those three things stay vague, the answer is probably no.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.