Most delays are not caused by a shortage of candidates. They are caused by unclear briefs, slow feedback loops and interview panels that keep changing.
When a role has been open for eleven weeks, the explanation you usually hear is that there is no talent in the market. Occasionally that is true. Far more often the pipeline was fine and the process leaked — candidates went cold waiting for feedback, the panel changed halfway, or the offer arrived a week after a competitor's.
Here is where the time actually goes, and what to do about each part, without dropping your standards to get a faster close.
1. Write the brief for one job, not two
The most common cause of a stalled search is a job description that describes two different people. A backend engineer who is also a data scientist. A sales head who will also run marketing. A finance controller with a compliance background who is also comfortable building dashboards.
Each of those exists. None of them exists at the budget attached. Before sourcing starts, separate must-haves from nice-to-haves and be ruthless about it: if you would reject a candidate for not having it, it is a must-have; everything else goes in the second list. A brief with more than five must-haves is usually two jobs.
2. Fix the panel before the first interview
Name every interviewer and every round before the first candidate is submitted. Adding a round in week three because a stakeholder wants a look resets the clock for everyone already in process, and it is the single most reliable way to lose your strongest candidate — who by definition has other options.
- Three rounds is enough for most roles. Four is the ceiling for anything below leadership.
- Block recurring interview slots in the panel's calendar for the duration of the search, rather than finding time per candidate.
- Give every interviewer a defined thing to assess, so rounds do not overlap and nobody has to be re-interviewed.
3. Give feedback in 48 hours, always
Feedback latency is the largest single component of time-to-hire in most processes, and it is entirely within your control. A candidate waiting six days for a verdict is a candidate talking to somebody else, and the recruiter chasing that feedback cannot tell them anything useful in the meantime.
4. Screen for intent, not just skill
A technically perfect candidate who is using your offer as leverage with their current employer costs you more time than a candidate who was never qualified. Intent should be tested early: why are they actually looking, what has changed, what would make them stay where they are, and what has their employer done the last time they resigned.
Notice period, current and expected compensation and counter-offer risk belong in the first screening call, not in the offer conversation. That is the whole point of a screening call.
5. Compress the offer window
Decide the compensation band before the search starts, and get approval for it before the final round rather than after. The gap between a final interview and a signed offer is where good candidates most often disappear, and almost all of it is internal approval time.
| Stage | Typical drift | Target |
|---|---|---|
| Brief to first shortlist | 2–4 weeks | 48 working hours |
| Shortlist to first interview | 1–2 weeks | 3–5 working days |
| Between rounds | 5–10 days | 48 working hours |
| Final round to offer | 1–2 weeks | 48–72 hours |
| Offer to acceptance | 1 week | 48 hours |
6. Keep the offer warm until the joining date
In India, notice periods of 60 to 90 days are normal, and a lot can happen in three months. The counter-offer arrives in week two. The competing process that was behind yours catches up. The candidate's manager makes promises. A signed offer is not a joined employee.
- 1Contact in the first week after acceptance — send the welcome pack and introduce their future manager.
- 2A short call at the midpoint of notice period, ideally from the hiring manager rather than HR.
- 3Documentation and system access confirmed two weeks before the joining date.
- 4A check-in in the final week, because that is when resignations from the new offer actually happen.
7. Measure the right number
Time-to-hire measured from requisition approval to offer acceptance hides the two stages that hurt most: how long the role waited before anyone started, and how long it took the accepted candidate to actually join. Measure requisition raised to joined, break it into stages, and look at where the days sit rather than at the total.
Once you can see the stages, the fix is usually obvious and usually free. It is almost never "post the job on another portal".
Frequently asked questions
What is a good time-to-hire in India?
For most mid-level roles, four to six weeks from requisition to offer acceptance is a healthy benchmark, plus the notice period before joining. Leadership and niche technical roles run longer because of market mapping and confidentiality. If a standard role is taking more than eight weeks, the cause is usually process latency rather than candidate supply.
Why do candidates drop out late in the process?
Nearly always because of silence or delay. Feedback that takes a week, an unexpected extra interview round, or an offer that arrives after a competitor's. Late drop-outs are a symptom of process speed, not of candidate seriousness.
How do we reduce offer drop-outs during notice period?
Test counter-offer risk during the first screening call, and then keep structured contact between acceptance and joining — a welcome pack in week one, a manager call at the midpoint of notice, documentation confirmed two weeks out and a check-in in the final week.