Recruiting Metrics

How do I find the bottleneck in my hiring funnel?

Lay out conversion rate and median time in stage side by side for every step, then look for the stage where either number is worst. Conversion problems mean the wrong people are entering or the bar is misapplied. Time problems mean a scheduling or decision blockage. Fix the single largest one before touching anything else.

Which numbers reveal a bottleneck?

Two per stage, read together. Conversion rate tells you how many candidates move from one step to the next. Time in stage tells you how long they wait there. A stage with low conversion is filtering, which may be correct or may mean the bar is misapplied or the pool is wrong. A stage with a long dwell time is blocked, almost always by scheduling or by a decision nobody is making. The pattern matters more than any single figure. A funnel that loses most candidates at first screen has a sourcing or advert problem. One that loses them after final interviews has a bar or an offer problem. Pull both from your [recruitment analytics](/recruitment-analytics-software) rather than reconstructing them by hand.

How do you tell a real bottleneck from normal filtering?

Compare against your own history and against similar roles, never against a published benchmark. Every funnel narrows, so a low conversion rate is only meaningful if it is worse than what the same role produced before, or worse than a comparable role today. Three questions sharpen it. Did this stage always convert at this rate, or did it change. Are candidates being rejected here, or are they withdrawing, which is a completely different problem. And are the people who pass this stage succeeding later. A stage that rejects heavily but produces strong finalists is working. One that passes people who then fail consistently is not filtering at all. Ask the interviewers at that stage what they are rejecting for, since the answer often differs from the scorecard.

What do you do once you have found it?

Fix one stage, then measure again before changing anything else. Simultaneous changes make the result uninterpretable. If the block is time in stage, the fix is usually mechanical: self-service booking through [interview scheduling software](/interview-scheduling-software), a feedback deadline, or pre-agreed offer approvals. If the block is conversion at screen, look at the advert, the sourcing channels and the screening criteria. If it is conversion at offer, examine compensation, speed and how well the role was sold. Give each change a few weeks and a named owner. Also record the reason candidates leave at each stage, because a stage that leaks through withdrawal needs a different intervention from one that leaks through rejection. Write down what you expect the change to do before you make it, so the result stays interpretable.

How often should you review the funnel?

Weekly at a glance for live searches, monthly in depth by role family. Weekly review catches the practical problems while you can still act: interviews not booked, feedback outstanding, a source that stopped delivering. Monthly review by role family is where structural patterns appear, since a single requisition rarely has enough volume to say anything reliable. Keep segments separate. Engineering, sales and support funnels behave differently, and averaging them hides the problem you were looking for. Watch the trend rather than the absolute value, and treat a stage that is deteriorating over two or three months as a signal even when it still looks acceptable. Bring the review into the same weekly meeting where blockers already get owners and dates.

Want Pitch N Hire to handle this for your team?

Related glossary terms

Next step

FAQ

Frequently asked questions

What if my volumes are too small for meaningful rates? +
Group similar roles into families and look at several months together, or work with counts rather than percentages. With a handful of candidates, one withdrawal swings a rate wildly and invites overreaction. At low volume, time in stage is the more reliable signal, because a delay is a delay regardless of how many people it affected.
Should I compare my funnel to industry benchmarks? +
Treat published benchmarks as rough context, not as targets. They mix industries, seniorities, locations and definitions, and few organisations measure stages the same way. Your own trend over time is far more actionable, because it is measured consistently and it reflects the roles you actually hire for.
Is a low offer acceptance rate always a pay problem? +
No. Slow processes, a poor final round, an unconvincing manager conversation and a role that was described vaguely all produce declines. Ask every candidate who declines for the reason and record it. After a handful of answers the pattern is usually obvious, and it is frequently not compensation.
Which stage causes the most trouble in practice? +
The gap between interview and decision is where most teams lose the most time, because it depends on people whose main job is not hiring. It rarely appears in a monthly report as a problem, since each individual delay looks small. Measured as time in stage across a quarter, it usually stands out immediately.
Built for recruiters & hiring teams

See how much faster your team could hire

Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo