How to Negotiate a Software Engineer Offer: A Founder's Playbook
Most founders are bad at offer negotiation — not because they lowball, but because they don't understand what candidates actually care about or how to structure a conversation that increases the probability of a yes. This guide covers the full playbook: from the first offer through counter-offers to close.
Quick Answer
The most common offer negotiation mistake is treating it as adversarial. Strong candidates want to join great companies — your goal is to understand what they need to say yes, then find the version of your offer that meets both of your constraints. Negotiation resolved this way almost always results in a stronger relationship.
What Candidates Actually Negotiate On
Based on RFS data across hundreds of engineering offers:
| Factor | % Who Raise It | % Who Make It a Dealbreaker |
|---|
| Base salary | 82% | 31% |
| Equity amount/terms | 68% | 44% |
| Start date | 45% | 8% |
| Title/level | 38% | 22% |
| Sign-on bonus | 35% | 4% |
| Vesting cliff | 28% | 18% |
| Remote/work location | 24% | 29% |
The insight: Equity terms are raised less often than base salary but are far more often dealbreakers. This means many candidates who don't raise equity are silently dissatisfied. Proactively addressing equity in your verbal offer — explaining the math, the vesting schedule, and the upside scenario — significantly improves close rates.
Reference: staffeng.com has detailed data on what staff engineers negotiate for; the pattern holds for senior ICs.
The Framework: Understand Before Countering
When a candidate counters, ask before defending: "Help me understand what's most important to you here — is it the cash comp specifically, the overall package, or something else?"
This question does three things:
- Gives you data to optimize the offer
- Signals that you're listening, not just defending your position
- Often reveals that the stated ask isn't the real ask (e.g., they say "higher base" but actually care more about title)
Comp Structure for Startup Offers (2026)
Source: levels.fyi, RFS placement data
| Component | Series A | Series B | Series C |
|---|
| Base salary (senior SWE) | $175K–$225K | $195K–$245K | $210K–$265K |
| Equity (senior SWE) | 0.08%–0.2% | 0.04%–0.1% | 0.02%–0.06% |
| Sign-on (if needed) | $15K–$40K | $20K–$50K | $25K–$60K |
| Vesting | 4yr/1yr cliff | 4yr/1yr cliff | 4yr/1yr, sometimes 6mo cliff |
Counter-Offer Strategies
When they ask for more base:
First, understand if it's a budget constraint ("I need $X to pay rent") or a relative issue ("I'm expecting market rate"). For budget constraints: offer a sign-on bonus that bridges the gap this year. For market rate concerns: share your comp bands and how you arrived at the offer — transparency signals respect. If you can move the base, move it once and move it meaningfully; multiple small increments erode trust.
When they ask for more equity:
This is where to spend your negotiation capital. Equity is cheaper for the company than cash and is the thing candidates remember most. Before increasing the grant, explain the current equity value, the vesting schedule, the last 409A strike price, and the realistic exit scenario. Many candidates who "want more equity" haven't done this math and change their ask once they understand what they already have.
When they have a competing offer:
Ask what's better about it. If it's comp: share your equity math and make the total comp comparison clear. If it's mission or team: have a direct conversation about the comparison. Never pressure or give exploding deadlines — it damages the relationship and rarely works. Strong candidates making a thoughtful decision will take the time they need.
Close Rate Signals
Three behaviors predict a candidate who will accept:
- They ask about start date logistics (practical, not evaluative questions)
- They intro you to their reference contacts proactively
- They tell you what they need to say yes
If none of these are happening 3 days after an offer, call them — not to pressure, but to understand.
Why Recruiting from Scratch
We guide founders through the full offer and negotiation process — with market comp data at every step. Talk to us about your next engineering hire →
Related: Software Engineer Salaries in Los Angeles: What Startups Pay in 2026 ·
Data Engineer Salary Guide: SF, NYC, and Remote (2026)
Frequently Asked Questions
Q: Should we give candidates a deadline on the offer?
A: Short deadlines (48–72 hours) are appropriate for candidates who've been in your process for 4+ weeks and have all the information they need. They signal you have a real hiring process, not an open-ended one. Exploding offers (24 hours, or "this offer expires if you don't sign today") are counterproductive — they create resentment, filter out candidates who value deliberate decision-making, and have a 40–60% higher renege rate even when accepted.
Q: What's the right way to handle a candidate who has a FAANG competing offer?
A: Don't try to match it on cash — you won't win. Present your equity value clearly and honestly (what 0.1% at a $20M Series A could be worth at 5x, 10x growth), discuss the ownership and scope difference, and let the candidate make the tradeoff. The candidates who choose startups over FAANG with full information are much better startup fits than those who joined only because the cash was the same.
Q: We rescinded an offer after the candidate countered — how do we handle this?
A: Rescinding an offer because a candidate negotiated is a serious reputational risk. The engineering community is small — word travels. Unless the counter was egregiously outside any reasonable range AND you had a clear mutual understanding this was a final offer, don't rescind. The reputational damage from one rescind can hurt your ability to hire for 12+ months.
Q: Is it appropriate to ask a candidate what they're currently making?
A: In many US states (California, New York, Massachusetts, and others), it's illegal to ask for current salary history. Even where legal, don't ask — it anchors the conversation to their previous comp rather than the market rate for your role, and sophisticated candidates view it as a red flag. Use market data (levels.fyi, our placement data) to set comp ranges, not candidate history.
