Hiring in India in 2026: what actually moves time-to-hire
Every hiring team we talk to in India measures time-to-hire. Very few can tell you which part of it they actually control. The number gets reported as a single average, 42 days, 55 days, 68 days, and then gets attacked with tactics that address the smallest slice of it.
Here is what the stages usually look like for a mid-level engineering role at a 200-person company, and where the time really goes.
The notice period is not your bottleneck, but you plan as if it were
A 60- or 90-day notice period is the most visible number in Indian hiring, so it absorbs most of the blame. It deserves less of it than it gets. Notice is fixed cost: it starts only after the candidate accepts, and no amount of process improvement shortens it.
What it should change is your planning horizon, not your pipeline. If a role must be productive by October, and the market standard is 60 days' notice plus a 35-day search, the requisition needs to open in June. Teams that treat notice as a surprise at the offer stage are not slow at hiring, they are late at starting.
The genuinely useful lever here is buyout negotiation, and it is underused. Many companies will fund a notice buyout for a senior hire but have no policy for mid-level roles, so recruiters never offer it. A documented buyout band, approved in advance, converts a 60-day wait into a 30-day one for a predictable cost.
Where the time actually disappears: between the stages, not inside them
Interviews are short. Scheduling them is not. When we break down a typical 45-day search, the interviewing itself accounts for perhaps four hours of real time. The rest is queueing:
- Resume sitting unreviewed — often 3 to 6 days, because screening is nobody's primary job
- Panel scheduling — 4 to 8 days per round when three senior engineers must find a shared slot
- Feedback lag — 2 to 5 days between the interview and a written verdict
- Approval to extend an offer — 3 to 10 days, longer if compensation exceeds a band
Add those up and the dead time dwarfs the active time. A team that cuts feedback lag from four days to one, across three rounds, saves more calendar time than one that shortens every interview by half.
The fix is unglamorous: a service-level agreement on feedback, enforced by a visible dashboard, and interviewer calendars with pre-blocked slots. Neither requires new software. Both require someone to own the number.
Tier-2 sourcing works, but not the way it is usually sold
The pitch for hiring outside Bengaluru, Delhi NCR, Hyderabad and Pune is usually about cost. That framing sets teams up for disappointment, because the compensation gap narrows every year and a candidate hired purely on cost tends to leave on cost too.
The stronger argument is competition density. In Indore, Coimbatore, Jaipur or Kochi, a strong engineer may be fielding two offers rather than seven. That changes the two metrics that hurt most: response rate at the top of the funnel, and offer-drop rate at the bottom.
What makes it work in practice is committing to it structurally. Remote-first interview loops, a written policy on travel and onsite frequency, and at least one senior person in the same time zone. Teams that treat tier-2 hiring as an experiment, one requisition, no process change, reliably conclude it does not work, because for them it did not.
Offer drop is a symptom you can read backwards
Offer-drop rates of 20 to 30 percent are common in Indian tech hiring, and the counter-offer takes most of the blame. But a candidate who accepts a counter-offer was usually reachable earlier in the process, and the signal was there.
Three predictors, in rough order of usefulness:
- Elapsed time from first contact to offer. The longer the process, the more parallel processes the candidate has accumulated. Speed is a retention tactic before it is an efficiency one.
- Whether the candidate has met their prospective manager. Loops that are entirely peer-panel produce offers with no relationship behind them.
- Whether compensation was discussed early and honestly. Discovering a 30 percent expectation gap at the offer stage means five weeks were spent on an outcome that was arithmetically impossible in week one.
The third is the cheapest to fix and the most often skipped, usually because recruiters worry an early number scares candidates off. It does, but it scares off the ones who were never going to accept, which is the entire point.
What to measure instead of time-to-hire
A single average hides everything useful. Three numbers that are actually actionable:
- Stage-to-stage latency, tracked separately. This tells you where to intervene; the aggregate never does.
- Offer-accept rate segmented by source. A channel with high volume and low accept rate is costing you time, not saving it.
- Requisition age at time of opening — how far in advance of the need date the role was actually posted. This is where most "slow hiring" originates, and it is a planning failure rather than a recruiting one.
The short version
Most time-to-hire problems in Indian hiring are not sourcing problems. They are queueing problems dressed up as sourcing problems. Before you buy another sourcing tool, measure how long a resume waits before someone reads it, and how long feedback takes after an interview ends. In most teams those two numbers, added together, are larger than everything else you are trying to optimise.