Salary Negotiation & Career Growth

You have passed the interviews. Now comes the part most engineers neglect: negotiation. The difference between accepting the first offer and negotiating effectively can be $50K-$150K+ over the life of an offer. This lesson covers compensation benchmarks, negotiation scripts, equity understanding, and career path planning for frontend engineers.

Reading an Offer

Get your benchmark numbers from levels.fyi on the day you need them, filtered by company, level, and location. We do not reprint them here, because equity is the largest component at senior levels and is repriced continuously — any table we published would be wrong before you read it, and quoting a stale figure to a recruiter costs you credibility at exactly the wrong moment.

What matters more than the benchmark is being able to compare two offers that are shaped differently. Most candidates compare the headline "total compensation" number, which is an average across four years, and then discover in month three that their actual income dropped.

With the defaults, the 4-year average is around $418K — but year one is $350K and steady state is $470K. Three things follow from that, and each one is a negotiation move:

• The sign-on is load-bearing, and it expires. Two years in, that $90K and $60K stop arriving. If you negotiated the sign-on up and the equity grant not at all, you improved the two years you are least likely to still be there for and left the rest untouched.
• A refresh grant is what closes the cliff. Ask what the typical refresh looks like at your level and when the first one lands. Most companies will not commit to a number, but they will tell you the cycle — and knowing that year three is when refreshes stack is the point.
• Compare like for like. If one offer front-loads and the other back-loads, the headline numbers are not comparable. Run both through the model above and compare steady state, then decide how much you discount the years you might not stay for.

Context worth stating plainly:

• Mid-size companies (Stripe, Airbnb, Coinbase) typically pay below FAANG bands, though the gap narrows at senior levels and reverses at individual companies in a strong year
• Startups vary widely — lower base, and equity whose value is a guess rather than a number
• Public-company equity moves with the share price, so a "total comp" figure is a snapshot of the grant date, not a salary
• Location matters less than it used to, but some companies still apply geographic pay bands
• Frontend engineers are compensated identically to backend engineers at the same level — there is no "frontend discount"

Negotiation Strategy

Rule #1: Never Give a Number First

When a recruiter asks "What are your salary expectations?", deflect:

"I'd prefer to understand the full compensation package before discussing numbers. I'm focused on finding the right role, and I'm confident we can find a number that works for both sides."

If they insist on a range:

"Based on my research for this level and location, I'd expect total compensation in the range of $X to $Y. But I'd love to see the full offer before committing to a number."

Rule #2: Express Enthusiasm, Then Negotiate

When you receive an offer, always respond positively first:

"Thank you so much — I'm really excited about this role and the team. I'd like to take a day or two to review the full package. Could you send the details in writing?"

Never negotiate on the spot. Get the offer in writing. Then prepare your counter.

Rule #3: Data-Backed Counter

When you counter, lead with excitement and data:

"I'm very excited about this opportunity, and [Company] is my top choice. After reviewing the offer and researching market data on levels.fyi and similar resources, I believe a total compensation of $X would better reflect the impact I expect to make at this level. Is there flexibility in the base salary and equity components?"

Rule #4: Negotiate Multiple Components

Total compensation has several levers. If they cannot move on base salary, ask about:

• Sign-on bonus — A one-time payment that does not affect ongoing budget. Companies are often flexible here.
• Equity / RSU grant — Ask for additional RSUs. At public companies, this can be the largest component of TC.
• Annual bonus target — Some companies have flexibility in the bonus percentage.
• Start date — If you have another offer's deadline, a later start date gives you more time to negotiate.
• Level — If you are borderline between L4 and L5, argue for the higher level. The comp band difference is significant.
• Review timing — Ask for a 6-month compensation review instead of the standard 12-month cycle.

Rule #5: Use Competing Offers Ethically

If you have multiple offers, you can mention this honestly:

"I have a competing offer at $X total comp. I'd prefer to join [Your Company] because of the team and the technical challenges. Is there room to close the gap?"

Never fabricate offers. Recruiters talk to each other, and the industry is smaller than you think.

Understanding Equity

