Recruiting operations
A working method for shortlisting at scale: build the scorecard first, run two passes, know which filters are real and which are proxies, and calibrate before you trust anyone's judgement — including your own.
A single advertised role in a metro Indian market can attract hundreds of applications within days, and a campus or entry-level posting can attract far more. At that volume, screening stops being a reading exercise and becomes a process-design problem. The question is not "is this a good resume" — it is "what decision am I making, on what evidence, in what order, and how do I know I am making it consistently." This guide sets out a method that works at volume, the filters worth applying, the proxies that quietly cost you good candidates, and how to tell when the problem is the pile rather than the screening.
The most common screening failure is starting with the applications. Once you begin reading, every criterion you form is contaminated by the candidates you have already seen — the third application quietly becomes the benchmark, and by the fiftieth you are comparing people to each other rather than to the job.
Before the first application is opened, write down what you are screening for. Four to six criteria is usually right, split into two groups: knockouts, which are binary and disqualifying, and evaluated criteria, which are scored. For each knockout, write the exact evidence that satisfies it. For each evaluated criterion, write what a strong, adequate and weak answer looks like.
This takes twenty minutes and it is the difference between a shortlist you can defend and a shortlist you can only describe as a feeling. It also gives you something to hand a second screener, which is what makes the next section possible.
Do not try to evaluate and reject in the same reading. They require different attention, and mixing them is what makes screening exhausting and inconsistent.
The first pass is a knockout pass. You are looking only at the binary criteria — the ones where the answer is present or absent. It should take well under a minute per application, and you should not be forming an opinion about anyone. A large share of the pile resolves here, and it resolves the same way regardless of who is doing it, which is exactly what you want.
The second pass is the evaluation pass, and it should take several minutes per application because you are now reading for evidence rather than presence. Score against the criteria you wrote. Write one line of reasoning per candidate — not for the candidate's benefit, but so that when the hiring manager asks why someone was rejected, the answer exists.
The order matters for a practical reason: the knockout pass is cheap enough to do on the whole pile, and the evaluation pass is expensive enough that you can only afford it on what survives. Reversing them is how screening backlogs form.
A knockout criterion is legitimate when it is genuinely necessary for the job and when its absence cannot be remedied in a reasonable ramp. Location where the role is on-site and non-relocating. A language where the role is field sales in a specific territory. A licence or registration where the work legally requires one. A hard technical capability the role uses from week one.
Everything else is a proxy, and proxies are where good candidates disappear.
Fresher applications look identical on the surface, which is a formatting artefact rather than a truth about the candidates. Because there is no employment history, almost all the signal sits in three places.
Projects are the first. What matters is not the project topic but the candidate's specific part in it, whether it had any real user, and whether they can describe a decision they made. A project with a README explaining why one approach was chosen over another is worth more than a longer list of project titles.
Internships are the second, and the useful question is what they were trusted with. An intern who shipped one small thing to production learned more than one who observed a large system for six months.
The third is the delta between academic record and demonstrated work. A candidate with a modest academic record and substantial self-directed work is telling you something specific about motivation, and it is usually a better predictor of early performance than the academic number alone.
For experienced candidates the signal is different, and three patterns carry most of it.
Scope growth is the first: did their responsibility widen across roles, or did they do the same job at three employers? Neither is disqualifying, but they predict different things. Tenure pattern is the second — the reasons behind short tenures matter far more than the count, and in some functions, sales particularly, short tenures are structural rather than personal.
The third is ownership language, and it is the most reliable single tell in the document. "Responsible for", "involved in" and "was part of" describe proximity. "I built", "I decided", "I moved" describe work. Candidates who did the work usually write the second way without being coached, and candidates who were adjacent to it usually cannot sustain the first way under a follow-up question.
Several data points appear on Indian applications that do not appear elsewhere, and each carries a screening decision.
Notice period is genuinely operational: a long notice period is not a quality signal but it does affect your timeline, and if your requirement is urgent it belongs in the job description rather than as a silent rejection reason. Current and expected compensation biases the pipeline and the decision; if your process collects it, keep it out of the screening pass and out of the shortlist discussion.
Employment history verification is a real concern in some segments of this market, where fabricated experience and shell-company references are a known pattern. Employers commonly address this with structured background verification and, where appropriate, checks against provident fund employment records. Whatever your approach, decide it as a policy applied consistently to a stage of the process rather than as an intuition applied to individual candidates during screening.
Two people screening the same pile against the same scorecard will disagree more than either expects. The fix is cheap: take ten applications, have both screeners score them independently, and compare. Where you disagree, the scorecard is ambiguous, and you fix the scorecard rather than arguing about the candidates.
Do this at the start of every significant search and again whenever a new person joins the screening rota. The output is not agreement for its own sake — it is a shared definition of what "adequate" means, which is the thing that silently drifts across a long search.
Then close the loop with the interview stage. Track how many of the people you shortlisted cleared the first interview. If almost all of them do, your screen is too tight and you are rejecting people you would have hired. If very few do, your screen is measuring the wrong thing, and the fastest fix is usually to sit in on two interviews and see what the panel is actually testing for.
Sometimes the shortlist is bad because the applications are bad, and no amount of screening discipline will fix it. Two diagnostics tell you quickly.
First, look at where your rejections cluster. If most of them fail on the same criterion, that criterion is in the wrong place — either it belongs in the job description as a stated requirement so that unqualified people stop applying, or it should not be a filter at all. Rejecting the same thing repeatedly is a job description problem being paid for with screening time.
Second, check whether the applications are on-target at all. A flood of irrelevant applications usually means the job title, the seniority signal or the channel is wrong, not that candidates are unserious. Retitling a posting and republishing it costs nothing compared with screening several hundred applications that were never going to work.
A JD-matching tool does the first pass well: it reads every application against your job description consistently, ranks them, and surfaces the requirement-level gaps so you can see why a resume scored where it did. That is genuinely useful, because consistency is the thing human screeners lose first at volume.
What it does not do is judgement. It cannot tell you that a candidate's project was unusually ambitious for their stage, or that a short tenure had an obvious explanation, or that someone from an adjacent domain will ramp quickly. Use the tool to order the pile and to make the knockout pass consistent, then spend your reading time on the evaluation pass — which is the part that actually decides who you hire.
Resumere's JD screening runs that first pass against your own job description and returns a match score with the criteria behind it, so the ranking is explainable rather than opaque. Candidates in the Resumere placement network also arrive with ATS-parsed profiles, which removes the formatting noise that makes resumes hard to compare in the first place.
More hiring guides, templates and recruiter tooling.
The components a job offer letter usually carries, the difference between an offer letter and an appointment letter, and the omissions that cause offers to be declined or disputed later.
How campus recruitment actually runs in India
Six complete, role-specific JDs you can copy
Stack depth over stack breadth. The JD that attracts engineers who ship and filters out keyword collectors.
The role most often mis-scoped as a data scientist. Fix the scope and the pipeline fixes itself.
Score applications against your own job description
JD screening scores every application against your own job description and shows the requirement-level gaps behind the score — so the pile is ordered before you start reading.