A requisition for a data engineer has been open for 75 days. The hiring manager says recruiting is not sending good profiles. The recruiter says the manager rejects everyone. Both may be partly right, and arguing will not settle it. The clock itself can, if it is read properly.

Two clocks that measure different things

Time to fill runs from when the requisition is approved (or opened in the ATS) to when a candidate accepts the offer. Some organisations stop the clock at the joining date instead, which in India adds the notice period and can double the number. Either is fine as long as the definition is stated and consistent. Time to fill measures how long the business went without the capacity it asked for.

Time to hire runs from when a particular candidate enters the pipeline (applies, or is sourced) to when that candidate accepts. It measures the process from the candidate’s side: how long a good person had to wait through your stages, during which other companies could reach them first.

The two can diverge sharply. A requisition with a 75-day time to fill might have a time to hire of 18 days for the person eventually selected, because she was only found on day 57. Alternatively, a strong candidate may have entered on day 5 and still been in the process on day 50 because interviews were slow to schedule. The first case points to sourcing; the second points to the process. A single average across all roles hides both.

Breaking the 75 days into stages

The useful analysis is stage ageing: how many days the requisition, and each candidate, spent in each stage. For our data engineer role, the ATS history might show something like this:

StageDaysWhat happened
Approval to intake meeting8Manager unavailable for a week
Sourcing to first shortlist1012 profiles shared
Waiting for manager CV review9Batch reviewed after a reminder; 3 approved
Interviews, round one12Panel availability; 2 of 3 rejected, 1 withdrew
Second sourcing cycle14Criteria revised to add cloud certification
Second review and interviews16One candidate selected after two rounds
Offer approval and negotiation6Compensation above band; exception approval
Total75

Read this way, the argument resolves itself. Roughly 35 of the 75 days were spent waiting on people inside the company (the intake, the CV review, panel scheduling, offer approval). The requirement changed on about day 40, which effectively restarted sourcing. And the eventual offer went above the band, suggesting the original band was below market for the profile. Recruiting’s own stage, sourcing, took 24 days over two cycles: not trivial, but not the main story.

Common patterns and what they mean

  • Long waits between stages, short stages themselves. The bottleneck is decision-making. Fixes include agreed turnaround times (for example, CV feedback within 48 hours), pre-blocked interview slots on panellists’ calendars, and a backup approver.
  • Many candidates shared, very few approved. Either the brief is unclear or the bar has moved. Compare the rejected profiles with the intake notes. If they matched what was asked for, the requirement needs to be renegotiated openly.
  • Candidates approved but lost to withdrawals and declines. The process is too slow for the market or the offer is not competitive. Look at time to hire for those candidates and at stated decline reasons.
  • Few candidates at all. A sourcing or market problem: the skill is scarce, the location is unattractive, or the band is low. More recruiter effort alone rarely fixes a pay or location constraint.
  • Requirement changes mid-way. Each change should reset the clock in your analysis, or at least be flagged, because it is a different search.

Benchmarks, used carefully

People often ask what a “good” time to fill is. External benchmarks exist, but definitions vary so much (approval or posting as the start, acceptance or joining as the end, calendar or working days) that comparing your number with a published average is usually meaningless. The better benchmark is your own history for the same job family and level. If senior data engineers have historically taken 50 days and this one is at 75, something specific has gone wrong. If they have always taken 80, the issue is structural, and planning should start hiring earlier.

Making the clock work for you

A few practices turn time metrics from a source of blame into a management tool:

  1. Report median rather than average; one requisition open for 200 days distorts an average badly.
  2. Show stage ageing on open requisitions weekly, so delays are caught at day 20 rather than explained at day 75.
  3. Track time to hire per candidate at the offer stage, especially for in-demand skills where a slow process directly causes lost candidates.
  4. Agree service levels in both directions at the intake meeting: what recruiting will deliver by when, and how quickly the manager will respond.

Speed is not the goal in itself; a fast hire who leaves in four months is worse than a slower good one. But in most organisations, the majority of hiring time is not spent evaluating anyone. It is spent waiting. Measuring where the waiting happens is usually the quickest way to fill roles faster without lowering the bar.

Written by the RP Strativa Team. The requisition and figures are illustrative.

Leave a Reply

Trending