You extend an offer to a candidate everyone loved, you're feeling good, and then you hear the words that make recruiters everywhere panic: "Can I have a week to think it over?"
The instinct is to assume they're shopping the offer. Sometimes that's true. After managing hundreds of technology searches, here's what I've learned about why a candidate takes a week to accept a job offer: it's usually less about the candidate and more about the process that got them there. More often than not, a week to accept isn't a candidate problem. It's a preparation problem, and preparation is the recruiter's job.
The Offer Should Be a Formality, Not a Surprise
Here's what a lot of people get wrong: closing doesn't happen when the offer letter goes out. It happens over the weeks before that, in every conversation a good recruiter has with the candidate along the way.
When I'm working a search, I'm not just scheduling interviews and passing along feedback. I'm setting expectations from the first call: what the comp range looks like, what the culture is really like (not the brochure version), what the role will demand in year one, how the team operates, what growth looks like two years out. By the time a candidate gets to a final round, they should already know what's coming. So when the offer finally lands, it shouldn't be new information. It should be confirmation.
Ashby analyzed 230,000 applications that reached the offer stage between January 2021 and March 2024 and found that candidates who accept a job typically do so within two to three days of receiving the offer, a number that fell from roughly 2.8 days to 2 days as the market tightened (Bryce Codell, "Offer Acceptance Rates," Ashby Talent Trends Report, June 6, 2024, ashbyhq.com). Candidates rarely need a week because of the offer itself. They need a week because questions they should have answered earlier are still unanswered.
What Happens When It Doesn't
We ran a search last year for a backend engineer. The candidate crushed the final round. Then the client went quiet. Three weeks, no update to us, no update to the candidate, while the hiring team sorted through their own internal decision-making.
When they were finally ready to move, the client wanted to extend the offer directly and didn't loop us in on the number beforehand. So we had no chance to prep the candidate for what was coming, no chance to remind him why he was excited, no chance to ask the one question that might have changed everything: what happens if your current company counters?
He asked for a week. He used it to have that exact conversation with his current employer, who came back with a number and a promotion timeline. He took it. (If you're wondering whether he made the right call, we've written about that too.)
Nothing about that candidate was flaky. He did what anyone does when they're left alone with uncertainty for three weeks: he looked for certainty somewhere else. Once the recruiter was removed from the conversation, nobody was left managing the candidate's expectations.
That search is a big part of why we push back now when a client goes fully dark between final round and offer, or wants to hand-deliver an offer without giving us the number first. It's not about control for its own sake. It's that the recruiter is usually the only person in the process whose whole job is tracking what the candidate is thinking week to week, and that job doesn't stop being useful the moment the offer gets written.
Where the Time Actually Goes
That candidate's story is really a bandwidth story, on both sides. An internal recruiter stretched across a dozen open reqs, or a contingent recruiter running ten searches at once chasing whichever one pays first, doesn't have the hours to keep one candidate's head in the game for three quiet weeks. That's not a knock on either.
It's math. You can't give one candidate ten hours of relationship-building when you're covering ten roles.
Somebody has to own those conversations. Whether that's an internal recruiter with the time to do it or an embedded recruiting partner almost doesn't matter. What matters is that somebody is having them. That's the actual case for retained search: not that it replaces an internal team, but that it gives that team an extra set of hands to do the part that's easy to skip when everyone's stretched thin. Someone stays close enough to the candidate that by the time the offer goes out, it's a formality, not a decision.
Bottom Line
A week isn't automatically a red flag on the candidate. It's usually a signal about what happened, or didn't happen, in the weeks before the offer went out. We track offer acceptance obsessively at 2Bridge because it's one of the clearest indicators of whether we're doing our job well. Today, our offer acceptance rate is 95%, and it's earned in the small, unglamorous work of staying close to a candidate for six weeks, not in the day the offer finally goes out.
If your offers routinely slow down at the finish line, it may be worth looking at the six weeks before the offer instead of the twenty-four hours after it.
