Fresher hiring is a campaign problem, not a pipeline problem

Most ATS platforms were built for steady-state hiring: a job opens, applications trickle in over weeks, recruiters work the funnel one stage at a time. That model breaks the moment you run a campus drive. Fresher hiring in India is not a pipeline — it’s a campaign. Tens of thousands of applications can land in 72 hours and then go quiet for the rest of the quarter. The tools you use to manage it have to be sized for the spike, not the average.

This is the single most common mistake we see TA leaders make when they evaluate hiring tech. They benchmark vendors on steady-state throughput and discover, on the morning of the drive, that the screening layer cannot keep up.

The pipeline mental model breaks down at scale

A pipeline assumes work arrives at a rate you can plan around. Two recruiters can carry steady-state lateral hiring at a sustainable interview load each week, and the math works.

A campaign throws that out. You open a graduate hiring window for a single Friday. By Monday morning your inbox holds enough resumes to fill a year of normal hiring. You have two weeks before offers need to go out, because the placement office has its own calendar and the candidates are talking to three other companies in parallel.

What looks like a slow trickle in a SaaS hiring stack is, in campus hiring, a flash flood. The metrics that matter change with the format:

• Steady-state hiring rewards conversion rates, time-to-hire, and recruiter utilization.
• Campaign hiring rewards burst capacity, rejection accuracy at the top of the funnel, and how quickly the funnel can be re-run if the first cut was wrong.

If your screening layer cannot rerun the entire top of the funnel in a single evening, it is not designed for campaigns.

What “campaign-shaped” tooling actually looks like

When we work with HR teams to redesign their campus flow, four things change once the pipeline assumption is dropped.

1. Concurrency is the headline number, not the average. You don’t care how many candidates a tool can handle per day on average. You care how many it can interview in the same 15-minute window. The default we run at is 20 candidates per slot, scaling up as the campaign demands. Anything that screens serially is the wrong shape for this work.

2. Rejection is the work, not the byproduct. In a steady-state funnel, the headline KPI is “candidates moved forward.” In a campaign, the headline KPI is “candidates correctly rejected, fast.” For a 5,000-applicant intake with 200 final slots, the first-filter is rejecting 4,800 people. Tools optimized for “find the best candidate” treat this as a side effect. We’ve argued before that the real ROI of AI screening is rejection accuracy, not speed — campaign hiring is where that argument actually pays off.

3. The funnel runs once, then stops. A pipeline runs forever. A campaign runs for two weeks and then the team goes back to lateral hiring. That means cost has to be elastic — you cannot afford to keep a screening team staffed for the trough between drives. This is part of why the per-interview pricing model that most AI screening vendors use feels wrong to campus-heavy hirers: you pay the same rate for the 4,800 rejections as for the 200 forward-passes, even though only the latter cohort has any human follow-up cost. We’re moving our own pricing toward a runway model for this reason.

4. The plan is a calendar, not a queue. Campaigns have hard external dates: placement-office slots, day-zero windows, offer-release deadlines. A queue-shaped tool gives you “next available” times. A calendar-shaped tool lets candidates self-schedule into 15-minute slots across a 48-hour window, and lets you reschedule when the placement office moves a date. This is invisible until it isn’t — and then it is the difference between making the deadline and missing it.

Why this framing matters for vendor selection

If you take a campaign view of fresher hiring, the questions you ask vendors change.

You stop asking “what’s your time-to-hire?” That metric is calibrated for the pipeline world. You start asking: “what’s the largest single-evening drive you’ve supported, and how many concurrent candidates did your system run in the same 15-minute window?”

You stop asking “do you integrate with our ATS?” Of course they do — every vendor checks that box. You start asking: “when 5,000 candidates apply in a weekend, what does the rejection workflow look like, and how do candidates who get rejected hear back without my recruiters writing 4,800 emails?”

You stop asking about per-interview cost as a benchmark. You start asking about the cost shape of an entire campaign — how a very large intake versus a smaller intake actually maps to invoiced spend. The unit economics for a single recruiter doing 30-50 phone screens per week look fine at ₹85–150 per call. Multiply that out to a 5,000-applicant drive and the numbers stop being defensible.

These are uncomfortable questions for vendors who built for steady-state SaaS hiring and pivoted into campus. They are normal questions for anyone who has run a campus drive in India.

What we do with this at HireQwik

The reason we frame the product the way we do — communication-first AI voice screening, 15–20 minute structured conversations, 20-candidates-per-15-min concurrency default, rejection-first scoring rubric — is that we have spent the last year running pilot campaigns at exactly this shape. We’ve put through more than 1,099 interviews so far, including a single evening where one TA team got through 3,000 candidates in 2 hours. None of that math works if you treat the work like a pipeline.

If you are planning a fresher drive for the July–September placement window, the most useful thing you can do this week is take the campaign view to whatever screening tool you are evaluating, and ask the four questions above. Most tools that look great in a pipeline demo do not survive the answers. The ones that do are the ones you can build a real campus operation on.

If you want to compare notes on how this looks in practice for a 5,000-candidate-class drive, we run short walkthrough calls with TA leaders preparing for the next cohort.