12.15 — Salary Negotiation & Offer Evaluation

Opening scenario

The recruiter calls: “We’d like to extend an offer — $250k base, 200k RSUs over 4 years, 15% bonus target. We’ll need an answer by Friday.” Your heart says yes. Your bank account says yes. The data says you’re leaving $40–80k/year on the table. This chapter is the framework for negotiating with confidence and grace.

Context — what total comp actually means

Total compensation (TC) = sum of all above per year, usually quoted as year-1 + year-2-on-blended.

Always compare offers in TC, not base.

The data sources

Before you negotiate, you need market data:

1. Levels.fyi — the gold standard. Filter by company, level, location, year.
2. Glassdoor — second-tier but useful for non-FAANG.
3. Blind — anonymous teamblind app; iOS folks share specifics.
4. LinkedIn Salary — third-tier.
5. Personal network — quietly ask 2–3 senior peers in similar roles.

For each company you’re talking to:

• Pull the L+1, L, and L-1 levels at your target band.
• Look at p50 / p75 / p90.
• Note total comp, not just base.

Walk in knowing the band. The recruiter does; you should too.

RSU vesting schedules — the hidden variable

A “$200k over 4 years” offer can mean wildly different things:

When evaluating, always compute the year-1 number explicitly. Two “200k over 4 years” offers can have $60k year-1 difference.

For private companies (startups), RSUs may be:

• Strike-price stock options — you pay to convert. Often illiquid until IPO.
• RSUs that vest but don’t convert until liquidity event — common at growth-stage.
• Phantom equity / profit share — less standard, read the docs.

Always ask: “What’s the strike price?” “What’s the current 409A valuation?” “When did the last secondary or fundraise happen, at what price?”

The negotiation script

Phase 1 — never anchor first

Recruiter: “What are you looking for in compensation?”

❌ “I’d like $X base.” ✅ “I’d rather understand the full picture of your offer first — base, equity, bonus structure. Then I can speak to whether it’s competitive for me.”

If they push: “What range did you have in mind for this level?”

If they truly insist: give a range from your market data, with the top of the range being your target.

✅ “Based on my research and other conversations, for a senior iOS role at your stage, I’d expect total comp in the $400–500k range. Where does your band sit for this level?”

Phase 2 — receive the offer in writing

Always: “Could you send the full offer in writing? I want to review it carefully before we discuss further.”

Never accept verbally on the call. Buy time — 48 hours minimum, ideally a week.

Phase 3 — counter

Counter in writing too. Structure:

Hi [Recruiter],

Thank you for the offer and for walking me through the details. I'm genuinely excited about [team / mission / specific thing].

After comparing this against the market data and a couple other conversations I'm in, I'd like to discuss the following adjustments:

1. Base: $260k → $290k
2. Equity: $200k over 4yr → $260k over 4yr (or front-loaded 35/30/20/15)
3. Sign-on: $30k → $50k to bridge unvested equity at my current role

I'd love to make this work. Let me know what's possible.

[You]

Notes:

• Always justify (market data, unvested equity, competing offers).
• Counter on multiple dimensions — if they can’t move on base, they may move on equity or sign-on.
• One round of counter is normal; two is acceptable; three signals trouble. Don’t drag.

Phase 4 — competing offers as leverage

If you have a competing offer, mention it factually:

✅ “I have another offer at $X TC. I’d prefer your team for [reason], but the gap is real. Can we close it?”

Never lie about competing offers. Recruiters in the same city talk and often verify casually. Caught fabricating, you lose the offer.

If you don’t have a competing offer, don’t fake one. Lean on market data and your conviction.

Phase 5 — when to accept

You should feel comfortable that:

• TC is at or above the company’s published band for the level.
• The equity vest schedule is reasonable.
• The role/team are what you want for 2+ years.
• You’d accept this offer even if a slightly better one came later — i.e., no regrets.

Sleep on it one night. Then accept in writing, with grace and enthusiasm.

Evaluating offers beyond comp

For each offer, score on:

A higher-paying role under a bad manager loses every time over 5 years. Optimize for the role, not just the paycheck.

iOS-specific perks worth asking about

These are real cash equivalent — ask explicitly:

• WWDC access: $1,599 ticket + travel. Many iOS-heavy companies cover annually.
• Hardware budget: latest iPhone + iPad + Mac for testing? $3–5k/yr value.
• Apple Developer Program: $99/yr — small but signals iOS investment.
• Conference budget: try! Swift, iOSDevUK, AltConf, dotSwift. $2–5k/yr.
• TestFlight + internal tooling access: not a perk but indicates engineering maturity.
• External iOS contractor agency contracts: some big-cos cover Toptal/freelance budget for design or specialized work.
• App Store assets: design, localization budget.

