Two questions that get confused
Every campus hiring team asks two different questions about a candidate, usually without noticing they are different:
- Is this student allowed to apply? Right university, right department and course, graduating this year, above the CGPA cutoff, no active backlogs.
- Is this student a good fit for this role? Skills that match the job description, strong academics in the subjects that matter, sensible answers to the screening questions.
The first is a yes or no question. The second is a ranking. We call the first Eligible and the second Matched, and we think a good shortlist needs both, shown side by side and never merged.
What goes wrong when you only see one
Only eligibility: the wide net
Suppose you open a graduate engineer trainee role to B.Tech CSE, IT, and ECE at eight campuses with a 7.0 CGPA cutoff. That can easily produce two thousand eligible students. Eligibility has done its job, since everyone on the list is allowed to apply, but it gives you no order. Recruiters fall back on proxies: campus tier, CGPA sorted high to low, or whoever registered first. CGPA alone is a weak signal across universities because grading scales and moderation differ, and “registered first” mostly rewards students who watch the portal closely.
A wide net is not a shortlist. Treating the eligible pool as the shortlist pushes the real filtering into the interview, which is the most expensive stage you have.
Only matching: the black box
The opposite mistake is a single “fit score” that quietly mixes hard rules and soft ranking. A student with an active backlog gets a 91% because their skills look great, and nobody notices until the university’s placement cell points out that the student is not eligible under your own criteria. Or a strong candidate is ranked low because one mandatory field was missing, and nobody can explain why. When the score cannot be explained, recruiters stop trusting it and go back to spreadsheets.
How the two views work together
Keep eligibility strict and binary. A candidate either passes every mandatory rule or does not, and the reason is visible: “Active backlog: 1,” “Course not in scope,” “CGPA below 7.0.” Rules are applied by the system, the same way for every campus, so no one has to re-check them per drive.
Then rank only within the eligible pool, and make the ranking explainable. In EzUnihire the match score is built from three things a recruiter can inspect for each candidate:
- Skills mapped against the skills in the job description
- Academic performance, read in context rather than as a raw CGPA
- Screening responses to the questions you set for the role
A recruiter looking at a 94% match can open it and see why. A recruiter looking at a 73% can see which part pulled it down and decide whether that part matters for this role.
A practical triage routine
Here is a routine that works well for talent teams running several campus drives at once:
- Set eligibility with the placement cell, in writing. Agree departments, courses, cutoffs, and backlog rules before the pre-placement talk, so neither side is surprised later.
- Start from the Matched view. Invite the top band for the first round. For most roles this cuts the first-round volume sharply without excluding anyone who is strong.
- Sample the Eligible view. Every drive, look at a handful of eligible students who ranked lower. If you keep finding good people there, your job description or screening questions are measuring the wrong things. Fix those, not the students.
- Look for strong matches who have not applied. Some of your best candidates never register because they assumed the role was not for them. Surfacing matched students before they apply, and inviting them, is one of the cheapest ways to improve quality.
- Keep both views in your reporting. Track offers by match band. If most offers come from the top band, the ranking is earning its place. If not, look at the inputs.
Why this matters for fairness
Campus hiring in India covers a wide range of institutions. A student at a state university with an excellent project portfolio should not be invisible because their campus is not on a legacy list. Separating Eligible from Matched lets you set clear, defensible rules for who may apply, and then rank on evidence that is actually related to the job. Both halves can be explained to a candidate, to a university, and to your own leadership.
If your team wants to see the two views on real campus data, take a look at the features page or book a demo and bring a job description you are hiring for this season.
