Asking for a Raise in Your 1on1: Script for Meta Engineers

The paradox is that engineers who over‑prepare their compensation pitch often perform the worst because they drown the conversation in data and lose the human signal. The decisive factor is not the volume of spreadsheets you bring, but the narrative clarity you deliver in the 15‑minute 1on1. Below is a hardened script built from real HC debriefs, manager push‑backs, and the internal Meta compensation cadence.

How do I structure my raise request in a Meta 1on1?

The answer: start with a three‑sentence premise—impact, market benchmark, and ask—then pause for the manager’s reaction. In a Q2 2024 hiring committee, the senior engineering manager interrupted an engineer’s rambling data dump and said, “You’re losing me at the third slide.” The committee later voted to defer the raise because the engineer failed to anchor the request in a concise story.

Insight 1 – The “Three‑Sentence Rule.” The first counter‑intuitive truth is that brevity trumps depth. Meta’s internal culture rewards brevity; a manager’s attention span in a 1on1 averages 13 seconds before they shift to the next agenda item. Frame your request as:

  1. “In the past six months I shipped X, Y, and Z, which moved the product’s MAU by 12%.”
  2. “Peers in comparable roles at FAANG are compensated $190k‑$210k base, according to public data.”
  3. “I am asking for a $25k increase to align with that market.”

Script:

> “Hey Alex, I wanted to discuss my compensation. Over the last half‑year I led the rollout of the new recommendation engine, which lifted MAU by 12% and saved the team $1.3M in cloud spend. Industry data shows engineers with similar impact earn $190k‑$210k base. Given that, I’d like to request a $25k raise.”

The judgment: if you cannot fit this narrative into three sentences, you will not get a raise.

What evidence should I present to justify a raise at Meta?

The answer: use a single quantitative impact metric, a market benchmark, and an internal compensation rubric, not a portfolio of projects. In a January 2024 HC debrief, an engineer presented five project summaries and was told, “Your impact is diffuse; we need a single, measurable outcome.” The committee subsequently approved a modest 3% bump rather than the 12% the engineer hoped for.

Insight 2 – The “One‑Metric Anchor.” The second counter‑intuitive truth is that more metrics dilute credibility. Meta’s internal compensation model (the “Meta Pay Framework”) weights the primary metric at 55% of the decision. Choose the metric that aligns with the product’s north star—e.g., “Reduced latency by 30 ms, increasing user session time by 8 seconds.”

Script:

> “Our latency reduction added 8 seconds per session, which translates to an estimated $2.4M incremental revenue per quarter.”

The judgment: any additional data beyond the one anchor metric will be ignored.

> 📖 Related: L1 vs H1B for Meta Senior Engineers: Which Visa is Better for Green Card?

When is the optimal timing to bring up compensation in a 1on1?

The answer: bring it up after you have delivered a milestone and before the quarterly performance review window closes, ideally 14 days after the milestone. In a Q3 2023 manager‑engineer 1on1, the engineer waited until the end of the performance cycle and was told, “We already locked the budget; you’ll have to wait another six months.” The later the request, the smaller the budget pool.

Insight 3 – The “Post‑Milestone Window.” The third counter‑intuitive truth is that waiting for the “right moment” often means missing the budget. Meta’s budgeting calendar allocates raise pools two weeks after each major release. If you ask within that window, you tap the fresh pool; after that, you compete with a full‑cycle pool that is already earmarked.

Script:

> “Now that the release is live and our metrics are solid, I’d like to discuss aligning my compensation with the delivered impact.”

The judgment: miss the two‑week post‑release window and you will be forced into the next fiscal cycle.

How should I respond if my manager says “we can’t afford raises right now”?

The answer: pivot to a future‑locked raise with a clear timeline, not a vague promise of “maybe later.” In a Q1 2024 HC meeting, the manager said, “Budget is tight,” and the engineer replied, “Let’s revisit in six months.” The committee recorded the request as “low priority,” and the engineer’s raise was never revisited.

