Offer Acceptance Rate

When hiring stalls, people look at the front of the funnel first. Not enough applicants, the posting isn't visible enough, send more sourcing emails. So the money and the effort all pile up at the entrance.

Some companies widened the entrance and still hired the same number of people. Twice the applicants, twice the interviews, and three hires in the quarter, same as before. Meetings blamed candidate quality, while what was actually happening is that half the finalists were turning down the offer — the proposal of salary, level, and start date the company makes at the end. Nobody could see it, because every number being watched described an earlier stage.

Offer acceptance rate exists to put an eye on that last stretch. It shows in one value whether hard-won candidates are being lost at the end, and how many of them.

Divide the number of offers accepted by the number of offers extended in the same period. Ten offers out in a quarter with seven accepted gives 70 percent.

The arithmetic is trivial; the differences between companies come from what gets counted. Four things are worth settling in advance.

1. The date that anchors a case — group by the day the document went out, or by the day the answer came back. An offer sent in the last week of a quarter gets answered in the next one, so without a rule the same case drifts between two periods.
2. Acceptances that fall through — someone who accepts and then changes their mind before the start date comes out of the numerator. The goal is a filled seat, not a signature. Leave those in and the metric stays high while the seat stays empty.
3. Cases that end verbally — the number gets said on a call, the candidate declines, and no document is ever sent. Drop those from the denominator and the rate reads higher than reality. Counting anything that reached the verbal stage is closer to what happened.
4. How results are grouped — read it by quarter, split by role. Merge engineering and sales into one figure and a problem on one side disappears inside the other side's numbers.

Sample size deserves the same attention. At a company extending eight offers a quarter, one case flipping moves the value by 12.5 percentage points. Reading four quarters in a row beats hunting for the cause of a single quarter's number. Teams with low volume sometimes record the counts alongside the ratio for this reason. Writing "2 of 6" carries the smallness of the sample in a way that "33 percent" does not.

The range people quote is 80 to 90 percent, but it's hard to use that as a standard. The market differs by role and by company stage. An early company without a known name, hiring into a competitive role, can sit in the 60s and be fine; a role that draws heavy inbound interest can hit 90 without surprising anyone. Comparing against the same company's last quarter is more useful than comparing against an industry average.

The other end is a signal too. A rate close to 100 percent suggests the terms are being set higher than they need to be, or that offers only go to candidates certain to say yes. Never being turned down also means never having reached for anyone. A team that always closes is worth asking about as much as a team that rarely does, because both patterns usually come from the same place — a hiring bar that has quietly been set by how comfortable the process feels rather than by who the team actually needs.

When the value drops, the cause is usually in one of four places.

1. The terms — the pay band, the salary range defined for each level, sits below the market. Repeatedly failing to close even at the top of the band points here.
2. Speed — if time to hire grew alongside the drop, candidates waited and went elsewhere. That's why the two numbers get read side by side.
3. The impression the interviews left — an interviewer who showed up unprepared, or a role whose actual scope stayed vague to the end.
4. A counter offer — the current employer moved to keep the person, which usually surfaces as an acceptance that falls through.

Separating those four takes more than the metric. Write one line of reason every time a candidate declines, and by the end of the quarter it's clear which of the four to work on. The reason given on a call is rarely the whole story — people soften it — so what matters is the pattern across a dozen of them rather than the wording of any single one.

"Offer acceptance was 50 percent this quarter. Last quarter it was 80."

We're losing half of them at the final step, so let's find the cause.

"It's not that acceptance dropped. It's that time to hire went up."

The reason the number moved is process speed, not compensation.

"Please make sure we ask this one for a reason when they decline."

Understanding the movement requires recorded reasons.

When engineering hiring jammed at Pagedeck, the first response proposed was more sourcing. Then Mia pulled the quarter's records: more candidates had reached the final round than in the previous quarter, and of six offers, two were accepted. Three of the four declines gave the same reason — two weeks of silence after the final interview.

Grace fixed the process instead of the band. Internal decisions would be made by the day after the final interview, and when a decision slipped, the candidate would hear where things stood anyway. The next quarter came in at four of five.

Many people read this as the people team's report card. They build and send the offers, so it looks like theirs. But the reasons candidates decline mostly sit outside that team. The pay band is set by leadership, the interview impression is made by the interviewers, and a slow decision is often the hiring manager's calendar. Use the number to evaluate one team and the causes stay unfixed, while that team starts declining to extend offers to anyone who might say no.

Reading it as higher-is-better leads to the same place. It's a percentage, so closer to 100 feels better. But set it as a target and the easiest way to hit it is to extend offers only to sure things. Acceptance climbs to 95 percent and the number of hires falls. This is a value that tells you where the leak is, not one to push up, and it only means something read next to hires made and time to hire.