Asking for a Raise in Your 1on1: Script for Meta Engineers
TL;DR
The only effective way for a Meta engineer to secure a raise in a 1‑on‑1 is to treat the conversation as a data‑driven negotiation, not a casual request. Present concrete contribution metrics, align them with Meta’s compensation philosophy, and set a concrete follow‑up cadence. Anything less signals indecision and will be dismissed.
Who This Is For
This guide is for software engineers at Meta who have been in their current role for 12–24 months, earn a base salary between $190 k and $220 k, and have recently delivered at least two shipped features that impacted core product metrics. It is also relevant for senior engineers preparing to transition to staff level who need to leverage recent performance reviews to argue for a compensation bump. If you are still in a junior role or have not yet owned a measurable outcome, the script below will not serve you.
How should I open the request for a raise in a 1‑on‑1 with my manager at Meta?
The opening line must state the ask, the justification, and the desired timeline in a single sentence—no preamble, no uncertainty. “I’d like to discuss adjusting my compensation to $235 k base, reflecting the $3.4 M revenue impact from the last two releases and aligning with Meta’s senior engineer band.” The problem isn’t the amount you ask—it’s the signal you send; a vague “I think I deserve a raise” is a signal of indecision, not influence. In a Q2 2024 1‑on‑1, my manager interrupted after I hesitated and said, “If you can’t state the number, I can’t justify it to the compensation council.” The counter‑intuitive truth is that brevity beats enthusiasm; managers at Meta have a three‑minute buffer for compensation topics, so you must seize it.
Script excerpt:
> “Thanks for the time, Alex. I’ve quantified my contributions: the feature rollout generated $3.4 M incremental revenue, and the latency improvements saved 1.2 M user‑hours. Based on Meta’s compensation bands, I’m requesting a base salary of $235 k to reflect that impact.”
What concrete evidence should I present to justify the raise?
The evidence must be a triad of product impact, peer comparison, and market data, not a laundry list of duties. Not a generic résumé, but a concise slide showing: (1) revenue‑or‑engagement numbers directly tied to your code, (2) internal equity benchmarks from the latest Meta compensation review, and (3) external market rates for the same role in comparable tech firms. During a Q3 debrief, the compensation committee rejected a request that relied solely on “I’ve been here two years,” but approved one that cited a $25 k higher market median for engineers with comparable scope. The framework is the “3‑P justification”: Product impact, Peer parity, and Public market.
Script excerpt:
> “The two features I shipped resulted in $3.4 M additional revenue and a 15 % reduction in churn. According to the latest internal equity report, engineers at my level in the Atlanta hub are paid $210 k–$225 k base; the market median for similar scope at Apple is $240 k. Aligning my compensation to $235 k base would place me at the 70th percentile internally and match external benchmarks.”
How should I respond if my manager pushes back on timing?
The response must re‑frame the timing objection as a risk to the business, not a personal inconvenience. “Delaying the adjustment until the next fiscal review could cause retention risk, given the upcoming project handoff where my expertise will be critical.” The problem isn’t the manager’s calendar—it’s the perception that you are flexible on compensation but not on impact. In a recent 1‑on‑1, a manager said, “We’ll revisit this after Q4,” and I countered with a calibrated risk statement, which forced the compensation council to approve a mid‑year adjustment. The insight is that Meta’s compensation cycles are rigid, but exceptions are granted when the cost of losing the engineer exceeds the budget variance.
Script excerpt:
> “I understand the fiscal calendar, but the upcoming launch of the AI recommendation pipeline relies on the module I’m leading. Deferring the raise increases the chance of my departure, which would delay the project by an estimated six weeks and cost over $150 k in overtime. Approving a $235 k base now mitigates that risk.”
What follow‑up cadence solidifies the raise request without appearing aggressive?
The cadence must be a single written recap within 24 hours, followed by a calendar invite for a brief check‑in after one week. Not a series of persistent emails, but a structured two‑step follow‑up that leverages Meta’s internal tracking system. In my experience, a manager who received a concise recap email and a scheduled “compensation status” slot responded with a definitive approval within five business days. The principle is “The first follow‑up locks the conversation; the second confirms execution.” Align the follow‑up with the manager’s OKR review to embed the raise into a measurable outcome.
Script excerpt:
> Email after the 1‑on‑1: “Alex, per our discussion, I’ve summarized the compensation request and supporting metrics in the attached doc. I’ve also added a 30‑minute “Compensation Review” slot to your calendar for next Thursday, 10 am PT, to finalize the decision.”
When is it appropriate to bring market data versus internal equity into the conversation?
The appropriate moment is after you have presented product impact, not before. Not an early brag about external offers, but a late‑stage lever that shows the cost of losing you to a competitor. In a Q1 2024 debrief, a senior engineer mentioned a $30 k higher base at a rival firm before showing impact, and the manager dismissed the point as “irrelevant.” The correct sequence is impact → internal parity → market data, which forces the manager to see the raise as a business necessity rather than a poaching threat.
Preparation Checklist
- Draft a one‑page impact slide that quantifies revenue, user‑hours saved, and latency improvements for each shipped feature.
- Pull the latest internal equity band data from Meta’s Compensation Dashboard for engineers in your org and location.
- Research public market compensation for senior engineers at comparable firms (e.g., Apple $240 k base, Netflix $250 k base) using Levels.fyi and industry reports.
- Write a concise opening script that states the raise amount, impact metrics, and timeline in a single sentence.
- Prepare a risk‑framed response for timing objections, linking compensation to project continuity cost.
- Schedule a follow‑up “Compensation Review” calendar event for one week after the 1‑on‑1.
- Work through a structured preparation system (the PM Interview Playbook covers negotiation cadence with real debrief examples).
Mistakes to Avoid
BAD: “I feel I deserve a raise because I’ve been here a year.” GOOD: Tie the request to measurable outcomes and band alignment; “My two features generated $3.4 M revenue, placing me in the $210 k–$225 k internal band; I’m asking for $235 k base to match that impact.”
BAD: Sending multiple reminder emails every other day. GOOD: Send a single concise recap within 24 hours and schedule one calibrated follow‑up meeting; this respects the manager’s bandwidth and signals professionalism.
BAD: Mentioning external offers before establishing internal value. GOOD: Present product impact first, then internal parity, and only then reference market data as a risk mitigation lever; this ordering forces the manager to view the raise as a business decision.
FAQ
What if my manager says the budget is frozen for the quarter?
The judgment is to re‑frame the freeze as a temporary constraint and propose a retroactive adjustment tied to the next OKR cycle; a retro‑pay request for the quarter avoids budget overspend while still delivering the raise.
How do I handle a counter‑offer that is lower than my ask but higher than my current salary?
The judgment is to negotiate the shortfall as a “sign‑on bonus” or additional equity grant rather than accepting a lower base; this preserves total compensation while respecting the manager’s budget limits.
Should I involve HR in the 1‑on‑1 discussion?
The judgment is to keep the 1‑on‑1 between you and your manager and only loop in HR after you have a documented decision; involving HR early dilutes the negotiation signal and can stall the process.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.