How to Calculate Cost Per Hire (And What to Actually Do With the Number)

Cost per hire is a simple formula that's frequently calculated inconsistently, which makes it hard to compare across companies or even across time within the same company unless the inputs are defined clearly and applied the same way every time.

The formula itself

Cost per hire = (total external recruiting costs + total internal recruiting costs) ÷ total number of hires in the period. The formula is simple; almost all the real difficulty is in deciding what counts as a recruiting cost in the first place, which is where most inconsistency between companies (and even within the same company over time) actually comes from.

External costs are usually the easier, more obvious half

Job board and posting fees, agency and staffing firm fees, background check and assessment costs, recruiting event and sponsorship costs, and job-board/ATS software subscription costs (prorated appropriately) are the more straightforward external inputs — the main risk here is simply forgetting a real cost category, like a recruiting-specific software subscription, rather than any conceptual ambiguity.

Internal costs are where most calculations quietly go wrong

A prorated share of recruiter and sourcer salary and benefits, a reasonable share of hiring manager and interviewer time (often skipped entirely, though it's a genuine cost), internal referral bonuses, and relocation or signing bonus costs where applicable are the internal side — and the most commonly, quietly omitted piece is interviewer time, which is a real cost even though no invoice for it ever arrives.

Decide your time period and hire-count denominator before you start, and stay consistent

Calculating cost per hire over a full quarter versus a single month can produce very different numbers purely from timing effects (a large agency invoice landing in one month versus spread over a quarter), independent of anything real changing about recruiting efficiency. Picking a consistent period (quarterly is common) and sticking with it makes the number comparable over time in a way that switching periods opportunistically never will.

What a high or low cost-per-hire number does and doesn't tell you

A high cost per hire isn't automatically bad — it may reflect necessary investment in hard-to-fill senior or specialized roles where a lower number would mean under-investing in sourcing quality. A low cost per hire isn't automatically good either — it can reflect under-resourced recruiting that's producing worse hires who cost more later in turnover and ramp time. The number is only genuinely useful alongside quality-of-hire and retention data from the same period, not read in isolation.

Use it to compare trend and role type, not as a single universal target

Cost per hire is most useful tracked over time for the same role type (is sourcing an engineering role getting more or less expensive quarter over quarter) or compared across role types to understand where recruiting spend is genuinely concentrated — rather than treated as a single number the whole organization should minimize regardless of role complexity or seniority.