Wipro Missed Its Own Fresher-Hiring Target by 3,000 Seats. Here's the Real Bottleneck

Wipro told the market it would onboard 10,000 to 12,000 freshers in FY26. It onboarded 7,500, more than 3,000 of them in the March quarter alone, and has now declined to set any fresher target for FY27 at all. CHRO Saurabh Govil put it plainly: fresher hiring is “completely on demand, very volatile environment.” That’s a 25-38% miss against the company’s own January 2025 guidance, from a company that runs one of the largest campus-hiring operations in India.

The easy read is demand uncertainty: IT services hiring is choppy, so the number moved. That’s true, but it skips the more useful question. Wipro didn’t miss because applicants didn’t show up. Companies at this scale never have an applicant shortage; a single opening at a name-brand IT services firm routinely pulls tens of thousands of resumes. The gap between “10,000-12,000 planned” and “7,500 delivered” is a gap in how fast an HR org can move a huge applicant pool through screening, offer, and joining before the business need shifts underneath the plan.

Why volatility punishes slow screening the hardest

A hiring target set in January and executed through the following March isn’t a single decision, it’s a pipeline running for over a year. When demand is stable, a slow screening funnel just means everything takes longer. When demand is volatile, and Govil’s own words say it now is, a slow funnel means the target moves before the pipeline catches up. By the time a batch of applicants clears a multi-week manual screening process, the business context that set the original 10,000-12,000 number may already be different. The plan doesn’t fail because the number was wrong on day one. It fails because the execution loop is too slow to track a number that’s allowed to move.

This is the same dynamic we described in why hiring 5,000 freshers is a capacity math problem, not a sourcing problem. The constraint was never getting enough people into the top of the funnel. It’s how many of them an HR team can actually move through a real conversation per week, and whether that throughput can flex up or down as fast as the target does.

What we’ve seen at pilot scale

In our pilot campaigns, 1,099 structured voice interviews ran across 14 separate hiring campaigns, and the AI screen auto-classified 60%+ of candidates as clear no’s before a recruiter ever opened a file. That second number matters more than the first for a volatility problem. It’s not just that interviews ran fast, it’s that most of the funnel got resolved without consuming a recruiter’s calendar at all. In one drive, 3,000 candidates were screened in a single evening, the kind of throughput that lets an HR team react to a target that’s still moving in month eight of a twelve-month plan, instead of locking in a hiring number in January and hoping the world holds still until March.

None of that guarantees Wipro specifically would have hit 12,000. Screening speed doesn’t fix a genuine demand collapse. If the business need for freshers actually shrinks mid-year, no amount of screening throughput manufactures headcount that isn’t there. What faster screening does is remove one whole category of shortfall: the one where the applicants existed, the roles existed, and the gap was purely how long it took to get a large pool through a structured conversation and a decision.

The contrarian part

IT services HR teams tend to explain a fresher-hiring miss the same way every time: “the market moved.” That’s rarely false, but it’s an incomplete answer that lets a slow screening process off the hook every single cycle. If your funnel takes six to eight weeks to move a candidate from application to offer, you are structurally exposed to any target that gets set more than six to eight weeks before it needs to be hit, and in a “completely on demand, very volatile” hiring environment, that’s most targets a large IT services firm sets. The fix isn’t a bigger sourcing budget. It’s a screening layer fast enough that the target and the execution move on the same clock.

What this means for the next drive

If your TA org is heading into a large campus cycle this year and demand feels as unpredictable as Wipro’s CHRO is describing publicly, the question worth asking isn’t “how do we source more applicants.” It’s “how many weeks does it take us to move 10,000 resumes into 10,000 screened, ranked, decision-ready candidates,” and whether that number is small enough to still be true by the time the business need is confirmed. Talk to us if you want to see what that timeline looks like against your own drive size.