Applicants per hire

Count applications in one cohort

The calculation is straightforward:

applications received for a role or cohort ÷ hires from that cohort

If a campaign receives 120 applications and results in two hires, it used 60 applications per hire. That is an illustrative calculation, not a benchmark to chase.

If the matched cohort has no hires, do not calculate applicants per hire. Report the application count and zero hires separately, then revisit the ratio once there is a non-zero hire count.

The definition of an application matters. One person may apply to more than one role, so counting people instead of applications changes the result. Join’s candidate-profile documentation describes profiles that can contain multiple applications; teams using that model should decide whether the question is about submitted applications, unique people, or a particular role before comparing periods.

Draw the line before comparing roles

The numerator and denominator need the same boundary. A useful cohort might be applications submitted for one job ad during April, with hires attributed to that search. Mixing applications from an open role with hires from a later replacement search makes the ratio look precise while answering no clear question.

Source mix can also change it sharply. The CareerPlug 2025 Recruiting Metrics Report reports applications per job and applications per hire as separate recruiting measures. Keep that distinction: applications per vacancy describes inbound volume; applicants per hire connects that volume to an outcome.

Use it to choose the next question

A rising ratio can mean more interest, weaker targeting, a stricter selection process, or several of those at once. It cannot establish which explanation is true. Check the stage-by-stage movement with yield ratio, then review the quality of the eventual hires with quality of hire. The ratio earns its place when it prompts that investigation rather than becoming a target by itself.