RSUs (Restricted Stock Units) — Public Companies

RSUs at public companies (Google, Meta, Amazon) are straightforward:

• You receive a grant of N shares
• They vest over a schedule (typically 4 years)
• Standard vesting: 25% after year 1 (cliff), then monthly or quarterly
• Amazon is different: 5% / 15% / 40% / 40% over 4 years (heavily back-loaded)
• When shares vest, they are taxed as ordinary income at the current stock price

Stock Options — Startups

Stock options at startups are more complex:

• Strike price — The price you pay to buy the shares (set by a 409A valuation)
• Current valuation — What the company says the shares are worth today
• Exercise window — How long you have to buy shares after leaving (90 days is standard, some companies offer longer)
• Dilution — Your percentage ownership will decrease as the company raises more funding rounds
• Liquidity risk — You cannot sell startup shares easily. The company needs to IPO or be acquired for your equity to become real money.

Key question to ask: "What is the current 409A valuation, and what was the last preferred share price?" The gap between these tells you how much upside investors think exists.

How to Evaluate Startup Equity

A simple framework:

1. Calculate your share count as a percentage of total outstanding shares
2. Apply a discount for risk (80-90% for early-stage, 50-70% for late-stage/pre-IPO)
3. Estimate possible exit values (acquisition or IPO)
4. Your expected value = (your % ownership) x (exit value) x (1 - risk discount)

For most people, the guaranteed cash at a public company is worth more than startup equity on paper. Treat startup equity as a lottery ticket with better-than-lottery odds, not as a guaranteed payout.

IC vs. Management Track

Frontend engineers have two career paths. Both are equally valued and compensated at top companies:

Individual Contributor (IC) Track

Junior Engineer (L3)
    ↓
Mid-Level Engineer (L4)
    ↓
Senior Engineer (L5)        ← Most engineers settle here
    ↓
Staff Engineer (L6)         ← Requires cross-team impact
    ↓
Principal Engineer (L7)     ← Requires org-wide impact
    ↓
Distinguished Engineer (L8+) ← Extremely rare, company-wide impact

What changes at Staff+ level:

• You define what to build, not just how to build it
• You write technical design docs that other teams follow
• You mentor senior engineers
• You identify and drive multi-quarter technical initiatives
• Your code output may decrease, but your impact through others increases

Management Track

Tech Lead (L5-L6)           ← Still writing code, leading a small team
    ↓
Engineering Manager (L6)    ← Less code, more people management
    ↓
Senior Engineering Manager
    ↓
Director of Engineering     ← Multiple teams, organizational strategy
    ↓
VP of Engineering           ← Department-level leadership

When to consider management:

• You genuinely enjoy growing other people's careers
• You are energized by organizational problems (hiring, process, cross-team alignment)
• You are comfortable with less direct coding time

When to stay IC:

• You love deep technical work
• You want to be the expert others come to for hard problems
• You find management meetings draining rather than energizing

There is no shame in either choice. The best organizations let people switch between tracks.

Building a Frontend Portfolio That Stands Out

Beyond interview prep, your long-term career benefits from visibility:

Open Source Contributions

• Fix bugs in libraries you actually use (React, Next.js, Vite, testing libraries)
• Even small documentation fixes show engagement with the ecosystem
• Maintainers remember helpful contributors when they are hiring

Technical Blog

• Write about problems you have solved — "How We Reduced LCP by 60% at [Company]"
• Deep dives on niche topics get more attention than generic tutorials
• Consistency matters more than volume — one quality post per month is enough

Side Projects

• Build something that solves a real problem, not just a tutorial clone
• Use the side project to learn new technologies you cannot use at work
• Deploy it publicly and keep it running — a live URL is worth more than a GitHub repo

Conference Talks

• Start with local meetups and lightning talks (5-10 minutes)
• Record yourself and share on YouTube/social media
• Talks establish you as a subject matter expert in a specific area

---

Ready to complete your full-stack interview prep? Continue with Backend Engineer Interviews — API design, database optimization, distributed systems, and the behavioural and compensation rounds from the backend side.

:::