# SalaryScript (full content for LLMs) > SalaryScript helps software engineers negotiate higher tech job offers. It publishes free, in-depth salary negotiation guides, word-for-word scripts, and company-specific playbooks, alongside a paid 125-page negotiation book for the recruiter back-and-forth that follows the first counter. Site: https://salaryscript.com Index: https://salaryscript.com/llms.txt ## Company-specific playbooks (summaries) - Google (https://salaryscript.com/google-salary-negotiation/): Base is capped per level; RSUs (33/33/22/12 front-loaded monthly vest) and sign-on are the levers. Push level before the offer is generated. - Meta (https://salaryscript.com/meta-salary-negotiation/): 25/25/25/25 RSU vest. The E5 to E6 leveling appeal can be worth $150K+ per year. Recruiters have more discretion and move fast. - Amazon (https://salaryscript.com/amazon-salary-negotiation/): Base hard-capped (~$175K for most roles); 5/15/40/40 back-loaded vest; Year 1 and Year 2 sign-on bonuses are the primary lever. - Apple (https://salaryscript.com/apple-salary-negotiation/): 25/25/25/25 vest with conservative initial grants; base has more flexibility than at Google or Amazon; refreshers reward strong performers. - Netflix (https://salaryscript.com/netflix-salary-negotiation/): All-cash comp, no RSUs, no bonus. The negotiation is entirely about base; competing offers move it $30K to $50K+. - Microsoft (https://salaryscript.com/microsoft-salary-negotiation/): On-hire stock vests 25% per year over 4 years; refreshers vest over 5 years quarterly, so total comp dips in Years 2 to 4 unless the on-hire grant is negotiated up. - Nvidia (https://salaryscript.com/nvidia-salary-negotiation/): NSUs vest quarterly at 6.25% with no cliff; no recurring annual cash bonus; the ESPP is a meaningful part of comp. - Stripe (https://salaryscript.com/stripe-salary-negotiation/): Double-trigger RSUs at a private company; liquidity comes through periodic tender offers; negotiate the dollar value of the grant. - Uber (https://salaryscript.com/uber-salary-negotiation/): Monthly vest with no one-year cliff; front-loading sometimes available; win the L4 to L5 leveling first. - OpenAI (https://salaryscript.com/openai-salary-negotiation/): Moved from Profit Participation Units to conventional RSUs after the October 2025 PBC conversion; top-of-market comp; confirm current grant terms. - Anthropic (https://salaryscript.com/anthropic-salary-negotiation/): Systematic no-negotiation offers (same level, same offer); RSUs vest 4 years with a 1-year cliff; tender offers provide liquidity; level placement and sign-on bridges are the real levers. - Databricks (https://salaryscript.com/databricks-salary-negotiation/): Private, L3-L8 ladder; equity is the dominant and most negotiable component; recurring tender offers; get the exact vesting schedule in writing. - TikTok (https://salaryscript.com/tiktok-salary-negotiation/): Base-heavy vs FAANG; ~25% bonus target; back-weighted ByteDance RSU vest with buyback liquidity; no refreshers, so the initial grant is the negotiation. - Salesforce (https://salaryscript.com/salesforce-salary-negotiation/): AMTS-PMTS ladder; RSUs vest 4 years with a 1-year cliff; sign-on is often omitted from first offers and must be asked for; equity moves most. - LinkedIn (https://salaryscript.com/linkedin-salary-negotiation/): Pays in Microsoft stock on LinkedIn's own named ladder; 25% cliff then quarterly vest; small refreshers make the on-hire grant the negotiation. - Coinbase (https://salaryscript.com/coinbase-salary-negotiation/): No-negotiation policy since 2021 (standardized pay per level); annual equity grants vesting quarterly with no cliff; level placement and documented sign-on asks still move. - Airbnb (https://salaryscript.com/airbnb-salary-negotiation/): G-level ladder; single US pay tier regardless of location; RSUs vest 4 years with a 1-year cliff then quarterly; equity is the lever. - Snowflake (https://salaryscript.com/snowflake-salary-negotiation/): IC ladder; quarterly vesting with no 1-year cliff for recent grants; no sign-on bonuses at all, so push value into the RSU grant. - Palantir (https://salaryscript.com/palantir-salary-negotiation/): Base often below FAANG for the level; equity has historically leaned on stock options rather than plain RSUs; firm take-it-or-mostly-leave-it offers, so level and equity mix are the real negotiation. Comp structure has shifted over time; verify the instrument in the written offer. - Datadog (https://salaryscript.com/datadog-salary-negotiation/): Public (NASDAQ: DDOG); conventional offers with liquid RSUs on a standard 4-year vest, a bonus for many roles, and an easy-to-overlook ESPP; leverage is level, RSU grant size, and a sign-on bridge. - Reddit (https://salaryscript.com/reddit-salary-negotiation/): Public since March 2024 (NYSE: RDDT); pays at or near top of market with a heavy RSU component; leverage is level, RSU grant, and sign-on, priced against a volatile post-IPO share price. - Robinhood (https://salaryscript.com/robinhood-salary-negotiation/): Public (NASDAQ: HOOD); RSU-heavy on a standard 4-year schedule with competitive base; known for large refresher and retention grants when the stock moves; price the grant against a volatile share price. ## Free tool - Counter-Offer Email Generator (https://salaryscript.com/salary-negotiation-email-generator/): enter your offer numbers and get a ready-to-send counter-offer email draft, free, in the browser, with no signup. ## Product - SalaryScript Bundle ($129): the 125-page Pro playbook plus the Pocket quick-reference guide. Instant download, 14-day results-based guarantee. https://salaryscript.com/#pricing - SalaryScript Pro ($109): the full 125-page negotiation playbook. - SalaryScript Pocket ($39): the 15-page quick reference for live calls. --- # Blog posts (full text) ## Big Tech RSU Vesting Schedules Compared (2026) URL: https://salaryscript.com/blog/rsu-vesting-schedules-big-tech/ Published: 2026-07-01 (updated 2026-07-02) Description: Google's 33/33/22/12, Amazon's 5/15/40/40, Meta's 25/25/25/25: every big tech RSU vesting schedule side by side, and how each one changes your negotiation. Two offers, both "$400K in RSUs over 4 years." One pays you $132K of equity in Year 1. The other pays $20K. That is not an edge case. It is literally Google versus Amazon, and it is why comparing 4-year equity totals without the vesting schedule is the single most common mistake engineers make when weighing big tech offers. Here is every major schedule side by side, based on what we have seen across 1,200+ negotiations, followed by what each one means for how you negotiate. ## The comparison table | Company | Schedule (Y1/Y2/Y3/Y4) | Cadence | Cliff | The catch | |---|---|---|---|---| | [Google](/google-salary-negotiation/) | 33% / 33% / 22% / 12% | Monthly | None | Front-loaded: income drops in Y3 and Y4 without refreshers | | [Meta](/meta-salary-negotiation/) | 25% / 25% / 25% / 25% | Quarterly | None | Cleanest vest in FAANG; grant size is the whole conversation | | [Amazon](/amazon-salary-negotiation/) | 5% / 15% / 40% / 40% | Annual then semi-annual | Effectively Y1 | Only 20% vests in the first 2 years; Y1/Y2 sign-ons paper over the gap | | [Apple](/apple-salary-negotiation/) | 25% / 25% / 25% / 25% | Semi-annual | None | Conservative initial grants; refreshers do the heavy lifting | | [Microsoft](/microsoft-salary-negotiation/) | 25% / 25% / 25% / 25% (on-hire) | Annual | None | Refreshers vest over 5 years quarterly, so TC dips in Y2 to Y4 | | [Netflix](/netflix-salary-negotiation/) | No RSUs | n/a | n/a | All-cash comp; stock options are an opt-in choice | | [Nvidia](/nvidia-salary-negotiation/) | 25% / 25% / 25% / 25% | Quarterly (6.25%) | None | No annual cash bonus; equity and ESPP carry the upside | | [Uber](/uber-salary-negotiation/) | 25% / 25% / 25% / 25% | Monthly | None | Front-loading is sometimes available, and itself negotiable | | [Stripe](/stripe-salary-negotiation/) | Time-based, double-trigger | Varies | Varies | Illiquid until a tender offer; value depends on the private valuation | | [OpenAI](/openai-salary-negotiation/) | ~4-year vest, terms in flux | Varies | Varies | Moved from PPUs to conventional RSUs after the Oct 2025 restructuring; confirm current terms | | [Anthropic](/anthropic-salary-negotiation/) | 25% / 25% / 25% / 25% | Monthly after a 1-year cliff | Year 1 | Private: liquidity via tender offers; some grants reported double-trigger, confirm yours | | [Databricks](/databricks-salary-negotiation/) | Reports conflict (front-loaded vs even) | Varies | Varies | Private with recurring tenders; get your exact schedule and any cliff in writing | | [TikTok](/tiktok-salary-negotiation/) | 20% / 25% / 25% / 30% (newer grants) | Quarterly after 1-year cliff | Year 1 | ByteDance buybacks are the liquidity; no refreshers, so the initial grant is everything | | [Salesforce](/salesforce-salary-negotiation/) | 25% / 25% / 25% / 25% | 1-year cliff, then quarterly | Year 1 | Refreshers not guaranteed below senior grades | | [LinkedIn](/linkedin-salary-negotiation/) | 25% / 25% / 25% / 25% (MSFT stock) | 25% cliff, then 6.25% quarterly | Year 1 | Vests quarterly, unlike Microsoft corp's annual cadence | | [Coinbase](/coinbase-salary-negotiation/) | Annual re-grants, not 4-year | Quarterly | None | Grant re-sized yearly at current price: steadier dollars, less stock upside | | [Airbnb](/airbnb-salary-negotiation/) | 25% / 25% / 25% / 25% | 25% cliff, then quarterly | Year 1 | Single US pay tier for salary and equity | | [Snowflake](/snowflake-salary-negotiation/) | 25% / 25% / 25% / 25% | Quarterly, no cliff (post-2023 grants) | None | Older guides still describe a 1-year cliff; check your grant agreement | | [Palantir](/palantir-salary-negotiation/) | Options and/or RSUs, 4-year | Varies by instrument | Varies | Historically options-heavy; confirm the instrument and strike before valuing | | [Datadog](/datadog-salary-negotiation/) | 25% / 25% / 25% / 25% | 1-year cliff, then quarterly | Year 1 | Liquid public stock; don't forget the ESPP discount on top | | [Reddit](/reddit-salary-negotiation/) | 25% / 25% / 25% / 25% | 1-year cliff, then quarterly | Year 1 | Post-IPO (RDDT) and volatile; weight refreshers, think in ranges | | [Robinhood](/robinhood-salary-negotiation/) | 25% / 25% / 25% / 25% | 1-year cliff, then quarterly | Year 1 | HOOD is highly volatile; large retention/refresher grants are part of the story | Schedules apply to standard engineering offers and can vary by level, org, and offer cycle. Always confirm the exact schedule in your written offer. ## Why the schedule changes your negotiation ### Google (33/33/22/12): negotiate the grant, plan for the Year 3 dip Google's front-loaded schedule is genuinely candidate-friendly early on: two-thirds of your grant lands in the first two years, vesting monthly. The trap is the back half. Years 3 and 4 deliver only 34% combined, so your total comp falls off a cliff unless refresher grants fill the hole. What to do with this: anchor your counter on the initial grant size (it can vary by $100K+ within a level) and ask directly about the refresh policy. The full [Google salary negotiation playbook](/google-salary-negotiation/) covers the equity conversation word for word. ### Amazon (5/15/40/40): the sign-on IS the negotiation Amazon's schedule is the inverse of Google's. You collect 5% of your equity in Year 1. That is why Amazon offers large sign-on bonuses split across Years 1 and 2: they exist specifically to make early total comp look competitive despite the back-loaded vest. What to do with this: model Y1 and Y2 income separately from the 4-year total, and push on the sign-on and the total RSU grant rather than base (which is hard-capped for most roles). Our [Amazon salary negotiation guide](/amazon-salary-negotiation/) walks through the math. ### Meta, Apple, Microsoft (25/25/25/25): grant size is everything An even vest means no schedule games, so the negotiation collapses to one number: the size of the grant. Meta moves fastest on equity increases. Apple starts conservative and pays for performance through refreshers. Microsoft's wrinkle is that refreshers vest over five years, which quietly dips Years 2 through 4 unless the on-hire grant is big enough. ### Netflix: there is no schedule Netflix pays all cash, full stop. No vest, no cliff, no golden handcuffs. That makes a Netflix offer easy to value and impossible to inflate with equity storytelling, and it means the entire negotiation is a [base salary conversation](/netflix-salary-negotiation/). ### Private companies (Stripe, OpenAI): value the liquidity, not the headline At Stripe, RSUs are double-trigger: they vest on a time schedule but only turn into money at a liquidity event, in practice a periodic employee tender offer. At OpenAI, the instrument itself changed in late 2025 (PPUs converting to conventional equity). In both cases the headline dollar figure assumes a valuation you cannot sell at today, so negotiate the grant while discounting for liquidity. ## How to use this when you counter 1. **Convert every offer to Year 1 and Year 2 income** (base + bonus + actually-vesting equity + sign-on). This is the honest comparison, and it is where Amazon's 5/15/40/40 or a Microsoft refresher dip shows up. 2. **Use the schedule gap as your justification.** "Your vest delivers $20K in Year 1; the competing offer delivers $130K. Can we bridge that with sign-on?" is a counter a recruiter can take to the comp committee. A proven [salary negotiation email template](/blog/salary-negotiation-email-templates/) gets the wording right. 3. **Ask about refreshers before you sign**, especially at Google, Apple, and Microsoft, where the initial schedule understates or overstates long-term comp. The schedule tells you where the money is. Signing without moving it locks the gap in for four years of vesting. Getting it moved is the back-and-forth that follows your counter, and that is what the SalaryScript playbook covers: a counter-move for every recruiter pushback, calibrated by company. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) (instant download, 14-day results-based guarantee) or [compare all plans from $39](/#pricing). Related reading: [The Complete FAANG Salary Negotiation Guide](/blog/faang-salary-negotiation-guide/), [How Much Should You Counter a Software Engineer Offer?](/blog/how-much-to-counter-software-engineer-offer/), and [How to Negotiate Salary After a Job Offer](/blog/how-to-negotiate-salary-after-job-offer/). ## Tech Sign-On Bonuses 2026: Typical Amounts by Company URL: https://salaryscript.com/blog/sign-on-bonus-negotiation/ Published: 2026-07-01 (updated 2026-07-02) Description: How much sign-on bonus to expect at Google, Meta, Amazon, Nvidia and the rest of big tech, why sign-ons move easier than base or equity, and how to ask. When a recruiter tells you "base is at the top of the band and the equity grant is standardized," most candidates give up. The candidates who don't ask one more question: "Is there flexibility on the sign-on?" There usually is. The sign-on bonus is the most underused lever in tech offer negotiation because it is the one component that sits outside the compensation band for your level. It is one-time cash, it sets no precedent, and at most companies it clears approval faster than any base or equity change. Here is what sign-ons look like across big tech, and exactly how to ask for one. ## Sign-on bonuses by company | Company | Typical sign-on | What it's for | Negotiability | |---|---|---|---| | [Google](/google-salary-negotiation/) | $30K to $80K, $100K+ senior | Bridging unvested RSUs you forfeit | High: separate budget from base/equity | | [Meta](/meta-salary-negotiation/) | $50K to $200K at senior levels | Closing competing offers, fast | High: Meta uses sign-ons aggressively | | [Amazon](/amazon-salary-negotiation/) | $80K to $150K+ split over Y1 and Y2 | Masking the 5/15/40/40 back-loaded vest | Highest: where 80% of Amazon negotiations move | | [Apple](/apple-salary-negotiation/) | Smaller than Amazon's | Closing a Year-1 gap without touching equity | Moderate | | [Netflix](/netflix-salary-negotiation/) | None | All comp is in base salary | n/a: negotiate base instead | | [Microsoft](/microsoft-salary-negotiation/) | Moderate; Year-2 sign-ons happen | Fixing the Year 2 to 4 refresher dip | Moderate | | [Nvidia](/nvidia-salary-negotiation/) | Case by case | Bridging Year 1 once the RSU grant is maxed | Good: sits outside the base band | | [Uber](/uber-salary-negotiation/) | Case by case | Year-1 cash or unvested equity bridge | Good: cleanest post-band lever | | [Stripe](/stripe-salary-negotiation/) | Case by case | Cash certainty against illiquid equity | Good: the most movable component | | [OpenAI](/openai-salary-negotiation/) | Case by case | Closing against big-tech cash | Varies: equity dominates the offer | | [Anthropic](/anthropic-salary-negotiation/) | Case by case | Bridging forfeited equity despite standardized comp | The flexible exception to a no-negotiation policy | | [Databricks](/databricks-salary-negotiation/) | Tens of thousands, scales with level | Competing FAANG offers, forfeited equity | Good | | [TikTok](/tiktok-salary-negotiation/) | $30K to $100K+ by level | First-year lump sum, 12-month clawback | Negotiable | | [Salesforce](/salesforce-salary-negotiation/) | Often omitted from first offers | You have to ask; 1-year prorated clawback | Good, once you ask | | [LinkedIn](/linkedin-salary-negotiation/) | Reported up to ~$75K around Staff | Often omitted as a negotiation filter | Moderate: needs concrete leverage | | [Coinbase](/coinbase-salary-negotiation/) | Only with written proof | Offsetting documented losses under the no-negotiation policy | Narrow but real | | [Airbnb](/airbnb-salary-negotiation/) | Case by case, reluctant vs peers | Year-1 cash | Moderate | | [Snowflake](/snowflake-salary-negotiation/) | None | Snowflake does not pay sign-ons; push equity instead | n/a | | [Palantir](/palantir-salary-negotiation/) | Case by case | Bridging forfeited equity against a firm offer | Good: the most movable cash lever | | [Datadog](/datadog-salary-negotiation/) | Case by case | Closing a gap or bridging unvested equity | Good: more room than the base | | [Reddit](/reddit-salary-negotiation/) | Case by case | Bridging forfeited equity, closing a competing offer | Good: pays up for engineers | | [Robinhood](/robinhood-salary-negotiation/) | Case by case | Bridging forfeited equity, closing the last gap | Good: aggressive for talent it wants | Ranges reflect what we have seen across 1,200+ negotiations and shift with level and market. Verify current data on Levels.fyi before you anchor. ## Why sign-ons move when nothing else does Compensation bands are rigid on purpose. If a recruiter raises one engineer's base above the L5 band, every future L5 negotiation gets harder, so the system pushes back hard on base increases. Equity grants face similar band pressure plus committee review. A sign-on bonus dodges all of that: 1. **It's one-time.** It does not compound into raises, refreshers, or bonus targets, so it costs the company far less than the same amount in base. 2. **It's outside the band.** Approving it does not distort the level's comp data. 3. **It solves a story the recruiter can sell.** "Candidate is walking away from $60K of unvested RSUs" is a one-line justification a comp team approves quickly. That third point is the key to asking well. Vague asks ("can you add a sign-on?") get vague answers. Specific, evidence-backed asks get approved. ## The three justifications that work **1. Unvested equity you're leaving behind.** The strongest and most common. Count the RSUs that would have vested at your current company over the next 12 to 18 months and ask for a bridge: "I'm forfeiting $[X] in unvested equity by leaving. Could a sign-on bridge part of that?" **2. A vesting-schedule gap at the new company.** If the offer's equity barely vests in Year 1 (Amazon's 5/15/40/40 is the extreme case; see our [RSU vesting schedule comparison](/blog/rsu-vesting-schedules-big-tech/)), frame Year-1 total comp against your competing offer or current pay and ask for the sign-on to close the difference. **3. A competing offer's Year-1 cash.** Sign-ons are how companies win head-to-head recruiting battles without moving bands. If another offer pays more in Year 1, say so with the number. ## The word-for-word ask > "Thanks again for walking me through the package. Base and equity both make sense to me at this level. The one gap is Year 1: I'm walking away from $[X] in unvested RSUs at [current company], and as structured I'd take a meaningful step back in the first year. Would a sign-on of $[Y] be possible to bridge that? If we can get there, I'm ready to sign by [date]." This works because it accepts the band constraints (so the recruiter doesn't have to defend them), names a specific number with a specific reason, and attaches a close. For the full email version, use our [salary negotiation email templates](/blog/salary-negotiation-email-templates/); template 4 covers the sign-on ask directly. > **The ask is one line. The response you get back is where it's won or lost.** "That's not something we normally do," a partial counter, or a week of silence, each needs a different reply, and the wrong one leaves the sign-on on the table for good. SalaryScript is the by-company, by-level playbook for the full back-and-forth. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) (instant download, 14-day results-based guarantee). ## Read the clawback terms before you celebrate Most sign-ons come with repayment terms: leave within 12 months and you owe some or all of it back. Amazon structures its sign-ons as monthly payments through Years 1 and 2 instead, which prorates automatically but also means the "bonus" disappears from your comp after Year 2 (plan for that cliff when you evaluate the offer). Check the exact terms in the written offer, not the recruiter's summary. ## Where the sign-on fits in the full negotiation The sign-on is usually your second or third move, not your first. Size your overall counter first (our guide on [how much to counter a software engineer offer](/blog/how-much-to-counter-software-engineer-offer/) covers the math), push the lever that compounds (equity or level) while you have maximum leverage, and then use the sign-on to close whatever Year-1 gap remains. The back-and-forth that follows the ask (the "that's not something we normally do," the partial counter, the silence) is where most of the money is won or lost. That is what SalaryScript covers: a counter-move for every recruiter tactic, calibrated by company. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) (instant download, 14-day results-based guarantee) or [compare all plans from $39](/#pricing). Related reading: [Big Tech RSU Vesting Schedules Compared](/blog/rsu-vesting-schedules-big-tech/), [How to Negotiate Salary After a Job Offer](/blog/how-to-negotiate-salary-after-job-offer/), and [The Complete FAANG Salary Negotiation Guide](/blog/faang-salary-negotiation-guide/). ## How Much to Counter a Software Engineer Job Offer URL: https://salaryscript.com/blog/how-much-to-counter-software-engineer-offer/ Published: 2026-04-19 Description: How much to counter a software engineer offer, by level (L3–L7), company tier, and leverage, with real examples, scripts, and the math behind each number. You have the offer in writing. The recruiter wants a response by Friday. And you are sitting there Googling the only question that actually matters right now: how much should you counter? Here is the short answer, and then we will get into the details. **For a typical software engineer offer, counter between 10% and 20% above the base salary, and push total compensation (TC) up by 15% to 30% when you include sign-on bonus and equity adjustments. Your exact number depends on three things: your level, the company tier, and how much competing leverage you have.** That is the headline. The rest of this guide is the math, the tables, the scripts, and the honest trade-offs behind it. We have helped over 1,200 tech professionals run this exact calculation, and the patterns are consistent enough that you can price your counter in about fifteen minutes once you know what to look at. ## The Short Answer, Visualized If you just want a number and a reason, use this table as a starting point. Adjust up or down based on your leverage (more on leverage below). | Level | Title examples | Typical counter on base | Typical counter on TC | Realistic TC gain | |---|---|---|---|---| | L3 / New Grad | SDE I, Associate SWE | 8% to 12% | 10% to 15% | $8K to $25K | | L4 / Mid | SDE II, Software Engineer | 10% to 15% | 15% to 22% | $20K to $55K | | L5 / Senior | Senior SWE, SDE III | 12% to 18% | 18% to 28% | $40K to $95K | | L6 / Staff | Staff Engineer, Principal SDE | 15% to 22% | 20% to 35% | $75K to $180K | | L7 / Principal | Principal, Distinguished | 18% to 25% | 25% to 45% | $150K to $400K+ | A few notes before anyone emails us. These are base-case ranges. They assume you have at least one competing data point (a second offer, a recent interview loop that went deep, a current comp stub showing a recent raise cycle, or clear Levels.fyi medians above the initial number). Without any leverage at all, you should shade toward the lower end. With two competing offers from peer-tier companies, you can often beat the upper end. Jonathan, a Staff Software Engineer who used our playbook at Reddit, negotiated $102K above his initial offer. Andrew, another Staff Engineer at ParTech, added $100K to what the company already called a "good offer." Tony, a Senior Data Scientist at Amazon, closed $75K above the initial number using our exact scripts. Those are not outliers for L5 and L6 roles. They are what happens when the counter is priced correctly. ## Why "How Much" Is the Wrong First Question Most candidates start by asking how much to counter. That is backwards. The counter number is an output, not an input. The real inputs are: 1. The market price for your exact level and location (what Levels.fyi and H1B Salary Data say the median and 75th percentile look like). 2. Your BATNA, which is negotiation jargon for the best alternative you have if this deal falls apart. Another offer is the strongest BATNA. An active final-round loop is the second strongest. A current job you would happily stay at is the third. 3. The flex this specific company has at this specific level. Some levels at some companies have bands twice as wide as others. Meta E5 has more room than Google L5 at most locations. Stripe has more room than Shopify. A Series B startup has less cash flex than a late-stage unicorn but more equity flex. Once you have those three inputs, the counter number writes itself. You pick the number that is slightly above the 75th percentile of market, inside the likely band, and close to or above what your BATNA would pay. If that number also lands 10% to 20% above the initial offer, you are in the standard zone. If it lands higher, you need strong BATNA to justify it. If it lands lower, you probably should not counter at all and should instead push non-cash levers (start date, PTO, title, bonus structure). ## Counter Offer Percentage by Company Tier Company tier matters because band widths differ. A 20% counter at a bootstrapped 40-person startup might be fantasy. The same 20% at Amazon L5 is routine. | Company tier | Examples | Base flex | Sign-on flex | Equity flex | |---|---|---|---|---| | FAANG + peers | Google, Meta, Amazon, Apple, Netflix, Microsoft | 5% to 12% | $20K to $100K+ | 20% to 50% | | Tier 2 / late-stage unicorns | Stripe, Databricks, Airbnb, Uber, Snowflake, Coinbase | 5% to 15% | $10K to $50K | 15% to 40% | | Established public tech | Salesforce, Oracle, IBM, SAP, Adobe | 3% to 10% | $5K to $30K | 10% to 25% | | Mid-stage startup (Series B to D) | Varies widely | 3% to 10% | $5K to $25K | 25% to 75% | | Seed / Series A | Varies widely | 0% to 8% | $0 to $15K | 30% to 150% | | Non-tech / traditional | Banks, consulting, retail tech | 2% to 8% | $0 to $20K | N/A or small | A pattern that surprises most first-time negotiators: at big tech companies, base salary is the hardest lever to move and equity is often the easiest. Recruiters are tightly boxed on base because raises roll off base every year. They have far more discretion on sign-on (a one-time cost) and equity (which vests over four years and partly masks the true dollar impact). If the recruiter says "the base is fixed," they are usually telling the truth. But they are almost never telling you the sign-on or equity is fixed, even if they imply it. ## The Three Data Points You Need Before Picking a Number Before you say a single number, get these three pieces of information. Most candidates skip step one entirely and wonder why they left money on the table. ### 1. The 75th percentile of market for your level and location Go to Levels.fyi. Filter by the exact company (or peer companies if the target is not listed), your level, and your metro. Look at the 75th percentile of total compensation, not the median. Your target number should land close to that 75th percentile. Why the 75th percentile? Because the median is what someone who took the initial offer without negotiating accepted. The 75th percentile is what someone who negotiated reasonably well ended up with. That is where you want to be. ### 2. Your BATNA (be honest about it) Write down what you would do if this offer disappeared tomorrow. Not what you would threaten to do. What you would actually do. The honest answer calibrates how aggressive you can be. - Two competing offers at peer-tier companies: aggressive counter, upper end of ranges above. - One competing offer of similar quality: standard counter, middle of the ranges. - One competing offer that is clearly worse: moderate counter, lean on non-cash levers. - No competing offers, but a strong current job: moderate counter. - No competing offers, no current job: conservative counter, focus on sign-on and non-base levers. We have seen many candidates bluff a competing offer that did not exist and get caught. Recruiters sometimes call the bluff by asking to see a redacted offer letter. Do not bluff. Use what you actually have. You will be surprised how much leverage even a modest BATNA provides when you use it honestly. ### 3. Band flexibility signals from this specific recruiter Recruiters leak information constantly if you listen for it. Things that signal wide band flex: - They volunteered equity or sign-on numbers before you asked. - They used phrases like "we have some room on this" or "what would make this work for you." - They asked what other companies you are talking to (they are trying to calibrate a counter). - The offer deadline is more than a week out. Things that signal narrow band flex: - "This is our best and final." - "Our comp is algorithmic, we cannot adjust it." - They refused to put the offer in writing for more than 24 hours. - The deadline is 48 hours or less. The first set means you can aim high. The second set means you should focus on one or two specific items rather than a broad counter. ## Real Examples: How Much Real Software Engineers Countered Abstract percentages are useful. Real numbers are more useful. Here are specific counters that worked, annotated with the leverage that made them work. **Jessica, Junior Front-End Developer at Microsoft, +$42K.** New grad offer. She had one other final-round loop at a smaller company, which was enough BATNA to counter the Microsoft base by 8% and push sign-on from $15K to $35K. Total TC impact was about $42K over year one. A new grad countering hard is the exception, not the rule, but it works when the data supports it. **Tony, Senior Data Scientist at Amazon, +$75K.** Amazon is famous for salary caps that push compensation into sign-on and equity. Tony countered by shifting most of the upside into year-one sign-on and a bumped equity grant, rather than fighting the base cap. That is the correct play at Amazon L5 and L6. Fighting base at Amazon is like trying to squeeze water from a stone. **Jonathan, Staff Software Engineer at Reddit, +$102K.** Staff level at a public company with real equity upside. Jonathan had a second offer from a peer company, which put the counter at the top of the L6 range. The counter moved base modestly, sign-on significantly, and equity by roughly 30%. Most of the $102K came from the equity adjustment compounded over the grant period. **Andrew, Staff Software Engineer at ParTech, +$100K.** The company opened with what they called a strong offer. Andrew countered anyway, with a specific justification tied to market data for his level in his metro. The counter moved base, added a performance bonus structure, and increased sign-on. Lesson: "good offer" is almost always 10% to 20% below "best offer" at staff level. **Edward, Senior Backend Engineer at StackAdapt, +18%.** Mid-sized ad-tech company. Edward did not have another offer in hand, but he had recent comp data from two friends at peer companies plus Levels.fyi benchmarks. The 18% improvement came mostly from base and sign-on, with a modest equity bump. This is a clean example of what you can do with data-driven leverage alone. These are five cases. Every single one involved a specific counter tied to a specific justification. Nobody walked in saying "I want more money." They walked in saying "based on this data, this is the number that makes sense." ## How to Actually Deliver the Counter Picking the number is the math. Delivering it is the craft. Here are three scripts we have seen work, calibrated to different leverage levels. ### Script 1: You have a competing offer > "Thanks again for the offer. I am genuinely excited about the team and the work. I do want to be transparent. I have another offer on the table with a total comp that is meaningfully higher, and I would like to see if we can close the gap. Specifically, I was hoping we could move base from $X to $Y, bring sign-on up to $Z, and add [number] more RSUs. If we can get close on those, this is where I want to be." Why this works: you led with enthusiasm, stated the BATNA without threatening, and gave specific numbers. The recruiter now has a concrete ask to take to the hiring manager and comp committee. ### Script 2: You have strong data but no competing offer > "I appreciate the offer and the time the team put into this. I have been doing my homework on market comp for this level, and based on data from Levels.fyi and a couple of peers at similar companies, the range for this level in this metro skews higher than the initial number. I would like to propose base of $Y, sign-on of $Z, and an equity refresh closer to [target]. I want to make this work. What kind of flexibility do you have?" Why this works: you did not claim a competing offer you do not have. You cited sources. You asked for flexibility rather than demanding. Recruiters respect the homework, and they often come back with 60% to 80% of the ask. ### Script 3: You are a new grad or have thin leverage > "Thank you for the offer. I am really excited about the role. Before I accept, I wanted to ask if there is any flexibility on the sign-on bonus or the initial equity grant. I know base can be hard to adjust for new grads, so I wanted to focus on those two areas if possible." Why this works: new grads who push hard on base sometimes get refused flatly. New grads who ask specifically about sign-on and equity often get meaningful movement. You are meeting the recruiter where their flexibility actually lives. In all three scripts, notice what is missing. No threats. No ultimatums. No "take it or leave it." Recruiters respond to partners, not adversaries. The best negotiators we have seen are almost disarmingly pleasant. They just happen to come prepared with specific numbers and specific justifications. > **Picking the number is the easy part. Defending it is where the money moves.** The moment you send the counter, the recruiter pushes back with a rehearsed line, and that reply is where most engineers fold and leave $30K+ behind, locked in as the base for every future raise. SalaryScript is the by-company, by-level playbook for that exact back-and-forth. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) (instant download, 14-day results-based guarantee). ## When to Counter Above 20 Percent (And When Not To) Countering above 20% on base is unusual. It can work in a few specific cases: 1. The initial offer is genuinely lowball. Check Levels.fyi. If the offer is at or below the 25th percentile for your level, a 20%+ counter is often justified. 2. You have two or more offers at peer-tier companies with meaningful TC differences. The highest becomes your anchor. 3. The role has significantly expanded scope versus what you interviewed for. This is rare, but it happens. 4. You are being leveled down. Sometimes the offer comes in at L4 when the scope is clearly L5. The right move is to push for a level bump, not just a comp bump. A level bump usually represents 25% to 40% in TC. Do not counter above 20% in these cases: 1. The initial offer is already at or above the 75th percentile for your level. 2. You have no BATNA and the company knows it. 3. The recruiter has clearly communicated a hard cap and explained why. 4. You are at a Seed or Series A startup where cash is genuinely constrained. A very aggressive counter in the wrong context can cause offer stalling or, in rare cases, rescission. In over a decade working with candidates and recruiters, we have almost never seen a good-faith negotiation rescinded. We have seen aggressive counters with no supporting justification cause recruiters to slow-walk the process and sometimes lose executive sign-off. Know which situation you are in. ## The Mistakes That Cost Engineers Tens of Thousands We see these patterns every week. Any one of them can cost $20K to $200K over the life of the offer. **Mistake 1: Accepting verbally before seeing the written offer.** Once you say yes on a call, the recruiter stops fighting for your number. Always ask for the offer in writing before giving any indication of acceptance. **Mistake 2: Giving a number first.** If the recruiter asks what you are looking for, deflect. "I would love to understand the full package first before discussing specific numbers." The first number on the table anchors the entire negotiation. Let them put it there. **Mistake 3: Countering only base.** Base is the hardest lever. Sign-on and equity are where the movement usually lives. A smart counter touches all three. **Mistake 4: Using a deadline you did not set.** If the recruiter says "we need an answer by Friday," ask for more time. Almost every deadline is soft. "I want to give this the consideration it deserves. Can we push to next Wednesday?" is a sentence that has literally saved candidates tens of thousands of dollars. **Mistake 5: Burning bridges by threatening.** "If you cannot match this, I am taking the other offer" puts the recruiter on the defensive. "I would really like to work here, and I want to see if there is a way to close this gap" puts them on your side. Same leverage. Very different reaction. **Mistake 6: Forgetting the refresh.** Your initial equity grant is only part of the story. At most big tech companies, annual refresh grants make up 30% to 50% of your long-term comp. Always ask what the typical refresh looks like at your level. Companies that refuse to discuss it are signaling something. **Mistake 7: Not negotiating relocation, PTO, start date, or title.** These are free moves. The recruiter often has unilateral authority over them. Even if you cannot get more cash, you can usually get a better start date, a title bump, or extra PTO. Amanda, a Product Manager we worked with, closed almost $60K across three offers partly by stacking these non-cash wins alongside cash moves. ## Frequently Asked Questions ### Is countering 20% too much? For most software engineer offers at FAANG, tier-2 tech, and late-stage unicorns, 20% on base is aggressive but not unreasonable. On total compensation, 20% to 30% is the standard band at L5 and above. The number is only "too much" if you cannot justify it with market data or a competing offer. ### How long should I take before countering? Ask for the offer in writing, then take two to five business days to review and respond. Faster than two days and you look desperate. Slower than a week and the recruiter starts to worry. If you need more time because you are waiting on another offer, be transparent about it. Most recruiters will extend deadlines to avoid losing you to a competitor. ### Should I always counter every offer? Almost always yes. Even a polite counter with minimal leverage typically nets $5K to $15K of movement, and often more on sign-on or equity. The only time not to counter is if the offer is already above the 90th percentile for your level and you have no competing data. Even then, asking about sign-on or PTO costs you nothing. ### What if the recruiter says "this is our best and final"? Almost nobody says best and final on the first pass. When they do, test it politely: "I understand. Is there any flexibility on sign-on or the initial equity grant specifically?" If they say no to everything, you have your answer and you can decide. If they say yes to one of them, best and final was not actually best and final. ### Can the company rescind the offer if I counter? In good faith, with reasonable asks, and without threats or bluffs, rescission is extremely rare. We have seen it a handful of times across thousands of negotiations, and in every case the candidate did something genuinely unprofessional (lied about a competing offer, demanded an immediate answer, used confrontational language). Professional negotiations do not get rescinded. They just get resolved. ### What about stock options at startups, not RSUs? Stock options at early-stage startups are a different math problem. The counter usually focuses on the option count, the strike price, and the acceleration terms on a liquidity event. Base salary is typically less negotiable because cash is constrained. If you are negotiating with a Seed to Series B startup, push for a larger option grant and single-trigger or double-trigger acceleration on change of control rather than a higher base. ### Is it okay to counter with exact numbers instead of a range? Yes, and it is usually better. Exact numbers signal that you have done the math. Ranges signal that you are hoping. Say "I was hoping we could get base to $215K and sign-on to $50K" rather than "I was hoping for something in the $210K to $220K range for base." ### How much does negotiating actually matter long term? More than almost any other career move. If you accept an offer $30K below what you could have gotten, that gap compounds. Raises and future offers are benchmarked against your current comp. Over a 10-year career, a single missed negotiation can cost $300K or more. That is why the math on spending a weekend preparing for this conversation is so lopsided. A few hours of work can change the shape of your financial life for a decade. ## Before You Hit Send If you are about to send your counter, run through this short checklist: 1. You know the 75th percentile of market for your exact level and metro. 2. Your counter number lands close to or slightly above that 75th percentile. 3. You have at least one justification for the number (competing offer, market data, recent comp history). 4. You are asking for base, sign-on, and equity together, not just base. 5. Your message leads with enthusiasm and ends with collaboration, not a threat. 6. You have a specific number in mind for each lever, not a range. 7. You are prepared for the recruiter to come back with 60% to 80% of your ask. If all seven are true, you are ready. The rest is pushing send. Most candidates we have worked with net between $15K and $100K above their initial offer, with outliers well beyond that at staff and principal levels. The difference between the candidates who net $15K and the ones who net $100K is not talent or luck. It is preparation. Everything in this guide is the preparation. If you would rather start from ready-to-send wording, our [counter-offer email templates](/blog/salary-negotiation-email-templates/) cover each of these scenarios: the competing-offer counter, the market-data counter, sign-on, equity, and the "push past best and final" follow-up. If you want the complete set of scripts, including the exact wording for follow-ups, the equity counter, the relocation counter, and the "push past best and final" script, that is what [SalaryScript](/#pricing) is built for. Over 1,200 tech professionals have used it to negotiate better offers at Google, Meta, Amazon, Microsoft, Reddit, Stripe, and hundreds of other companies. The average reader keeps $30K to $100K that would otherwise have stayed with the company, money that compounds into every raise and future offer benchmarked off the higher base. But even without any product at all, the framework in this article is enough to move your offer meaningfully. Do the homework, pick the number, send the counter. The worst case is they say no to part of it. The best case is the difference between this offer and the life you actually wanted. Related reading: [The Complete FAANG Salary Negotiation Guide](/blog/faang-salary-negotiation-guide/), [Salary Negotiation Email Templates](/blog/salary-negotiation-email-templates/), and [How to Negotiate Your Salary After Receiving a Job Offer](/blog/how-to-negotiate-salary-after-job-offer/). ## Salary Negotiation Email Templates: 12 Real Examples (2026) URL: https://salaryscript.com/blog/salary-negotiation-email-templates/ Published: 2026-04-19 (updated 2026-06-12) Description: 12 copy-paste salary negotiation email templates: counter-offer, sign-on, equity, and follow-up emails used by FAANG hires to add $30K–$300K to tech offers. Recruiters read a lot of negotiation emails. Most of them sound the same. "I just wanted to follow up." "I was wondering if there's any flexibility." "Thank you so much for the offer, I'm really excited about the opportunity." Polite, safe, and entirely forgettable. The ones that actually get money moved read differently. They are short. They name specific numbers. They lead with enthusiasm and close with collaboration. They sound like a professional making a request, not a candidate hoping for a favor. Below are 12 salary negotiation email templates and counter offer email examples for every stage of a software engineer offer negotiation: the first response, the counter with and without a competing offer, sign-on and equity asks, the "best and final" pushback, and the follow-up. We wrote them based on patterns we have seen work across more than 1,200 offer negotiations at FAANG, tier-2 tech, and late-stage startups. Copy them, adapt them, use the language that fits your situation. But do not send anything without reading the next section first, because the structure matters more than the words. > ⚡ **Want it auto-written?** [Generate your counter-offer email free →](/salary-negotiation-email-generator/). Enter your offer numbers and copy a ready-to-send draft in seconds, then come back for the scenario-specific wording below. ## Jump to the template you need 1. [First response to an offer](#template-1-first-response-to-an-offer): buy yourself days of thinking room without giving anything away 2. [Asking for more time](#template-2-asking-for-more-time): extend the deadline cleanly 3. [Counter with a competing offer](#template-3-the-counter-with-a-competing-offer): the highest-leverage situation 4. [Counter without a competing offer](#template-4-the-counter-without-a-competing-offer): market-data anchored 5. [Pushing past "best and final"](#template-5-pushing-past-best-and-final): test the claim on non-base levers 6. [Sign-on bonus only](#template-6-negotiating-the-sign-on-bonus-specifically): the unvested equity argument 7. [Equity / RSU grant only](#template-7-negotiating-equity-and-rsu-grants): where the most movement lives 8. [Relocation](#template-8-negotiating-relocation): almost always partially granted 9. [Title / level bump](#template-9-asking-for-a-title-bump): the highest-impact ask of all 10. [Start date and PTO](#template-10-negotiating-start-date-and-pto): free wins 11. [Follow-up after silence](#template-11-the-follow-up-after-silence): when the counter sits for days 12. [Accepting gracefully](#template-12-accepting-gracefully): close the negotiation like a future colleague ## Salary negotiation email vs salary negotiation letter A quick note on terminology, because the search results for both phrases land on the same kind of page. A "salary negotiation letter" and a "salary negotiation email" are the same thing in 2026: a written, asynchronous counter sent to your recruiter. Nobody mails physical letters for offer negotiations anymore. The templates below work whether you are searching for an email template, a letter template, a pay negotiation letter, or a written counter-offer. The format, structure, and language are identical. Some recruiters and HR teams still call the document a "letter" out of habit; the content is the same. ## How to Write a Salary Negotiation Email: The 5-Part Anatomy Every email below follows the same five-part structure. It works because it mirrors how recruiters actually process these messages. 1. **Open with enthusiasm.** Genuine, specific, about the role or the team, not generic "excited about the opportunity" corporate speak. 2. **Bridge to the ask.** One short sentence. "I wanted to see if we could revisit a few items in the offer." 3. **State specific numbers.** Base, sign-on, equity, each with a target number. Vague asks get vague responses. 4. **Provide one sentence of justification.** Market data, competing offer, or internal anchor. Not a wall of text. 5. **Close collaboratively.** "I want to make this work" or "let me know what's possible" or an equivalent. Four to eight sentences total. That is the format. Any email longer than that is almost certainly bleeding leverage. The templates below all land in that range. One more note before we get into the templates. Read every email aloud before you send it. If it sounds like something a human would actually say, it will land. If it sounds like a form letter, recruiters will treat it like one. ## Template 1: First Response to an Offer Use this within two hours of receiving a verbal or emailed offer. Goal: buy time, get everything in writing, avoid accidentally anchoring yourself. > Subject: Thank you, and a quick ask > > Hi [Recruiter Name], > > Thank you so much for the offer. The conversations with [hiring manager] and the team have been some of the most substantive I've had in a while, and I'm genuinely excited about what you're building. > > Could you send over the full written offer with base, sign-on, equity breakdown, and benefits? I want to give this the consideration it deserves and walk through the details with my family this weekend. > > Appreciate your patience. I'll plan to get back to you by [date, 3 to 5 business days out]. > > Best, > [Your Name] What this does: it closes the verbal conversation without giving the recruiter any information they can use to anchor the offer. It establishes that you are going to review the written details. It sets a reasonable timeline that you control. It does not reject, accept, or signal interest in negotiating yet. You have bought yourself days of thinking room. ## Template 2: Asking for More Time Use this if the original deadline is shorter than you need, or if a competing offer is still in motion. > Subject: Quick request on timing > > Hi [Recruiter Name], > > I'm working through the offer carefully and want to give it the full consideration it deserves. Would it be possible to extend the deadline to [specific date]? I'm also finishing up a conversation with another team I've been in process with, and I'd like to be able to give you a clean yes rather than a rushed one. > > Happy to jump on a call if it helps. Thanks for being flexible. > > Best, > [Your Name] A few things this template does well. It treats the extension as reasonable, not a favor. It hints at a competing process without making it a threat. It closes with an offer to talk, which makes the request feel collaborative rather than avoidant. Most recruiters will grant 3 to 7 extra days without pushback. ## Template 3: The Counter With a Competing Offer This is the highest-leverage situation. Use this template when you have a real, comparable offer in hand. > Subject: Re: offer discussion > > Hi [Recruiter Name], > > Really appreciate you putting this together. I've been talking with my wife about the role, and I want to be transparent: I've also received another offer with a total comp package that comes in meaningfully higher. > > I'd genuinely prefer to join [Company]. The team, the product roadmap, and the scope of the role are all a better fit. That said, to make the decision work, I was hoping we could look at the following: > > - Base: $[target number] > - Sign-on: $[target number] > - Initial equity grant: [target number of RSUs or $ value] > > These numbers would put me in line with what the other offer would pay out over year one. I want to make this work. Let me know what's possible. > > Best, > [Your Name] Why this works: the recruiter now has a concrete ask to bring to the hiring manager and comp committee. The language is specific but not confrontational. The phrase "I'd genuinely prefer to join" signals that the deal is winnable, which matters because recruiters fight harder for candidates they think they can close. If you leave the recruiter thinking you'll probably take the other offer regardless, they will not push internally for you. If they think you'll sign if the math works, they will. Jonathan, a Staff Software Engineer, used this framing at Reddit with a competing offer from a peer tier-2 company. The counter moved his total comp up by $102K over the initial offer. The key is specificity. Numbers he could have vaguely hoped for did not work. Specific numbers tied to an anchor did. ## Template 4: The Counter Without a Competing Offer This is the harder case, but also the more common one. Use this when you have good market data but no second offer. > Subject: Re: offer discussion > > Hi [Recruiter Name], > > Thanks again for walking me through the offer. I've spent the last few days looking at market comp for [level] in [metro], pulling from Levels.fyi and a couple of data points from peers at similar companies. Based on that, I'd love to see if we can close some gaps. > > Specifically, I was hoping we could land on: > > - Base: $[target] > - Sign-on: $[target] > - Initial RSU grant: [target] > > I know base is often the toughest lever, so if there's more flexibility on the sign-on and equity side, I'm open to that as well. I'm really bought in on this team and want to find a version of this that works for both of us. > > Best, > [Your Name] Two things make this template land. First, the explicit reference to market data means the recruiter is not fighting an abstract ask. They're fighting a data-backed one, which is harder to dismiss internally. Second, the sentence that acknowledges base is hard signals that you understand how recruiters actually operate, which builds trust. Recruiters respond to candidates who seem to know how the machine works. Edward, a Senior Backend Engineer, used this shape at StackAdapt with only market data, no competing offer. He closed an 18% improvement on the initial package. Market-data counters work. They just need to be specific. Market-data counters also draw the most practiced pushback. With no competing offer in hand, the recruiter usually comes back with some version of "that is already strong for your level," and this is where most candidates stall, because they wrote the opening email and never planned the reply. You will likely see that response within a day or two of sending the counter above, with $20K to $60K riding on what you say next. [SalaryScript](/#pricing) gives you the exact counter for each version of that "no," so you answer in an hour instead of caving. ## Template 5: Pushing Past "Best and Final" Use this when the recruiter has claimed the offer is already at its limit, but you believe there is still room. > Subject: Quick follow-up > > Hi [Recruiter Name], > > Thanks for checking with the hiring manager. I completely understand base can be hard to move at this stage. > > Before I make a decision, I wanted to ask about two specific things: > > 1. Is there any room on the sign-on bonus, even $[smaller number more achievable]? > 2. Could we look at the initial equity grant? I've seen [level] grants at [company] come in higher in the public data, and I want to make sure the long-term comp makes sense. > > I know you've gone to bat for me already. I appreciate it, and I'm close to being able to say yes. > > Best, > [Your Name] This template respects the recruiter's previous effort, which is important. It then tests the "best and final" claim on two specific non-base levers where flexibility is most likely to live. The language "I'm close to being able to say yes" signals that a small move closes the deal, which gives the recruiter a strong internal case. This is the template that usually unlocks one last $10K to $30K of movement on sign-on or equity. Here is the part the template cannot carry for you. "Best and final" is rarely final, and the recruiter has a rehearsed answer ready for whatever you send back. This is the single most common place engineers fold, and the reply usually lands the same week you counter, with one shot to get it right. [SalaryScript](/#pricing) lays out the counter-moves for every flavor of "best and final," calibrated by company and level, plus the calm wording that keeps the offer warm after you push one more time. ## Template 6: Negotiating the Sign-On Bonus Specifically Use this when base has been frozen and you want to focus firepower on sign-on. > Subject: Question on sign-on > > Hi [Recruiter Name], > > Understood on the base being fixed. I do want to surface one thing: I'm leaving unvested equity at my current company worth roughly $[amount]. A sign-on of $[target number] would help bridge that gap and make the transition clean. > > Even half of that would put the decision in a very different place. Is there any room to work with there? > > Best, > [Your Name] The unvested equity argument is underused and extraordinarily effective. Recruiters understand that you are leaving real money on the table to join them, and most companies have specific sign-on budgets designed to cover exactly that gap. Even if you are not leaving meaningful unvested stock, a smaller version of this same argument works: moving costs, lost bonus potential, or the opportunity cost of leaving a current role. Tony, a Senior Data Scientist, used this framing at Amazon where base is heavily capped. The counter shifted most of the upside into sign-on and equity, totaling $75K above the initial offer. ## Template 7: Negotiating Equity and RSU Grants Use this when you believe the equity component is light compared to the level. > Subject: Quick thought on the equity component > > Hi [Recruiter Name], > > One thing I wanted to surface. Looking at Levels.fyi data for [level] at [company], the initial RSU grant tends to skew higher than what's in the current offer. I realize grants vary by candidate, but I was hoping we could revisit the equity number specifically. > > Target would be [number] RSUs (roughly $[dollar value] at current share price), which lines up with the 60th to 75th percentile of recent grants at this level. > > I'm happy to share the data I'm working from if that's helpful. > > Best, > [Your Name] Equity is the most negotiable lever at most big tech companies and simultaneously the one candidates least often push on. Framing the ask with public data makes it nearly impossible for a recruiter to dismiss. The offer to share your data points is a nice touch that signals you are being transparent and collaborative. Andrew, a Staff Engineer at ParTech, pushed equity as part of a broader counter and added $100K to what the company had initially called a "good offer." Staff-level equity grants have the most variability, which means they have the most room. Equity is also where recruiters lean hardest on "our grants are standardized," and the right answer depends entirely on the company. The RSU lever that moves at Google is not the one that moves at Amazon, Netflix, or a pre-IPO startup. [SalaryScript](/#pricing) breaks the equity levers down company by company, with the real grant bands by level and the wording that gets past "standardized," so your ask lands in the range that is actually reachable instead of the one the recruiter wants you to accept. ## Template 8: Negotiating Relocation Use this if you are relocating and the original relocation package feels thin. > Subject: Relocation question > > Hi [Recruiter Name], > > Quick one on relocation. Based on current market rates, moving from [city] to [city] with my family will run somewhere in the $[estimate] range between movers, temporary housing, and the lease-break fee on my current place. The $[current relocation offer] allowance covers part of that but leaves a meaningful gap. > > Is there flexibility on the relocation amount, or a tiered relocation package I might qualify for? Even a one-time bump would help make this a clean move. > > Best, > [Your Name] Relocation asks are almost always granted partially and sometimes fully. Companies budget for relocation specifically and it often sits outside the main comp band, which means you can increase relocation without cutting into the harder-to-move base or sign-on numbers. Itemizing your actual costs makes the ask feel documented rather than speculative. ## Template 9: Asking for a Title Bump Use this when the offer came in at a level that feels below the scope you interviewed for. > Subject: Thought on leveling > > Hi [Recruiter Name], > > One thing I've been thinking about since the offer came in. Based on the scope we discussed during the interview loop, particularly around [specific responsibility: leading X, owning Y, managing Z], the role feels closer to a [target level] than a [current level offered]. I want to raise this now rather than six months in. > > Would it be possible to revisit the leveling, either a title bump to [target] or an accelerated path with a defined timeline to get there? I'd rather have this conversation up front than find myself doing [target level] work at [current level] comp. > > Best, > [Your Name] Level bumps are the highest-impact negotiation move available. A successful bump from L4 to L5 typically means 25% to 40% more in total compensation, not just a one-time bump in base. This template works when your interview loop was genuinely at the higher level. If the scope truly is at the lower level, pushing for a bump will backfire. ## Template 10: Negotiating Start Date and PTO Use this for the easiest wins in the negotiation. Both often cost the recruiter nothing to grant. > Subject: Start date and PTO > > Hi [Recruiter Name], > > Two quick logistics items. > > First, I'd like to push my start date to [specific date, usually 4 to 6 weeks out]. I want to wrap up cleanly at my current role and take a short break before starting, so I can come in fresh. > > Second, I noticed the PTO is [current PTO]. Given my previous tenure in the industry, could we adjust to [target PTO, often 5 extra days]? > > Thanks for working through these with me. Almost there. > > Best, > [Your Name] These two asks are typically approved with no internal escalation at all. Most recruiters have direct authority over start date and mid-level discretion over PTO. This is free money in the sense that it costs nothing in negotiation capital and almost always lands. ## Template 11: The Follow-Up After Silence Use this if your counter has been out for three or more business days with no response. > Subject: Just checking in > > Hi [Recruiter Name], > > Hope your week is going well. Just wanted to check in on the counter we discussed. I know these things take a few internal conversations, and I don't want to rush, but I also want to make sure I'm not waiting on something that fell through the cracks. > > Happy to jump on a quick call if that's easier than email. Let me know. > > Best, > [Your Name] The key word here is "fell through the cracks." It gives the recruiter a graceful out if they forgot, while also gently surfacing that you are still waiting. No pressure, no edge, just a friendly nudge. Recruiters are juggling multiple candidates, and counters genuinely do get stuck in internal approval queues. A polite follow-up is expected and rarely costs you anything. ## Template 12: Accepting Gracefully When the negotiation closes and you have a final number you are happy with. > Subject: Signing and thank you > > Hi [Recruiter Name], > > Thank you for working through this with me. The final package is one I feel genuinely good about, and I'm looking forward to joining the team. > > Please send over the updated offer letter when ready, and I'll countersign the same day. Let me know what else you need from me on the onboarding side. > > Really appreciate the partnership through this process. > > Best, > [Your Name] Negotiation is a long relationship. Recruiters talk to each other across companies and they remember candidates. The way you close the negotiation sets the tone for your first year at the company. Close it warmly. It costs nothing and it builds a real ally inside the company before day one. ## Five Common Mistakes in Negotiation Emails Even with the right templates, the wrong framing can kill a negotiation. These are the patterns we see derail otherwise strong counters. **Mistake 1: Apologizing for the ask.** Phrases like "I hate to ask" or "I know this is awkward but" signal low leverage and invite the recruiter to say no. The ask itself is normal. Treat it as normal. **Mistake 2: Using hedges in the numbers.** "I was thinking maybe around $200K or so if that works for you" is weaker than "I was hoping we could land at $215K on base." Hedging signals you don't really believe your own number. Recruiters use that. **Mistake 3: Writing a wall of text.** Any email longer than 10 sentences is too long. Negotiation emails that succeed are almost always under 150 words. Extra words dilute the ask. **Mistake 4: Mentioning feelings instead of facts.** "I feel like my experience justifies more" is weaker than "the 75th percentile for this level in this metro is $X." Recruiters cannot take feelings to the comp committee. They can take data. **Mistake 5: Ending with a passive close.** "Please let me know your thoughts" is weaker than "happy to hop on a call tomorrow afternoon if that's easier than email." Close with a specific next step, not an open question. ## One Sentence of Strategic Advice Most software engineers lose tens of thousands of dollars not because they sent the wrong email, but because they sent no email at all. The gap between a strong counter and no counter is usually $15K to $100K. The gap between a perfect counter and a merely good counter is more like $5K to $20K. Which is to say, if you are torn between "I'm not sure what to write" and "write something reasonable and send it," send something reasonable. The upside is enormous and the downside is essentially zero. Every template in this guide is reasonable. Pick the one that fits your situation, swap in your numbers, and hit send. The 12 templates above get your counter sent. What they can't do is carry the back-and-forth that follows, when the recruiter pushes back, re-anchors low, or stalls for a week. That's what [SalaryScript](/#pricing) is built for: a counter-move for every recruiter tactic, calm responses when they pressure you, and real case studies from the 1,200+ engineers who've used it to net $30K to $100K above their first offer. The templates on this page are enough to move most offers, and you should send one today. But if you are looking at a live offer right now and the recruiter has already started pushing back, that next reply is where the money is won or lost. [Get SalaryScript before you send it · $129](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b), instant download, 14-day results-based guarantee, or [compare all plans from $39](/#pricing). Related reading: [How Much Should You Counter a Software Engineer Job Offer?](/blog/how-much-to-counter-software-engineer-offer/), [How to Negotiate Salary After a Job Offer](/blog/how-to-negotiate-salary-after-job-offer/), and [The Complete FAANG Salary Negotiation Guide](/blog/faang-salary-negotiation-guide/). ## Frequently Asked Questions ### What is the best way to start a salary negotiation email? Start with genuine enthusiasm about the role and the team, then bridge into the negotiation with a simple transitional phrase like "I had a chance to review the full package and wanted to see if we can make the numbers work." Never open with a demand. Recruiters read the first three lines and decide whether you are a partner or a problem. ### Should I negotiate by email or by phone? Email is almost always better for the initial counter. It gives you time to pick exact numbers, prevents you from anchoring too low on a live call, and creates a paper trail that reduces miscommunication. Phone is fine for follow-up discussion after the written counter has been sent. ### How do I counter an offer without a competing offer? Lead with specific market data rather than a competing offer. Cite Levels.fyi, H1B salary disclosures, or specific peer data points for your exact level and metro. Ask for a specific number on each lever (base, sign-on, equity) and frame it as "finding what works" rather than demanding a specific amount. See [Template 4](#template-4-the-counter-without-a-competing-offer) above for the exact wording. ### How long should a salary negotiation email be? Keep it short. Four to eight sentences is the sweet spot. Your goal is to communicate enthusiasm, state your specific asks, provide brief justification, and invite the recruiter to respond. Long emails signal insecurity. Short, specific emails signal that you have done the math. ### How many times can I counter in a salary negotiation? Usually one or two rounds total. The first counter is the big one. If the recruiter comes back with 60% to 80% of your ask, a single follow-up to split the difference on one or two remaining items is normal. A third counter can start to feel aggressive and rarely moves the needle much. ### What should I do if the recruiter does not respond to my counter email? Wait three business days, then send a brief follow-up that checks in without adding pressure. Recruiters are busy and counters often require sign-off from the hiring manager and comp committee. If there is no response after a second follow-up three days later, a polite phone call is appropriate. [Template 11](#template-11-the-follow-up-after-silence) has the exact follow-up wording. ### Can I negotiate a job offer over email only? Yes. Entire negotiations are routinely handled by email. Some candidates prefer it because it removes the pressure of a live call. The only time a phone call is genuinely necessary is if the recruiter requests one or if the negotiation has been stuck for more than a week and something is clearly lost in translation. ### Should I mention a competing offer in the email if I have one? Yes, if the offer is real and comparable. Mention it briefly and specifically. You do not need to name the company if you do not want to, but you should be prepared to share the offer letter if the recruiter asks for verification. Never invent a competing offer. Recruiters talk to each other and bluffs get caught surprisingly often. ## How to Negotiate Salary After a Job Offer (Tech) URL: https://salaryscript.com/blog/how-to-negotiate-salary-after-job-offer/ Published: 2026-03-15 (updated 2026-07-01) Description: A step-by-step framework for negotiating a higher salary after you've received a tech job offer, without risking the offer or burning bridges. You just got the offer email. The title is right, the team seems great, and you're genuinely excited. Then you scroll down to the comp section, and a thought creeps in: *Is this the best they can do?* Almost certainly not. In our experience helping over 1,200 tech professionals negotiate their offers, we've seen a consistent pattern: **the initial offer is rarely the final offer.** Companies build negotiation room into their budgets. Recruiters expect you to push back. The question isn't whether you *can* negotiate. It's whether you know *how*. This guide walks you through the exact process, from the moment you receive an offer to the moment you sign a number you're genuinely happy with. ## Why You Should Always Negotiate (Even If You're Happy With the Offer) Let's address the fear first. Most candidates worry about three things: 1. **"What if they rescind the offer?"** In over a decade working in and around FAANG hiring, we've almost never seen this happen from a professional, good-faith negotiation. Companies invest thousands of dollars in recruiting you. They're not going to throw that away because you asked for more. 2. **"I don't want to seem greedy."** Recruiters negotiate comp packages every single day. It's a normal part of their job. Asking for what you're worth isn't greedy. It's professional. 3. **"I'm not senior enough to negotiate."** This is the most expensive myth in tech. Entry-level offers at large companies routinely have $20K–$50K of room. Staff and principal-level offers can move by $100K+. Here's the real cost of not negotiating: if you accept an offer that's $30,000 below what you could have gotten, that gap compounds. Raises and future offers are benchmarked against your current comp. Over a 10-year career, that single missed negotiation can cost you $300,000 or more. ## Step 1: Don't React Immediately When the recruiter calls or emails with the offer, your first move is to **express gratitude and buy time**. Never accept, reject, or counter on the spot. Here's what to say: > "Thank you so much! I'm really excited about this opportunity and the team. I'd love to take a couple of days to review the full package. Can you send over the details in writing?" This does three things: - It shows enthusiasm (recruiters want to close candidates who are excited) - It gets everything in writing so you can analyze the full picture - It gives you time to prepare a proper counter **How much time?** 2–3 business days is standard. If you have competing timelines, be transparent about it. Recruiters would much rather wait than lose you. ## Step 2: Understand the Full Compensation Package Salary negotiation in tech isn't just about base pay. A typical offer at a mid-to-senior level includes: - **Base salary:** your annual cash compensation - **Equity/RSUs:** stock grants, typically vesting over 4 years - **Sign-on bonus:** one-time cash (sometimes split across two years) - **Annual bonus:** target percentage of base (often 10–15% at FAANG) - **Refresher grants:** additional equity granted each year to retain you - **Benefits:** relocation, PTO, 401k match, wellness stipends A common mistake is fixating on base salary while ignoring RSU upside or a sign-on that could be worth tens of thousands. Before you counter, understand which levers you can pull and which ones have the most room. **Pro tip:** At many large tech companies, base salary has a hard cap per level. If you're hitting that ceiling, the recruiter physically cannot increase it, but they often *can* increase RSUs or sign-on significantly. Know which levers to pull for the company you're negotiating with: the lever that moves at [Google](/google-salary-negotiation/) (equity) is not the one that moves at [Amazon](/amazon-salary-negotiation/) (sign-on) or [Netflix](/netflix-salary-negotiation/) (base, since all comp is cash). We keep per-company playbooks for [Google](/google-salary-negotiation/), [Meta](/meta-salary-negotiation/), [Amazon](/amazon-salary-negotiation/), [Apple](/apple-salary-negotiation/), [Netflix](/netflix-salary-negotiation/), [Microsoft](/microsoft-salary-negotiation/), [Nvidia](/nvidia-salary-negotiation/), [OpenAI](/openai-salary-negotiation/), [Stripe](/stripe-salary-negotiation/), and [Uber](/uber-salary-negotiation/). ## Step 3: Determine Your Target Number Your counter needs to be grounded in reality, not pulled from thin air. Here's how to build a credible target: ### Research market data Use [levels.fyi](https://levels.fyi) to find reported compensation for your exact role, level, and location. Focus on the median and 75th percentile. This gives you a realistic range. ### Factor in your leverage Your negotiating power depends on several factors: - **Competing offers:** the single strongest lever you can have - **Specialized skills:** ML, infra, security, and other high-demand specialties command premiums - **Current compensation:** relevant as a floor (you shouldn't take a pay cut without good reason) - **Market conditions:** how aggressively the company is hiring right now ### Set a range, not a single number Decide on: - **Your target:** where you realistically want to land - **Your stretch:** the number you'd ask for, knowing they'll meet somewhere below - **Your walk-away:** the minimum you'd accept Counter with your stretch number. If the initial offer is $180K total comp and you want $210K, ask for $225K–$230K. This gives the recruiter room to "work with you" and still land where you want. ## Step 4: Frame the Counter Around Value, Not Need This is where most people get it wrong. They say things like: > ❌ "I was hoping for more because my rent is really high." > > ❌ "My friend at Google makes $50K more." > > ❌ "I need at least $200K to make this work." These frames make it about *you*, not about *them*. Recruiters are advocates internally. They go to their comp team to get approval. Give them ammunition. Instead: > ✅ "I'm genuinely excited about this role and the team. Based on my research and conversations with others at similar levels, I was expecting total comp closer to [target]. Given my experience with [specific relevant skill/project], I believe that reflects the value I'd bring. Is there flexibility to close that gap?" This works because: - You reaffirm your excitement (they need to know you'll accept if they move) - You cite research, not feelings - You highlight specific value you bring - You ask an open question rather than issuing an ultimatum ## Step 5: Handle the Recruiter's Response There are three typical responses. Here's how to handle each: ### "Let me see what I can do" This is the best case. The recruiter is going to bat for you internally. Thank them, reiterate your enthusiasm, and wait. Don't pester. One follow-up email after 2–3 days is appropriate. ### "This is already at the top of the band" This is often a negotiation tactic, not a fact. Respond with: > "I appreciate that. I know comp bands can be tight. If base is at the ceiling, is there flexibility on the equity side or sign-on? Those are also meaningful to me." By shifting the conversation to other levers, you're making it easier for them to find room. ### "We can't move on this" If they truly can't move (and sometimes they genuinely can't, especially at smaller companies with tighter budgets), consider negotiating non-comp items: start date, remote flexibility, title, learning budget, or a 6-month performance review with a defined path to a raise. > **This reply is where the money is actually won or lost.** The three responses above are the openers. What you send back when the recruiter re-anchors, claims best-and-final, or goes quiet is the part most engineers fumble, usually within the same week, with one shot to get it right and $30K+ riding on the wording. SalaryScript is the by-company, by-level playbook for that exact back-and-forth, so you are not improvising the most expensive email of your year. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) (instant download, 14-day results-based guarantee). ## Step 6: Handle Multiple Offers Strategically If you have competing offers, you're in the strongest possible position. But there's a right way and a wrong way to use them. **Do:** - Be transparent that you have other options: *"I'm fortunate to be evaluating a couple of opportunities right now"* - Share the competing comp range if it helps your case - Give each company a fair chance to compete **Don't:** - Fabricate offers. Recruiters talk to each other, especially within the same market. - Play companies against each other in a rapid-fire bidding war. It signals you'll leave for $5K more. - Use an offer you'd never accept as leverage. If called on it, you have nothing. The most effective approach: tell your preferred company what it would take for you to sign. Make it easy for them to win. ## Step 7: Get It In Writing, Then Accept Once you reach verbal agreement, ask for an updated offer letter before you formally accept. Review every line. We've seen cases where verbal promises didn't make it into the written offer. Check that the letter includes: - Updated base salary - Equity grant amount and vesting schedule - Sign-on bonus and any clawback terms - Start date - Any special terms you negotiated (remote work, title, etc.) Once everything matches, sign it with confidence. You've earned this. ## Common Mistakes That Cost Candidates Thousands After working with over 1,200 tech professionals, these are the patterns we see repeatedly: **Negotiating too early.** Don't bring up comp during interviews. Wait until you have a written offer. That's when you have maximum leverage. **Accepting too quickly.** The excitement of getting an offer leads people to say yes within hours. Even 48 hours of patience can be worth $30K+. **Only negotiating base salary.** At companies like Google, equity can be 40–60% of total comp. If you only negotiate base, you're leaving the biggest lever untouched. **Being adversarial.** Negotiation isn't a fight. The recruiter is your advocate. Help them help you. Be firm but collaborative. **Not practicing.** The first time you say your counter number shouldn't be on the phone with the recruiter. Practice with a friend or out loud until it feels natural. ## The Bottom Line Every dollar you negotiate at the offer stage is a dollar that compounds throughout your career. A $30,000 increase today translates to hundreds of thousands over a decade through raise percentages, future offers benchmarked against your comp, and compound investment returns. The companies expect you to negotiate. The recruiters are prepared for it. The only person who loses when you don't negotiate is you. --- *Accepting without negotiating doesn't cost you once. The $30K–$300K you leave behind becomes the base for every raise, refresher, and future offer that follows. SalaryScript gives you the word-for-word frameworks FAANG insiders use to keep that money, with real case studies showing exactly how it's done. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) or [compare all plans from $39](/#pricing).* Related reading: [Salary Negotiation Email Templates](/blog/salary-negotiation-email-templates/) (12 copy-paste counters, sign-on asks, and follow-ups), [How Much Should You Counter a Software Engineer Offer?](/blog/how-much-to-counter-software-engineer-offer/), and [The Complete FAANG Salary Negotiation Guide](/blog/faang-salary-negotiation-guide/). ## FAANG Salary Negotiation Guide 2026: Per-Company Tactics URL: https://salaryscript.com/blog/faang-salary-negotiation-guide/ Published: 2026-03-14 (updated 2026-07-01) Description: How comp really works at Google, Meta, Amazon, Apple & Netflix: per-company FAANG salary negotiation tactics from insiders who've closed 1,200+ offers. Generic salary negotiation advice breaks down at FAANG companies. The comp structures are fundamentally different from the rest of the industry. The recruiter dynamics are different. The internal approval processes are different. If you're negotiating an offer from Google, Meta, Amazon, Apple, or Netflix, you need to understand how *their specific system* works, not just "how to negotiate a salary." This guide is based on our team's combined 30+ years working inside these companies, plus the patterns we've observed helping over 1,200 candidates negotiate their FAANG offers. ## How FAANG Compensation Actually Works Before you can negotiate effectively, you need to understand the machine you're negotiating with. ### The leveling system Every FAANG company maps candidates to an internal level. That level determines your compensation band: a range with a minimum, midpoint, and maximum for each comp component. Here's why this matters: **your negotiation ceiling is defined by your level, not by how well you negotiate.** If you're leveled as an L5 at Google, no amount of pushback will get you L6 comp. The most important negotiation often happens *before* the offer, during the leveling discussion. If you suspect you've been underleveled: - Ask the recruiter directly: *"Can you share what level this offer corresponds to?"* - If it's lower than expected, make your case with specific evidence: years of experience, scope of previous roles, and the complexity of your interview performance - This is time-sensitive. It's much easier to adjust level before the offer is generated than after ### The comp committee At most FAANG companies, recruiters don't set comp. They *recommend* it. The actual approval comes from a compensation committee or a hiring manager's budget. When you negotiate, you're really asking the recruiter to go back to this committee with justification for a higher number. This means your counter-arguments need to be things a recruiter can put in an email to their comp team: market data, competing offers, specific qualifications. "I just want more" doesn't give them anything to work with. ## Google: Where Equity Is the Real Conversation ### The structure Google's comp for engineers and PMs typically breaks down as: - **Base salary:** capped per level (hard ceiling) - **Annual bonus:** target 15% of base for most levels - **RSUs:** granted as a total dollar value vesting over 4 years - **Sign-on bonus:** usually offered to bridge the equity vesting gap ### What actually moves **Base salary** at Google has well-defined bands per level. If your offer is already at the top of the band, the recruiter literally cannot increase it. The system won't allow it. Don't waste your negotiation capital here if they tell you it's at ceiling. **RSUs are where the real money is.** Google equity grants can vary significantly within a level, sometimes by $100K or more over the 4-year vest. This is the lever with the most room, and the comp committee has more flexibility here than on base. **Sign-on bonuses** are particularly negotiable when you have a competing offer. Google often uses sign-on to make the Year 1 total comp competitive, especially because their RSU vesting is back-loaded (33% vests in Year 1 vs. 25% standard at other companies). ### Google-specific tactics - If you have a Meta or competing offer, share the total comp number. Google's comp team specifically benchmarks against competitor offers. - Ask about the RSU refresh policy. Google's refresher grants are meaningful and can significantly change the long-term value of the offer. - Don't fixate on the "target bonus" percentage. It's standard per level and rarely changes. Focus your energy on base and RSUs. *Deep dive: our full [Google salary negotiation playbook](/google-salary-negotiation/) breaks down the equity bands, level-by-level base ceilings, and a copy-paste counter for a Google offer.* ## Meta (Facebook): Fast Offers, Flexible Comp ### The structure Meta's comp is similar to Google's but with a few key differences: - **Base salary:** competitive bands, slightly more flexible than Google - **Annual bonus:** target 10–15% - **RSUs:** 4-year vest with a standard 25%/25%/25%/25% schedule - **Sign-on bonus:** commonly offered, especially for senior roles ### What actually moves Meta is often more willing to move on **total comp** than individual components. Their recruiters have more discretion than Google's, and the approval process tends to be faster. **The Level 2 bump.** If you're coming in at E5 (senior) and have 8+ years of experience with strong interview results, push for E6 consideration. The comp difference between E5 and E6 at Meta can be $150K+ in annual total comp. This is the single highest-leverage conversation you can have. **RSU negotiation** is straightforward at Meta. They have clear bands and the recruiter can often get approval for increases within a day or two. If you're going to push on one thing, push on equity. ### Meta-specific tactics - Meta moves fast. They may pressure you with tight deadlines. It's okay to ask for more time. A simple *"I want to make the right decision for both of us, could I have until [date]?"* almost always works. - If you have a Google offer, explicitly share the total comp. Meta's comp team is highly responsive to Google competition. - Relocation packages at Meta are often generous and somewhat negotiable. If you're relocating, don't leave this on the table. *Deep dive: our full [Meta salary negotiation playbook](/meta-salary-negotiation/) covers the E5→E6 leveling case, RSU bands, and the exact language for a Meta counter.* > **Have a live FAANG offer on your desk?** Knowing the levers is half the job. The other half is the reply you send when the recruiter says "that's already top of band." SalaryScript is the 125-page playbook for that exact moment, with a counter-move for every recruiter tactic. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) (instant download, 14-day results-based guarantee) or [compare all plans](/#pricing). ## Amazon: The Unusual Structure ### The structure Amazon's comp is uniquely structured and trips up many candidates: - **Base salary:** hard-capped at $175K for most roles (occasionally $185K+ for very senior) - **RSUs:** 4-year vest with a heavily back-loaded schedule: 5%/15%/40%/40% - **Sign-on bonus:** large, designed to compensate for the back-loaded vesting - **Annual bonus:** generally not offered for most tech roles ### What actually moves **The base salary cap is real.** Unlike Google or Meta, Amazon genuinely caps base for most roles. Don't burn relationship capital trying to push past it. **Sign-on is the primary lever.** Because of the back-loaded vesting, Amazon offers substantial sign-on bonuses (sometimes $80K–$150K+ split across two years) to make Years 1 and 2 competitive. This is highly negotiable. **Total RSU grant** is the other major lever. The difference between a $200K and $350K RSU grant is enormous, especially in Years 3 and 4 when 80% of it vests. ### Amazon-specific tactics - Frame your Year 1 and Year 2 total comp separately from Years 3+. The back-loaded vesting means these feel like two different offers. - If you have a Google or Meta offer, Amazon will often increase sign-on significantly to match Year 1 total comp. - Ask about team-specific RSU refresher policies. Some orgs within Amazon grant aggressive refreshers; others don't. This meaningfully changes the long-term value. - Don't forget about the stock price: Amazon RSUs are granted as a dollar amount but convert to shares. If the stock rises, your actual comp increases. Factor this into your analysis. *Deep dive: our full [Amazon salary negotiation playbook](/amazon-salary-negotiation/) maps the base cap, the back-loaded vest, and how to push sign-on across Years 1 and 2.* ## Apple: The Quiet Negotiator ### The structure Apple is less transparent about comp than other FAANG companies, which makes preparation even more important: - **Base salary:** competitive, with more flexibility than Google or Amazon - **RSUs:** 4-year vest, typically 25%/25%/25%/25% - **Sign-on bonus:** offered but generally smaller than Amazon's - **Annual bonus:** varies by org, not always guaranteed ### What actually moves Apple recruiters have meaningful discretion on base salary, more so than at Google or Amazon. If you're going to push on base, Apple is the FAANG company where it's most likely to work. **RSU grants** are also flexible, though Apple tends to be more conservative with initial equity grants compared to Google or Meta. The refresh grants are where Apple makes up the difference for strong performers. ### Apple-specific tactics - Apple is notoriously secretive about internal comp data. Use external data sources and competing offers as your primary reference points. - Emphasize your long-term commitment. Apple's culture values loyalty, and framing your negotiation as *"I want to make sure the comp reflects a long-term partnership"* resonates better than short-term optimization. - Hardware and silicon roles command premiums that don't always show up in generic comp data. If you're in one of these areas, push harder. *Deep dive: our full [Apple salary negotiation playbook](/apple-salary-negotiation/) covers ICT leveling, why base is the lever, and the refresher game behind Apple's conservative initial grants.* ## Netflix: A Different Game Entirely ### The structure Netflix operates on a fundamentally different philosophy: - **Base salary:** the primary comp component, significantly higher than other FAANG - **No RSUs:** Netflix pays in cash, not stock (they offer the option to take part of your comp as stock options, but this is your choice) - **No annual bonus:** your salary *is* your comp - **Market-rate adjustments:** Netflix re-evaluates comp annually based on market data ### What actually moves At Netflix, compensation negotiation is primarily a **base salary** conversation. Since there's no equity or bonus to adjust, the base number matters enormously. Netflix's philosophy is to pay "top of market." They use compensation surveys and competing offer data aggressively. If you can demonstrate your market value through competing offers, Netflix will often match or exceed them. ### Netflix-specific tactics - Netflix values senior, independent contributors. If you're at that level, the comp reflects it, but you need to be prepared for the expectations that come with it. - Competing offers are extremely powerful at Netflix because their whole comp philosophy is built around market positioning. A strong offer from Google or Meta can move your Netflix base by $30K–$50K+. - Ask about their annual "market re-rate." Understanding how Netflix adjusts comp over time helps you evaluate the long-term value of the offer. *Deep dive: our full [Netflix salary negotiation playbook](/netflix-salary-negotiation/) explains the all-cash model, the stock-option toggle, and how to anchor a base-only counter.* ## Universal Tactics That Work Across All FAANG Companies ### Timing matters FAANG companies have fiscal year boundaries that affect budgets and headcount. If you're negotiating near the end of a fiscal year or quarter, there may be pressure to close you before budget resets. This can work in your favor, or against it. ### The "exploding offer" pressure Recruiters may give you tight deadlines. While you should be respectful of timelines, a good rule: **a company that would rescind an offer because you asked for one more week wasn't a company that valued you.** Ask for reasonable extensions when you need them. ### The competing offer dance Having competing offers is the single most effective negotiation tool. But the way you present them matters: > ✅ "I'm genuinely interested in [Company]. I do want to be transparent that I'm also evaluating an offer from [Competitor] at a total comp of [X]. I'd love to find a way to make [Company] work. Is there flexibility to get closer to that range?" This is collaborative, honest, and gives the recruiter a specific number to work with. Not sure what that number should be? Our guide on [how much to counter a software engineer offer](/blog/how-much-to-counter-software-engineer-offer/) breaks down the right amount by level and by lever. ### Don't negotiate via email if you can help it Phone and video calls convey tone (enthusiasm, flexibility, professionalism) in ways email can't. Use email for confirmations and follow-ups, but have the actual negotiation conversation live when possible. When you do put your counter in writing, work from a proven [salary negotiation email template](/blog/salary-negotiation-email-templates/) rather than drafting from scratch. The exact wording of a written counter is what recruiters forward to the comp committee. > **Negotiating a FAANG offer right now?** The guides above show you where to push. SalaryScript is the 125-page playbook for the back-and-forth that follows: a counter-move for every recruiter tactic, calm responses under pressure, and real case studies behind $30K to $300K wins. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) ## The Compounding Effect of Getting It Right At the FAANG level, a single negotiation can move your comp by $50K–$200K annually. Over a 4-year stay, that's $200K–$800K. Factor in the impact on future offers (which are benchmarked against your current comp), and the lifetime impact easily reaches seven figures. The companies know this. They have entire teams dedicated to compensation strategy. The question is whether you're going to negotiate with the same level of preparation. If you've just received an offer and want the move-by-move sequence, start with [how to negotiate salary after a job offer](/blog/how-to-negotiate-salary-after-job-offer/). Negotiating just outside FAANG? The same playbook applies, with a few twists. For other public big-tech offers, see our guides on [Microsoft salary negotiation](/microsoft-salary-negotiation/) (push the on-hire stock award, not base), [Nvidia salary negotiation](/nvidia-salary-negotiation/) (equity-first, and don't overlook the ESPP), [Uber salary negotiation](/uber-salary-negotiation/) (win the L4→L5 jump first), [Salesforce](/salesforce-salary-negotiation/) (ask for the sign-on they left out), [LinkedIn](/linkedin-salary-negotiation/) (Microsoft stock on LinkedIn's own ladder), [Airbnb](/airbnb-salary-negotiation/) (one US pay tier, equity is the lever), [Snowflake](/snowflake-salary-negotiation/) (no sign-ons, so the grant carries everything), and [Coinbase](/coinbase-salary-negotiation/) (which famously does not negotiate at all: win the level instead). For top private companies, where equity is illiquid and realized through tender offers or buybacks, see [Stripe salary negotiation](/stripe-salary-negotiation/), [OpenAI salary negotiation](/openai-salary-negotiation/) (which moved from PPUs to conventional equity after its 2025 restructuring), [Anthropic](/anthropic-salary-negotiation/) (systematic offers, level decides the number), [Databricks](/databricks-salary-negotiation/), and [TikTok](/tiktok-salary-negotiation/). --- *A FAANG negotiation is one conversation, and going into it unprepared routinely costs $50K–$200K a year that you never get back. SalaryScript was built specifically for this scenario: the exact scripts, counter-strategies, and scenario-by-scenario playbooks our team developed from 30+ years inside these companies. [Get the Bundle · $129 →](https://salaryscript-inc.lemonsqueezy.com/checkout/buy/22f9faf1-9dda-48c0-88b5-5006e0a77c1b) or [compare all plans from $39](/#pricing).*