Overqualified and off-target: why mass job posts attract the wrong people, not just too many

A recruiter at an IT services firm in Pune put it plainly: “We had 4,200 applicants for 60 fresher support roles. The real problem wasn’t the count. It was that 700 of them had five-plus years of experience in unrelated fields, and another 900 had postgraduate degrees we’d never hire into a ₹3.2 LPA band.”

That is not a volume problem. That is a wrong-category problem — and it requires a different fix.

India’s campus hiring scale is well-documented. Over 1.2 million freshers were absorbed by industry in 2024-25, and 73% of Indian employers are planning fresher hiring in 2026. The pressure to hire fast and hire in bulk is real. But the more corrosive issue — one most HR teams don’t measure separately — is the ratio of off-target applicants embedded in every mass posting. These candidates won’t pass any screen you run. They were wrong before they clicked apply. Getting more screening throughput doesn’t help you; fixing who applies in the first place does.

Two failure modes that look like the same problem

A standard campus hiring funnel collapses two distinct filters into one painful process. The first is the wrong-type filter: is this candidate even in the right category for this role? Wrong experience band, wrong compensation expectation, wrong academic background, wrong location intent. The second is the wrong-fit filter: given that this candidate is broadly eligible, are they actually good enough?

Both show up as “rejection” in your ATS. Both increase time-to-hire. But they require entirely different interventions.

Wrong-fit rejections are a screening quality problem. You need better questions, more structured criteria, and sharper calibration of your scoring rubric. Wrong-type rejections are a sourcing signal problem. You need the JD itself to do more of the filtering before anyone lands in your pipeline.

The mistake most TA teams make is applying a screening solution to a targeting problem. You add more interview rounds, tighten the ATS filter, or deploy AI screening — and find your pass rates at the first screen are still dismal, because 30-40% of the volume never should have entered the funnel at all.

What mass postings signal to wrong-category applicants

When a company posts “₹3.5 LPA, 0-2 years experience, engineering graduates” simultaneously on Naukri, LinkedIn, campus portals, and job aggregators, three applicant groups respond:

First, your actual targets: 2024-25 batch graduates who are genuinely interested and roughly qualified. Second, career-stuck applicants with three to six years of unrelated experience who see a vague JD as an opportunity to reset. Third, postgraduate degree holders who apply because nothing in the JD explicitly rules them out.

Groups two and three aren’t a problem because there are many of them. They are a problem because no amount of AI-assisted screening will make them suddenly right for the role. You are spending infrastructure cost — AI interview slots, recruiter review time, HR bandwidth — on candidates with a known outcome.

In enterprise pilots running 2,500 to 3,000 candidate campaigns in a single evening, the pattern was consistent: approximately one-third of disqualifications came not from nuanced assessment of communication or aptitude, but from basic eligibility mismatches that could have been resolved before the structured interview began. The 15-20 minute structured screening conversation was wasted on a yes/no that should have been a 60-second knockout.

Three things that actually change who applies, not just who passes

The honest answer is that you cannot fully prevent wrong-category applications without changing what and where you post. Three levers matter:

Explicit compensation banding in line one of the JD. “₹2.8–3.6 LPA, freshers only, non-negotiable” in the opening sentence is the fastest wrong-CTC filter you have. Many companies in India still soften this language to preserve negotiation flexibility. What they actually preserve is a pile of wrong-salary-band applicants who cost recruiter time to remove.

Platform selection over broadcast reach. LinkedIn and Naukri generate volume. Unstop, Internshala, and direct campus career portals generate qualified volume. Using campus-native platforms as the primary intake channel — and treating aggregators as supplementary — substantially reduces the wrong-career-stage problem. A three-year experienced candidate on Unstop is an outlier. On Naukri, they are the majority.

Phase-0 knockout questions before any screening conversation begins. Firing two to three basic eligibility questions — batch year, CTC expectation, degree type — at the point of entry, before any interview slot is allocated, removes wrong-category applicants without consuming any structured screening capacity. A candidate who fails a batch-year check in 30 seconds costs nothing. The same candidate taking a 15-minute AI screen and then being rejected wastes both parties’ time and your per-interview budget.

For the capacity math on why this matters at scale, the earlier analysis of hiring 5,000 freshers as a capacity problem, not a sourcing problem lays out the arithmetic clearly.

The take

The volume problem and the match problem are not the same problem. Solving volume — through caps, ATS filters, or faster screening — doesn’t change who is applying. It just makes the wrong-category applicants easier to remove slightly faster.

The correct sequence is: fix targeting so fewer wrong-category applicants enter the funnel, then apply structured screening to the narrower, better-calibrated pool. Companies that do this in the right order find that their AI screening pass rates are materially higher — not because the AI got better, but because the input changed.

You don’t need a better screen for overqualified applicants. You need a JD that doesn’t invite them.