Most Meta engineers lose raise negotiations because they ask during the wrong 1:1 moment, not because their performance is weak. You need a specific half-cycle script that aligns with Meta's rating system and comp committee timing — not generic advice. This article gives you the exact words, the precise week to use them, and the one data point that kills your case if you get it wrong.

What Data Do I Need Before I Even Ask for a Raise at Meta?

The only data that matters is your last half's rating, your current total comp (RSUs + base + bonus target), and your manager's written PS feedback. Everything else is noise.

In a Q3 debrief I sat on, an E5 from Instagram spent twenty minutes in his 1:1 showing external offers from Uber and Stripe. The hiring manager didn't even open the documents. Why? Because Meta's comp committee only considers external offers if you have an active written offer letter with a start date, and even then, it's a counterweight, not a primary driver. The real lever is your internal rating trajectory. If you got "Meets Most" last half and "Exceeds Some" the half before, your case is stronger than someone with two "Meets Most" ratings who has three competing offers.

The counter-intuitive observation here: your manager's written PS feedback is more useful than your raw rating. A rating of "Exceeds Most" with weak written justification is less persuasive than a "Meets Most" with a narrative that shows you delivered a D2 (Design Doc 2) that unblocked two adjacent teams. The comp committee reads the narrative, not the number. Pull your PS from Workday and highlight every sentence that ties your work to business impact — revenue, shipping velocity, or org-level efficiency.

What Is the Exact Week I Should Bring Up the Raise in My 1:1?

Week 5 of the half-cycle, after your manager has submitted their draft PS but before the calibration meeting. That window is three business days.

Most engineers ask during Week 8 or Week 1, both of which are wrong. Week 1 is too early — your manager hasn't even started thinking about ratings yet, so your ask lands as an abstract request. Week 8 is too late — the PS is already locked in Workday, and your manager would need to reopen it, which triggers a flag in the system. The debrief I remember most vividly: an E4 on the Monetization team asked in Week 9, after his manager had already submitted. The manager literally said, "I can't change anything now. You should have brought this up five weeks ago." The engineer left the meeting frustrated, and his manager felt manipulated.

The reason Week 5 works is psychological. Your manager has drafted the PS but hasn't seen the calibration results yet. They still have room to add one sentence of upward adjustment, like "This engineer also led X initiative that drove Y impact." That sentence is what the comp committee uses to justify a +$15k to +$30k base increase. If you wait until after calibration, your manager's hands are tied by the forced distribution curve.

How Should I Start the Conversation — What Exact Words Do I Use?

Start with a framing statement that signals data and trajectory, not emotion or entitlement. Say: "I want to discuss my compensation trajectory relative to the impact I've delivered this half. Can we review my PS draft together and see if the narrative supports a comp adjustment?"

The problem isn't your question — it's your framing. Most engineers open with "I feel undervalued" or "I think I deserve a raise." Both collapse immediately because they're subjective. Your manager's job is to defend the team's rating distribution to their director, not to validate your feelings. The framing above works because it positions you as someone who understands the system: you're asking for a calibration review, not a favor.

One E6 I coached used this exact opener in a 1:1 with his skip-level manager. The manager paused, then said, "That's a smart way to ask. Let me pull up your PS." That manager later told me the engineer stood out because he didn't waste time on "emotional labor" — the manager's exact phrase. The engineer got a +$25k base increase and an extra 200 RSUs vesting over the next two years.

What If My Manager Says "Your Rating Is Fine, But There's No Budget"?

This is the most common deflection at Meta. The correct response is: "I understand budget constraints. Can you show me the comp band for my level and tell me where I fall within it? If I'm below the midpoint, let's discuss a path to get there."

The counter-intuitive observation: budget is rarely the real blocker. The real blocker is that your manager hasn't made your raise a priority in their own planning. Meta's comp system has a discretionary pool for off-cycle adjustments — typically 0.5% to 1.5% of total engineering budget. Your manager can access that pool if they argue your retention risk justifies it. The phrase "no budget" means "I don't want to spend political capital on you."

In a 2023 calibration meeting I observed, a director pushed back on a manager's request for an off-cycle raise. The manager said, "This engineer has a written offer from Google for $50k more." The director replied, "The budget is gone for this quarter. We'll revisit next half." The engineer quit two weeks later. The point: if your manager says "no budget," your next move is not to argue — it's to ask for a concrete timeline and a specific rating target for next half. If they can't give you either, you have your answer.

How Do I Handle the "You Just Got a Promotion Six Months Ago" Objection?

Say: "Promotion adjustments cover level change, not impact growth. My impact in the last half has exceeded the expectations for my new level. Let's review the work together."

