How to Negotiate Salary With a Competing Offer: Most Engineers Waste the Leverage

- Stagger applications by 2-3 weeks so faster-moving companies generate offers before your top choice decides
- Your BATNA gives the negotiation real force: by offer time, the company has sunk thousands of dollars and dozens of hours on you
- Never lead with an ultimatum: frame the competing offer as information that helps you say yes, not a bid to beat
- Base salary compounds; signing bonuses don't: a $10K base increase is worth ~$130K over a decade, a $10K signing bonus is worth $10K once
- Startup equity gets a 75% mental haircut from FAANG recruiters evaluating competing packages, so apply the same discount yourself
- Deadline extensions are almost always grantable: one week is standard, and companies prefer extending over losing a candidate they've already invested in
- Never accept an offer you plan to decline: recruiters move between companies and reneging has real, lasting career costs
You're sitting on an offer from Company A. It expires Friday. Company B, the one you actually want, is still radio silent after your final round two weeks ago. This is the scenario most salary negotiation advice skips entirely, because the people writing it got an offer, signed it, and never had to navigate the collision in real time. It requires moving three things at once: stall one company, accelerate another, and negotiate with both simultaneously.
Get it right and you can add $30,000 to $80,000 in total compensation before you've written a single line of production code. Get it wrong and you accept a suboptimal offer under deadline pressure, or you reveal too much to the wrong recruiter at the wrong moment and torch your position entirely.
The Setup Most Candidates Skip
The whole game starts before you have a single offer. Whether you end up with overlapping offers is almost entirely determined by how you sequence your applications.
Tech companies have dramatically different timelines. A startup might go from phone screen to offer in three weeks. Google can take eight. Amazon falls somewhere in between. If you apply everywhere on the same day, you'll get a startup exploding offer before Google has finished scheduling your first coding round. This is the most common way sharp engineers accidentally trap themselves into a bad hand.
The fix is boring and it works: stagger deliberately. Apply to your safety and backup companies first. Wait two to three weeks before applying to your top choices. By the time your preferred company extends an offer, you'll already have competing ones from the faster-moving companies in your pipeline.
Throughout the process, tell every recruiter you're "actively in process with several companies" and expect to make a decision "within the next three to four weeks." You're not lying. You're not giving away information. You're setting a timeline that forces everyone to move.
You Have More Power Than You Feel
Here's the part nobody tells you before your first negotiation: by the time a company extends you an offer, you're no longer the nervous candidate auditioning for a job. You're the asset they've already decided they want. The power dynamic has flipped. You just haven't been told.
Your company has already spent thousands of dollars and dozens of hours on hiring you. Engineering time, recruiter time, manager time, committee reviews. By the time they extend an offer, the sunk cost is real. As Patrick McKenzie put it in his 2012 salary negotiation essay, a small bump in your base salary is "mouse droppings" compared to that investment. They want to close.
You, meanwhile, feel like the supplicant. You're nervous. You rehearsed your counter-offer in the shower, it sounded great, and now you're about to say "that sounds reasonable" because a human voice makes your brain go blank.
Offers are almost never rescinded because you negotiated. They're occasionally rescinded when a candidate revealed they weren't actually interested, or made demands so disconnected from reality that the recruiter concluded they'd never close. But a clear, specific, professionally framed counter almost always just gets you a counter back.
Don't Lead With the Ultimatum
Most people think using a competing offer means announcing it upfront: "I have a better offer from Company B. You need to beat it."
That's an ultimatum. Ultimatums create adversarial dynamics where none needed to exist. Recruiters who feel cornered have less flexibility and less motivation to work with you. Nobody loves having a gun pointed at them, even a metaphorical one denominated in base salary.
The correct framing is the opposite. You're not here to win a bidding war. You're here because this company is your preference, and you want to give them a chance to make it work. That one reframe changes everything. The recruiter goes from "how do I make this person go away" to "how do I help this person say yes."
What to Actually Say
Start with genuine, specific enthusiasm. Not "I'm really excited about this opportunity," which is the verbal equivalent of a stock photo. Name something real: the team's technical approach, a product you admire, a specific problem the role addresses. Then one sentence of bridge: "There are a few things I wanted to work through on the offer before I can give you a clean yes."
Then be specific. Not "I was hoping for more." Not "I have a competing offer that's higher." Instead: "I'm targeting $185,000 base. I also have another offer from a company I'm less excited about than you, and I'd like to resolve that this week. Is there room to get there on base?"
Notice what happened. You named a number. You disclosed a competing offer. But you positioned it as information, not a threat, and embedded a preference signal in the same breath. The message isn't "beat them." It's "help me say yes to you."
If the recruiter asks for specifics on the competing offer, you're not obligated to name the company or disclose the exact number. "I'd prefer not to get into specifics, but I'm happy to tell you where I need to land" is completely reasonable, and most recruiters won't push further.
One firm rule: never fabricate a competing offer. Experienced recruiters maintain detailed market data and talk to each other more than you'd expect. If you claim an offer from Stripe and the number doesn't match Stripe's known bands for that level, you've destroyed your credibility and your candidacy in a single sentence.
How to Use a Competing Offer When You're Still Waiting
The more common problem isn't overlapping offers. It's one offer with a deadline and radio silence from your first choice.
Contact your preferred company the day you receive the first offer. The message is simple: "I've received an offer from another company I need to respond to by [date]. I'm very interested in continuing my conversation with you. Is there any possibility of accelerating the process?"
This is completely standard. Recruiters deal with it constantly. A company that wants you will move. A company that can't move at all is telling you something useful about how it operates generally.
Then separately request an extension from the company whose offer you're sitting on. "This is an important decision for me. Would you be able to extend the deadline to [specific date]?" One week is almost always grantable. Two weeks, sometimes. Most companies would rather extend than lose a candidate they've already invested in.
Exploding offers with 24 or 48-hour windows are real, mostly at startups, and they're a deliberate pressure tactic. You can still request an extension. If they refuse entirely, that's data about what working there will be like.
What's Actually on the Table
Most candidates negotiate salary and leave everything else untouched. That's real money sitting on a table they never bothered to check.
Base salary is the most important item and the most compounding. A $10,000 increase in base is worth roughly $130,000 over a decade when you account for raises, bonuses, and future offer anchoring. A $10,000 signing bonus is worth $10,000, once, before taxes.
Equity has wild variance. At public companies, the share count and vesting schedule are both negotiable. At startups, understand the preference stack and dilution history before treating that number as real money. It may not be.
Signing bonus is often the most flexible line item because it comes from a one-time budget rather than recurring payroll. Don't lead with it as your primary ask, but use it as a fallback: "If you can't get to my base target, would you be able to bridge the gap with an additional signing bonus?"
Levels.fyi negotiation reviews show increases ranging from 15% to 42% in total compensation for candidates who came in with specific competing-offer context. The median lands somewhere in the 15% to 25% range.
Recruiters Discount Startup Equity. So Should You.
When you're stuck on base and the recruiter says they've hit their ceiling, the natural move is to shift to equity: offer to trade some of the salary ask for more RSUs.
The catch is valuation. A public company RSU is worth roughly face value minus income tax. A Series B startup RSU is worth somewhere between zero and something, with the exact answer depending on things you will not be allowed to see. Levels.fyi data suggests FAANG companies implicitly discount startup equity by up to 75% when evaluating competing packages. If you're using a startup offer to push Google, Google's recruiter has already applied that haircut before they even finished reading your message.
This isn't unfair. It's accurate. Apply the same discount yourself when evaluating what you're actually being offered.
The One Move That Actually Hurts You
There's one practice that will damage your career in ways that are hard to recover from: accepting an offer you have no intention of honoring.
Reneging after signing is harmful. The company has rejected other candidates, stopped searching, and made internal plans. It costs them real money and time. And "tech is too big for word to spread" is a comforting thought, but it's mostly wrong. Recruiters move between companies. Hiring managers talk at conferences. Large companies often track this explicitly in internal systems.
You can negotiate hard. You can request extensions. You can use one offer to accelerate another. What you cannot do responsibly is accept an offer you're planning to decline.
If you're not planning to accept, say so. "I appreciate the offer. I'm not ready to commit by your deadline, so I won't be accepting. I hope we can work together in the future." That's harder than signing and ghosting. It's also what lets you re-apply, work with their team, or get referred by their recruiter four years from now.
Practice the Conversation Out Loud
One thing separates candidates who walk away with 20% bumps from those who get 5%: they've said the words before.
If you've never done a salary negotiation out loud, your first one will be rough. You'll second-guess your number the moment you hear a human voice. You'll fill silence with concessions. You'll agree to something you didn't mean to because quiet feels unbearable and agreeable feels safe.
This is exactly the same problem SpaceComplexity targets for coding interviews: the gap between knowing what to do and actually doing it under pressure with someone watching. Run the negotiation conversation with a friend or record yourself doing the counter. At minimum, write out the exact sentences you'll say before you pick up the phone.
The negotiation happens in real time. Not in your head.
Further Reading
- Salary Negotiation: Make More Money, Be More Valued - Patrick McKenzie's foundational essay, still the best single piece on the topic
- Dear Negotiation Coach: Dealing with an Exploding Offer - Harvard Program on Negotiation on the research behind deadline pressure
- Salary Negotiation Strategies - Candor's guide with FAANG-specific context including band structures
- Levels.fyi Ultimate Negotiation Guide - Compensation component breakdown with real data
- How to Sabotage Your Salary Negotiation Before You Even Start - Interviewing.io on the information disclosure mistakes that kill leverage