Most job offers that get declined weren't declined because of the number. They were declined because the offer felt like a form letter from a company that hadn't been paying attention. If you're a tech leader who has already read the "be competitive and move fast" articles and still losing candidates at the offer stage, this is for you.
The direct answer: a job offer engineers accept is personalized, pre-validated, and structurally transparent. It reflects the specific conversation you had with that specific candidate — not a template your HR team sends to everyone. If you nail those three things, your acceptance rate will be above 85%. Miss them, and you're leaving it to chance.
The conventional advice — "move fast, be competitive, explain equity" — is true but insufficient. Here's what gets glossed over:
| Component | What to Include | Common Failure Mode |
|---|---|---|
| 1. Role Framing | One paragraph that names the specific problem this person will own — not a job description copy-paste | Generic title + team name with no context |
| 2. Base Salary | Exact number + band context ("this is the top of our L4 band") | Just the number, no context on growth ceiling |
| 3. Equity Breakdown | Share count, current 409A FMV, vesting schedule, cliff, and a worked example of what 1x, 5x, 10x exit looks like | Just the share count and vesting schedule — useless without FMV |
| 4. Bonus Structure | Target %, historical payout rate (be honest), and what drives it | "Up to 15%" with no context — candidates assume 0% |
| 5. Benefits Highlight | Pull out 3–4 benefits that came up in conversations or match their stated priorities | Full 20-page benefits PDF attached — no one reads it |
| 6. The Personal Note | 2–3 sentences from the hiring manager referencing something specific from the interview process | Omitted entirely, or a generic "we're excited to have you" |
At Hypertalent, we coach hiring managers to draft the personal note before the equity section — it forces them to think about this as a communication to a human, not a compensation transaction.
You're offering a senior backend engineer $195K base + 0.3% equity at a Series B. Google counters at $220K base with RSUs. You cannot win on base salary. Stop trying. The offer letter should lead with the equity narrative: model out what 0.3% is worth at your last post-money valuation, your projected exit range, and the vesting timeline. Then add one line: "At Google, your comp is fixed. Here, it's a function of what we build together." Corny? Slightly. Effective? Yes — because it reframes the comparison. Also: have the CEO or CTO co-sign the offer. The personal weight matters at this inflection point.
They went through the process professionally but never pinged you between rounds. Acceptance risk is high. The mistake here is sending a standard offer and hoping. Instead: before you send the written offer, have the hiring manager call them — not to pitch, but to ask: "Is there anything in the offer we're putting together that would make this an easy yes for you?" This conversation, done well, surfaces the real objection while you still have time to address it. Then tailor the offer letter to directly answer whatever came up.
They want $210K; your band tops out at $195K. Don't send $195K and hope. Send $195K and explain: "Our L5 band is $175K–$195K. We're offering the top of that band, which we reserve for candidates who come in with your level of experience. The next band review is in Q1, and the criteria for moving to L6 are X, Y, Z." Transparency about the ceiling converts more candidates than a number that's mysteriously 7% below their ask. If you want help benchmarking whether your bands are even competitive, book a free consultation with Hypertalent — we run this analysis across dozens of companies every quarter.
The written offer should never be the first time a candidate hears a number. If there's any ambiguity after the verbal offer conversation — "sounds good, I'll think about it" — you do not have alignment. Sending the formal document into that ambiguity is how you create a situation where a candidate sits on an offer for five days and then declines. The fix: end the verbal offer call with a direct question. "If we can get you an offer at X, are you ready to move forward?" An enthusiastic yes or a specific objection are both good outcomes. A vague positive is not.
Yes, with context. Showing the band prevents future resentment when they learn a new hire is at the top of it. But you need to frame it: tell them where they sit and why. "We're placing you at $195K, which is the 90th percentile of our L5 band, reflecting your eight years in distributed systems." That framing makes the number feel earned, not just assigned.
Five business days is the standard. For senior or executive hires, seven is reasonable. Anything longer than ten signals you're not serious about the hire. If a candidate asks for more time, the right question is: "What's the timeline driven by — another process, a personal consideration?" That tells you whether you're waiting on a competing offer to close or a life event, and you can respond accordingly.
Ask about them early — during the process, not at the offer stage. If you know they're interviewing at three other companies, you can time your offer strategically and address the likely competitors directly. Waiting until they mention a counter-offer puts you in a reactive position where you're bidding against a number you can't verify and a company you probably can't beat on cash.
The legal document comes from HR or legal. But it should be accompanied by a personal note from the hiring manager — even if it's just three sentences in the email body. The signal that the person who interviewed you is personally invested in you joining is one of the most underrated conversion levers in the process.
Follow up at 48 hours with a no-pressure check-in: "Just wanted to make sure you got everything you need — happy to walk through the equity math or answer any questions." If they go silent after that, a second follow-up at day four is appropriate. Do not chase more than twice. If a candidate won't engage after two genuine attempts, you likely lost them before the offer stage and didn't know it.
Writing a great offer isn't a one-time skill — it's a system your team builds over dozens of hires. The companies that consistently hit 85%+ offer acceptance rates have a pre-offer conversation protocol, a modular offer letter template that's genuinely customizable, and someone accountable for the candidate experience between verbal and written offer. If you're building that system from scratch, or you've lost two or three candidates at the offer stage in the last quarter and want to understand why, the Hypertalent blog has additional frameworks on compensation benchmarking and candidate closing strategy.
At Hypertalent, we work embedded with engineering hiring teams to close exactly these kinds of gaps — from offer structuring to competitive benchmarking to coaching hiring managers on the conversations that actually move candidates. If your offer acceptance rate isn't where it should be, the issue is usually diagnosable in one conversation.
Ready to hire world-class tech talent?
Hypertalent sources pre-vetted engineers, designers, and PMs — faster than traditional recruiting.
Book a Free Call with Hypertalent.png)
.svg){kind=icon}