This is the most frequent objection for E5s and E6s who were recently promoted. The assumption from many hiring managers is that a promotion resets your comp to the midpoint of the new band, so you shouldn't ask for more for at least a year. That assumption is wrong. Meta's comp system explicitly separates level-based band adjustments from performance-based comp adjustments. If you were promoted to E5 at the 25th percentile of the E5 band, and you're now delivering E6-level impact, you have a case for a comp adjustment within the same level.

The bad example: "But I've been doing great work!" That's emotional. The good example: "My promotion to E5 was based on potential. My last six months have demonstrated execution at the E5+ level. Here are three D2s I shipped, two of which are now in production." Then pull up your PS and point to the specific lines. Your manager can't argue with documented impact. They can argue with feelings.

What If My Manager Says "We Can Discuss This at Performance Review Time"?

Say: "I don't want to wait until performance review because the comp band may shift. Can we discuss a off-cycle adjustment now, or at minimum align on a specific impact target that would trigger a review in two months?"

This is a power move disguised as a request. The hiring manager's instinct is to defer until the formal review cycle because it's easier for them — they don't have to fight for budget now. But you're not asking for a favor. You're asking for clarity on the path. If your manager says "we'll discuss at review time" without giving you a specific target, they are signaling that you are not a priority. That signal is valuable information for your own career planning.

In a 2022 debrief I witnessed, an E5 on the Ads team got exactly this response. He followed up with an email that said: "Per our conversation, I understand we will revisit this at performance review time. To ensure alignment, can you confirm in writing that my PS this half will reflect the impact I've outlined, and that we will discuss comp adjustment during the review cycle?" The manager replied with a vague "yes." The engineer used that ambiguity to start interviewing externally. He left three months later for a +$60k total comp increase at a competitor.

A Practical Prep Framework

  • Pull your last two PS ratings from Workday and highlight every sentence that ties your work to measurable business impact (revenue, shipping velocity, org-level efficiency). If there are zero such sentences, you are not ready to ask.
  • Identify the exact week of your current half-cycle (Week 5, after your manager submits draft PS but before calibration). Mark it on your calendar.
  • Practice the opener aloud three times: "I want to discuss my compensation trajectory relative to the impact I've delivered this half. Can we review my PS draft together and see if the narrative supports a comp adjustment?" Your tone must be collaborative, not confrontational.
  • Research the comp band for your level using internal tools or trusted peers. Know where you fall within the band (25th, 50th, 75th percentile). If you are above the 50th percentile, your case is weaker.
  • Prepare two backup responses: one for "no budget" and one for "you just got promoted." Script them word-for-word so you don't fumble.
  • Work through a structured preparation system (the PM Interview Playbook covers comp negotiation with real debrief examples from Meta, Google, and Amazon — the framing techniques transfer directly to engineering roles).
  • Send a follow-up email within 24 hours summarizing any agreed-upon next steps. If your manager is vague, ask for a specific timeline and impact target in writing.

Patterns That Signal Weak Preparation

Mistake 1: Asking in Week 1 or Week 8 of the half-cycle.

BAD: "Hey, can we talk about my compensation?" in a Week 1 1:1. The manager hasn't even started thinking about ratings. Your request lands as abstract noise.

GOOD: "I'd like to review my PS draft together in Week 5, after you've submitted it but before calibration." This signals you understand the system's timing.

Mistake 2: Using external offers as your primary argument.

BAD: "I have an offer from Uber for $40k more." This makes you look like a retention risk, not a high performer. The manager's instinct is to let you leave.

GOOD: "My impact this half has exceeded expectations for my level. Here are three deliverables that drove measurable revenue." Lead with performance, not threats.

Mistake 3: Treating the conversation as a demand rather than a calibration review.

BAD: "I deserve a raise because I've been here two years." This is emotional and subjective. The manager can nod and do nothing.

GOOD: "Can we review my PS together and see if the narrative supports a comp adjustment?" This positions you as someone who understands the system and wants to collaborate on a solution.

FAQ

Q: What if my manager says "Your comp is already at the top of the band"?

A: Ask to see the band data. At Meta, bands are updated every half. If you are truly at the top, your only path is promotion. Focus the conversation on your promotion trajectory, not a raise.

Q: How long after asking should I expect an answer?

A: Typically two to four weeks. Your manager needs to discuss with their director and potentially the comp committee. If you hear nothing after four weeks, follow up with a written summary of your previous conversation.

Q: Can I ask for a raise if I just joined Meta six months ago?

A: No. Wait at least one full half. Your initial offer already set your comp based on market data. Asking earlier signals you don't understand how Meta's comp system works.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.