Front-Loaded Vesting Is Now Standard at Big Tech: How to Evaluate and Negotiate an Offer That Looks Bigger Than It Is

A $400,000 offer that pays out like a $280,000 offer is not a $400,000 offer. That distinction sounds obvious until you are sitting with three competing packages, a spreadsheet that adds up total compensation, and no framework for what the vesting curve actually does to the numbers you are comparing.

In September 2025, Levels.fyi published an analysis describing front-loaded vesting as one of the biggest structural changes to tech compensation in years. The piece did not say compensation is higher. It said the shape of compensation has changed — and that shape determines what you actually take home depending on when you leave, when the market moves, and which company you choose. Most candidates are still evaluating offers as if vesting were a linear function. It is not, and has not been at most large tech companies for some time.

This matters most to engineers who are actively comparing offers across multiple companies — which describes the majority of software engineers in a loop at more than one big tech firm at any given point. If you are weighing Google against Meta against a late-stage startup, you are almost certainly looking at three different vesting architectures. Adding up four-year grant totals and dividing by four does not model any of them accurately.

How front-loaded vesting actually works

The standard mental model for RSU vesting is 25% per year over four years. That model is increasingly inaccurate. Front-loaded schedules, most commonly in a 5/15/40/40 or similar structure, distribute a smaller share in years one and two and a significantly larger share in years three and four. The result is a grant that reads as $300,000 over four years but delivers roughly $60,000 in year one and $120,000 in year three — before accounting for stock price movement in either direction.

The four-year total is not the number that determines your financial outcome. The vesting curve is. Two offers with identical four-year totals can produce outcomes that differ by more than $100,000 depending on when you leave and what the stock does in each year.

Meta has used a front-loaded vesting schedule — frequently cited as 25/25/25/25 with an additional refresh mechanism — while Google's RSU refreshes and cliff structures operate differently at different levels. Amazon, notably, has historically used a back-loaded schedule (5/15/40/40), which front-loads the risk onto the employee in years one and two. Candidates who have gone through Amazon's offer process consistently report that the year-one and year-two cash compensation is structured partly to compensate for the lower RSU delivery in those years — meaning the "total comp" figure requires decomposing into cash and equity components separately to understand the real trajectory. These patterns are reported by candidates on Levels.fyi and corroborated by offer data shared publicly on the platform.

The implication of front-loading — whether the front-load is in equity or in cash — is that the attractiveness of an offer changes based on your expected tenure. An engineer who expects to stay four or more years benefits more from a back-loaded equity schedule if they believe the stock will appreciate. An engineer who expects to move within two years benefits from front-loaded equity delivery or higher year-one base. Neither preference is irrational. But you cannot apply the same evaluation to both without distorting the comparison.

What to actually compare when evaluating competing packages

When you have multiple offers in hand, the comparison that matters is not total four-year compensation. It is year-by-year expected cash flow, adjusted for your realistic tenure assumption and your view on each company's stock trajectory. That sounds like more work than most candidates do — because it is. But failing to do it means you are making a significant financial decision on a number that does not represent your actual expected outcome.

Start by decomposing every offer into its components: base salary, signing bonus (and whether it is subject to clawback if you leave before year two), RSU grant with the full vesting schedule, and annual refresh grants — which are often omitted from initial offer letters entirely. Levels.fyi's compensation database includes reported refresh data for many companies and roles, which gives you a baseline for what to expect and what to negotiate. Reported refresh rates at large companies vary significantly by level and performance rating, but they are not zero, and ignoring them understates the long-term value of staying.

For the negotiation itself: the vesting schedule is rarely negotiable at large tech companies. The grant size is. Signing bonuses are frequently used to compensate for year-one equity delivery gaps — meaning if you are coming from a company with a large unvested grant, the signing bonus at your new employer is partly a transfer-of-risk payment, not a reward. Treat it as such in your negotiation. Ask what the signing bonus is intended to compensate for, and make sure the answer maps to your actual unvested equity, not a round number someone generated from a salary band.

Level placement is the other variable that candidates underweight. At most large tech companies, a one-level difference in placement produces a compensation difference that compounds over multiple grant cycles. Candidates who have successfully negotiated level changes — rather than grant size changes — at companies like Google and Meta consistently report that the level conversation is worth having before the offer is finalized, not after. The software engineer interview process at most big tech companies includes a calibration step after the loop closes but before the offer is written, and that calibration is more malleable than the written offer that follows it.

One thing worth stating directly: most candidates receive an offer, feel time pressure, and evaluate it against the number at the top of the letter. The number at the top is not the offer. The offer is the year-one cash, plus the year-one equity delivery, plus the signing bonus, minus the unvested equity you are leaving behind, minus the clawback risk on the signing bonus if you leave early. That full calculation is what you are actually accepting. Doing the math before you accept is not pessimistic — it is the minimum diligence the decision warrants.

Compensation structure is one part of the equation. The other is making sure you get to the offer in the first place — which starts with how your background is read before you are ever in a room. If you want to understand how your resume positions you against the bar for software engineering roles, the next step is a structured review that looks at your experience the way a recruiter and hiring manager actually do.