Mass Job Posts Attract the Wrong People, Not Just More

When a Bangalore IT services firm posts hundreds of ops-support openings in a typical ₹25K-₹30K CTC band, they expect volume. What they don’t expect is that a meaningful share of those applications will come from candidates with eight to ten years of experience and compensation histories well above the posted range. That gap between expected composition and actual composition is the overqualified applicants problem India’s volume hiring teams have stopped talking about — mostly because they’ve accepted it as background noise.

They shouldn’t.

The person-type problem is distinct from the volume problem

TA directors in Indian IT services consistently frame the challenge as “too many applications.” That framing leads to predictable solutions: tighter ATS filters, mandatory pre-apply assessments, harder qualification bars. These solutions attack headcount. They don’t touch the underlying mismatch.

Consider what halving your application count actually achieves if the remaining pool still contains a large share of mismatched CVs for every genuine fit. You’ve made the pile smaller. The ratio problem hasn’t moved.

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 top IT services firms alone hired more than 80,000 freshers in FY25 (NASSCOM). Lateral hiring in the same period contracted in IT services, BPO, and ops segments. The consequence: mid-career professionals with eight to twelve years of experience are applying to fresher-band openings at scale. They’re not confused — they know the CTC is below their history. They’re betting on getting in somewhere, anywhere, while markets reset. A ₹30K-range ops role is better than no role for someone who was earning significantly more six months ago and has limited runway left.

This is the person-type problem. It doesn’t show up as a keyword mismatch. It doesn’t fail an ATS filter. It passes every minimum qualification check. It only becomes visible when the screener looks at the candidate’s actual experience and salary history — and by then, your team has already spent time on a candidate who will either exit compensation discussion immediately or leave within weeks.

Wrong-type and wrong-fit: two failure modes that look like one

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. Those candidates won’t pass any screen you run. They were wrong before they clicked apply.

Why your JD is partly responsible

Generic JD language functions as a floor, not a ceiling. “Zero to three years experience, strong communication, team player” reads to a nine-year veteran as “I easily clear that bar.” The post was designed to describe a minimum, not a target persona. The overqualified candidate applies rationally: the JD invited them.

Who answers a broadcast posting

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.

Ceiling language and the CTC in the first line

Explicit ceiling language changes this dynamic. “This role is designed for zero to two years of experience; candidates with more than three years may find the scope of work limited” is blunt. Some HR teams avoid it because it sounds exclusionary. But it’s not exclusionary — it’s calibrating. The candidates who self-select out after reading it were going to be mismatched regardless. You’re just moving the filter earlier.

CTC-range disclosure does the same work at lower cost. In India’s current market, publishing a maximum CTC with no negotiation room filters out laterals faster than any skill assessment. Most candidates with higher compensation histories won’t apply to a job that states a ceiling upfront. The ones who still apply after reading that either genuinely want this scope of role, or they’ll tell you in the first conversation that their expectation is different. Either way, the information surfaces before your team invests time.

Where you put the number matters too. “₹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.

Where screening earns its value

For candidates who pass the JD filters and submit, the first conversation is the most efficient checkpoint. Not a skill assessment — an expectation calibration. Current CTC. Expected CTC. Willingness to commit to a specific location. These questions, asked in the first two minutes of a structured screen, surface person-type mismatches that no resume can show you.

This is where AI screening earns its place — not in scoring qualifications, but in running expectation-calibration conversations at scale before a human spends a minute on someone who was never going to work. In an enterprise pilot, phase-0 knockout questions running CTC expectations and location preferences cleared a substantial share of the queue inside the first ninety seconds per candidate — before any scoring began. The pilot completed 1,099 AI interviews across 14 campaigns. Nearly all of those early exits were person-type mismatches: laterals expecting compensation well above the posted band, candidates applying from locations that ruled out the posting.

In enterprise pilots running 2,500 to 3,000 candidate campaigns, the pattern was consistent: a large share 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. Any of those that reach a 10-20 minute structured screening conversation waste it on a yes/no that should have been a 60-second knockout.

So push the knockouts as early as they will go. 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 screening budget.

A related breakdown of volume screening tactics is covered in screening high-volume campus applicants without overwhelming HR, but the tactical mechanics only pay off once you’ve diagnosed whether your mismatch is a headcount problem or a person-type problem. Most teams haven’t done that diagnosis. 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 contrarian take

The recruiting industry’s obsession with reducing application volume misses the point. Cutting your inbound count means nothing if the remaining pool still contains candidates who clear every keyword filter, pass minimum experience requirements, and then fail compensation discussion in week one.

Person-type mismatch doesn’t respond to volume reduction. It responds to earlier, more specific signals about role scope, seniority target, and compensation reality. The teams that fix this problem aren’t the ones with the best ATS — they’re the ones who wrote honest JDs and built first-contact flows around expectations, not credentials.

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.

The bottom line

TeamLease EdTech reported that 73% of Indian employers planned fresher hiring in H1 2026. The drives are large, the timelines compressed, and the candidate pools include a significant share of overqualified applicants from a contracted lateral market. That’s not a prediction — it’s already the pattern from 2024-25.

The HR teams that get through drive season without burning out their recruiters will be the ones who treated person-type mismatch as a first-order problem, not an acceptable byproduct of volume. Fix the JD. Disclose the CTC. Build your first-contact screen around expectations. The headcount will follow.

Related reading: why volume hiring pulls overqualified applicants