Red flags during negotiation

• Refusal to put offer in writing: hard pass.
• Pressure to decide same-day: “this offer expires tonight” — fake. Always ask for 48 hours, push back if refused.
• Reluctance to share band or salary range: signals a low-comp culture. Walk if persistent.
• Counter-offer dropped below original verbal: huge red flag for trust.
• Recruiter promising verbally what isn’t in writing: only writing matters. Verbal promises are nothing.
• “We don’t do that here” for sign-on, equity refresh, etc. — without explanation: get clarity. Sometimes legit; sometimes a brushoff.

Counter-offers from your current employer

If you’ve resigned and your current company offers a counter:

• Typical advice: don’t take it. The reasons you wanted to leave usually don’t go away with money.
• Exception: if the counter addresses a specific concern (boss, team, role, not just money) and you trust it’ll stick.
• Reality: ~70 % of accepted counter-offers result in the engineer leaving within 12 months anyway (industry survey data, take with salt).

Equity refresh and yearly review

After year-1, ask about equity refresh:

• Most big-cos give an annual refresh (10–30 % of original grant) on top of vesting schedule. Without it, your TC steps down sharply after year-4.
• Negotiate refresh visibility in the offer: “What’s the typical annual refresh band?”
• At review time (annual or biannual), come prepared with the same market data exercise.

Common misconceptions

1. “Negotiating offends the company.” It doesn’t — they expect it. Not negotiating signals you may underperform on advocacy too.
2. “Top of band is greedy.” Top of band is the band. They published it; they expect to fill it.
3. “Don’t negotiate at a small company / startup.” Negotiate everywhere. Smaller companies often have more flexibility on equity than base.
4. “Sign-on is just a perk.” Sign-on rebalances vest schedules. Negotiate it explicitly to bridge unvested equity at current role.
5. “Always take the highest TC.” Highest TC under a toxic manager beats your nervous system every time. Optimize whole career value, not just first paycheck.

Seasoned engineer’s take

Negotiation is not adversarial. The recruiter wants to close the offer — your interests are 90 % aligned. You both want a “yes” that you’ll be happy with for 2+ years. Approaching it as collaboration (“help me make this work”) consistently outperforms adversarial framing (“give me more”). The data shows: average successful counter at senior iOS levels lifts TC by 10–25 %, with no offers rescinded for politely negotiating.

TIP: Always negotiate base over equity at growth-stage startups — base is portable and certain; equity may be worth zero. Reverse at IPO-near or public companies — equity may be the multiplier.

WARNING: Don’t ghost recruiters once you’ve started a negotiation. Even if you decline, do it professionally. The iOS community is small and reputational; you’ll see these people again at conferences and at future companies.

Interview corner

Junior: “Should I negotiate my first offer?” Yes, every time. Even a 5–10 % bump compounds over a career. Lead with gratitude, then mention you’d like to discuss the package given market data.

Mid: “What’s the biggest negotiation mistake mid-level engineers make?” Anchoring first — giving a number when asked “what are you looking for” before knowing the company’s band. Always invite their offer first; use market data to evaluate; counter on multiple dimensions.

Senior: “How do you decide between two offers with similar TC?” I score them on: team and manager quality (highest weight), growth trajectory, tech alignment, remote flexibility, equity vesting profile, and brand for the next role after this one. A high-TC role under a bad manager loses to a lower-TC role with a great team over a 3-year horizon — both for happiness and for the doors it opens. I also factor risk: a $400k offer at a stable public co with 25/25/25/25 vesting is different from a $400k startup offer where the equity might be worth $0 or $4M, with a 4-year cliff. I’d usually take the higher-expected-value-with-lower-variance option unless I had specific information that tilts the variance.

Red-flag answer: “I always just take the highest number.” Reveals lack of long-term thinking about career, growth, and risk-adjusted value.

Lab preview

No formal lab. This week: pull your current market data on Levels.fyi for your target level + location, write down your “walk away” TC and your “delighted” TC. Update annually whether or not you’re job-searching — it shapes how you evaluate any opportunity that surfaces.

Phase 12 complete. You now have the technical, communication, and career-craft toolkit for the senior iOS interview loop. Next stop: Phase 13 (capstone projects) brings it all together in shippable form.

Labs in this phase:

• Lab 12.1 — Refactor to MVVM
• Lab 12.2 — Modularize a Monolith
• Lab 12.3 — Mock Technical Interview
• Lab 12.4 — System Design Whiteboard