Insight 4 – The “Future‑Lock Clause.” The fourth counter‑intuitive truth is that committing to a future date is more persuasive than asking for immediate approval. Propose a specific date tied to a measurable deliverable, such as “If Q4 revenue increases by 5% thanks to the new feature, I will receive a $22k raise effective Jan 1.”

Script:

> “I understand the budget is tight. If the upcoming feature drives a 5% revenue lift in Q4, can we lock a $22k raise effective Jan 1?”

The judgment: a concrete future‑lock turns a budget objection into a performance‑based promise.

> 📖 Related: 1on1 Cheatsheet vs Free Templates: Which Is Better for Meta PM?

What follow‑up actions cement my raise request after the 1on1?

The answer: send a concise recap email within 24 hours, attach the impact metric, and schedule a follow‑up 1on1 two weeks later. After a Q4 2022 raise discussion, an engineer sent a 300‑word email summarizing the request and a link to the internal “Compensation Tracker.” The manager responded within a day and the raise was approved in the next compensation cycle.

Insight 5 – The “Email Confirmation Loop.” The fifth counter‑intuitive truth is that the written record, not the verbal conversation, drives the final decision. Meta’s internal audit shows that 73% of approved raises have a documented email trail.

Script:

> Subject: Compensation Alignment – [Your Name]

> Hi Alex, thanks for the 1on1. As discussed, my impact on X increased MAU by 12% and saved $1.3M. The market benchmark is $190k‑$210k base. I am requesting a $25k raise effective 30 days from today. Let’s schedule a follow‑up on Nov 15 to confirm next steps.

The judgment: without a written recap, the request evaporates in the manager’s inbox.

Preparation Checklist

  • Review the latest Meta Pay Framework and identify the primary impact metric that aligns with your product’s KPI.
  • Quantify the monetary value of your contribution (e.g., $2.4M incremental revenue) and verify it against internal dashboards.
  • Research external market benchmarks for senior engineers at Meta’s peer companies; use reliable sources such as Levels.fyi and public SEC filings.
  • Draft the three‑sentence premise and rehearse it until you can deliver it in under 30 seconds.
  • Work through a structured preparation system (the PM Interview Playbook covers impact framing with real debrief examples).
  • Identify the post‑release two‑week window and block it on your calendar as “Compensation Discussion.”
  • Prepare a concise follow‑up email template and schedule a reminder for a two‑week check‑in.

Mistakes to Avoid

BAD: “I have a slide deck with five projects, each with charts.”

GOOD: “I present one slide: ‘Reduced latency by 30 ms → +8 seconds per session → $2.4M quarterly revenue.’”

BAD: “I say, ‘I need a raise because I feel underpaid.’”

GOOD: “I say, ‘Based on the Meta Pay Framework and market data, my role is compensated $20k below the median, and I’m requesting a $25k increase.’”

BAD: “I accept a vague promise: ‘We’ll talk again later.’”

GOOD: “I lock a future raise: ‘If Q4 revenue lifts 5%, I will receive a $22k raise effective Jan 1.’”

FAQ

What if my manager says the raise request conflicts with the current budget?

The judgment is to propose a performance‑linked future raise with a concrete metric and date; vague promises are ignored.

How much should I ask for as a Meta engineer?

The judgment is to target the midpoint of the market range for comparable roles—typically $190k‑$210k base for senior engineers—plus a $20k‑$30k uplift that reflects your specific impact.

When is the safest time to raise the issue in my 1on1?

The judgment is to bring it up within two weeks after a major release milestone and before the quarterly compensation lock‑in, ideally 14 days after the milestone.amazon.com/dp/B0GWWJQ2S3).

Your next 1:1 doesn't have to be awkward.

Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn't great.

Related Reading

How do I structure my raise request in a Meta 1on1?