Bulk hiring challenges for Indian IT services in 2026

When LTIMindtree announced plans to hire 5,000 freshers in FY26 (HR Katha, 2025), the conversation in their TA team wasn’t about where to find candidates. India’s engineering college system produces candidates at a scale the market can’t absorb. The conversation was about how to run first-round screens across 40+ campuses with a TA team sized for a fraction of that volume.

That mismatch — between the volume of hiring intent and the throughput capacity of HR — is the defining constraint in bulk IT hiring in 2026. It’s a logistics problem, not a talent problem.

The math that breaks hiring drives early

Take a mid-sized IT services firm targeting 3,000 fresher hires this season. The screening funnel for fresher roles typically runs at a steep ratio — many candidates for every eventual offer. That means tens of thousands of first-round interactions, each requiring scheduling coordination, recruiter bandwidth, and candidate follow-up. At any reasonable estimate of time-per-screen, the queue runs into weeks, not days. Well past the window when placement seasons close and candidates accept competing offers.

Nobody runs this math before the season starts. It surfaces during week three, when recruiter no-show rates are climbing and the shortlist is still 40% of target.

The standard fixes don’t hold at this scale. Contract recruiters need calibration time before they’re reliable. Extended timelines cause candidates to accept faster-moving employers. WhatsApp nudge campaigns add coordination noise without solving throughput. These are tactical responses to what is structurally an engineering problem.

Why IT services is harder than it looks from the outside

Consumer tech companies typically run one consolidated hiring drive with a few hundred slots across a handful of tier-1 colleges. IT services firms operate differently. They simultaneously source from IITs and NITs for high-complexity delivery roles, deemed universities for mid-tier volume, and state engineering colleges for the bulk of their headcount. Each campus runs on a different calendar, has a different placement officer with different expectations, and produces a candidate pool with meaningfully different preparation levels.

This multiplies coordination overhead multiplicatively, not linearly. A recruiter managing phone screens across three concurrent campuses is context-switching every 45 minutes while handling rescheduling, placement officer check-ins, and candidate queries in parallel. That’s not a sustainable operating mode at 3,000-candidate scale.

Infosys and TCS solved this historically through institutional infrastructure — a dedicated campus function built over years, pre-built assessment frameworks, deep college relationships. For IT services firms outside the top five by revenue, that infrastructure doesn’t exist. Bulk hiring for them is always somewhat improvised, and that improvisation breaks first at the screening stage.

Where AI-assisted screening changes the throughput ceiling

An enterprise pilot screened 3,000 candidates in a single two-hour evening window. Candidates self-scheduled via a link sent after application, called in at their chosen time, and completed a 15–20 minute structured conversation with no recruiter involvement in real time. HR reviewed scored shortlists the following morning. An 89% reduction in HR time per candidate, compared to manual phone screens, was the measured outcome.

That removes the scheduling-and-screen step entirely from the recruiter’s plate. It doesn’t remove judgment — borderline candidates still get human review, and final offers involve direct conversation. But for the clear no-gos — failed mandatory qualifications, communication significantly below role threshold, mismatched location expectations — the system can surface decisions without recruiter time investment.

The honest constraint: this only works if per-JD screener rubrics are built before the drive launches. A Java developer screen, a business analyst screen, and a technical support screen have different first-filter criteria, different communication benchmarks, and different weight on problem articulation versus domain knowledge. A single generic screener deployed across roles doesn’t outperform a generic phone screen — it just fails at higher volume.

The IT services firms getting real efficiency in 2026 are the ones spending time per role-cluster building screener frameworks before campus season starts. That upfront investment is what makes the throughput math hold.

The compliance overhead that arrived without warning

Several large global clients now require their IT services partners to demonstrate bias-auditable hiring practices for offshore delivery roles. The EU AI Act’s high-risk classification for AI used in hiring decisions (EU AI Act Article 6) is starting to appear in vendor contract language, even for Indian entities with EU-headquartered clients.

This adds a documentation layer to bulk hiring that didn’t exist five years ago. Every AI-assisted screening decision needs an audit trail: which rubric, what score, what threshold triggered the outcome. Most TA teams discover this requirement after deployment rather than before it. Building the audit trail architecture during screener setup is significantly cheaper than retrofitting it when a client asks for documentation post-drive.

The actual planning failure

Most IT services TA leaders budget for sourcing — job boards, campus connect fees, college visit logistics — and treat screening as a zero-cost step absorbed by the existing team. The result: the top of the funnel fills, and candidates stall mid-pipeline for weeks while recruiters work through the queue one phone screen at a time.

For a clear look at how the recruiter-to-candidate ratio math compounds across teams at different sizes, the 1:30 HR-to-candidate ratio breakdown maps the problem precisely.

India’s campus hiring produced approximately 1.2 million fresher hires in 2024–25 (NASSCOM / industry estimates). The firms that close faster in 2026 are the ones that treat screening as a logistics operation — staffed, tooled, and load-tested before the drives start — rather than an ad hoc activity that runs off recruiter goodwill.

The capacity ceiling is real. Plan around it before the season starts, not during it.