How Employers Make Hiring Decisions: A Fresher's Field Guide

Most campus placement decisions are made in a debrief session you never attend. Knowing what gets scored in that room changes how you prepare for everything before it.

The hiring process at Indian IT companies follows a consistent three-stage structure. Each stage eliminates a portion of the applicant pool on different logic, and passing one stage says little about your chances at the next. The criteria shift in ways that catch unprepared freshers off-guard.

For a complete preparation timeline covering every stage, FACE Prep’s interview preparation guide covers the week and day before the interview itself. This article covers the decision-making logic that runs behind every stage.

The Three Filters Every Campus Recruiter Applies

Campus recruitment at Indian IT companies runs on three sequential filters, whether the company is a mass-hire services firm or a mid-size product company. Each filter has a different purpose and a different elimination rate.

Filter	What it tests	Who runs it	What eliminates a candidate
Resume screening	Eligibility and relevance to the role	HR team	CGPA below cutoff, branch mismatch, graduation year outside window
Online assessment	Baseline technical and aptitude skills	Assessment platform	Percentile or raw score below the company’s threshold
Interview rounds	Communication, thinking process, and fit	Hiring panel	Panel rubric score across four evaluation dimensions

The first filter is largely automatic. Resumes that don’t meet stated eligibility criteria are screened out before a human reads them. This is why resume-to-JD alignment is a prerequisite at the application stage, not a strategy.

The second filter is where most candidates at mass-hire drives are eliminated. At IT services companies, this round typically covers quantitative aptitude, verbal reasoning, and basic coding. At product companies, the coding section is harder and often includes data structures. Clearing this round places you in a pool small enough for a panel to evaluate individually.

The third filter is where the actual hiring decision is made. Most freshers prepare for what to say in an interview. Fewer think about how the panel scores what they say.

These three filters are not independent events. HR teams design them to reduce the applicant pool progressively: the online assessment passes through the top portion of the academic pool, and the interview identifies who from that shortlist will actually perform in the role. Understanding this sequence helps you allocate preparation time correctly.

Before your interview, check AmbitionBox for candidate-reported experiences at the specific company you’re targeting. The data there often shows exactly how many rounds ran, which technical topics came up, and how long the panel took to communicate a decision.

What Panel Evaluators Score After Your Interview

After each interview round, panel members fill in an evaluation form. The exact template varies by company, but the dimensions being scored are consistent across most Indian IT hiring processes.

Evaluation dimension	What evaluators look for	How it shows in your answers
Technical depth	Can this candidate apply the concepts on their resume?	Accurate answers to follow-up questions on claimed projects
Communication clarity	Can this candidate explain technical ideas to a non-specialist?	Clear structure, logical flow, no excessive filler words
Role and team fit	Would this person complement the existing team’s working style?	Specific examples of collaboration, not generalised claims
Initiative signals	Does this candidate take ownership beyond what was required?	Self-started projects, certifications with applied output

Two candidates with identical test scores frequently receive different panel ratings. The difference is almost always in the specificity of their answers. A candidate who says “I built a recommendation system using collaborative filtering for my final-year project, here is what the precision score was and what I would change” scores higher on technical depth than one who says “I am familiar with machine learning and have done projects.” Both statements can be equally true. Only one gives the panel something concrete to score.

A common gap for technically prepared freshers is explaining their work to a non-specialist. The communication clarity dimension scores exactly this. If you can explain your project to a relative who works outside tech, you can explain it to an HR interviewer sitting next to the technical panel member.

The Calibration Stage You Never See

The decision most freshers don’t prepare for is the calibration meeting: the session between HR and the hiring manager after all individual panels are complete.

In this session, two things happen. Each panel member shares their individual scores and notes for each candidate. Then the group reconciles disagreements. If two panel members rated the same candidate differently on communication, they discuss why and reach a consensus score.

This calibration conversation typically happens within a few hours of the final interview round, while observations are fresh. The output is a ranked or tiered candidate list: clear offers, clear rejections, and a waitlist of borderlines. Waitlisted candidates remain active until offer acceptances come in. If an accepted offer is later declined, the calibration list determines who gets the next call.

Calibration is where borderline cases get resolved. A candidate rated “maybe” by one interviewer and “yes” by another will either reach the offer list or not, depending on which concerns are considered blockers and which are considered trainable gaps.

One observation that surfaces regularly in calibrations: the candidate’s conduct throughout the day. How they behaved with support staff, whether they asked thoughtful questions at the end of their interview, and how they interacted with other candidates in the waiting area. These are not always on the formal evaluation form, but they inform how the panel discusses close cases.

Your formal interview performance is the primary input into the calibration. It is not the only input.

The Five Factors That Tip a Close Decision

When two candidates have cleared every filter and scored similarly on the formal rubric, the final decision often comes down to factors that are observable but not always on the evaluation form.

• Resume-to-JD alignment. The candidate whose resume specifically addressed each requirement in the job description is easier to justify in a calibration meeting than one who is generally strong but tangentially relevant.
• Question quality at interview close. Candidates who asked specific, well-researched questions at the end of their interviews signal genuine preparation. Candidates who asked nothing, or asked generic questions about the company culture, leave a weaker impression.
• Interaction with non-panel staff. Campus drives involve coordinators and administrative staff. How you treat people outside the formal panel is observed, and sometimes mentioned during the calibration stage.
• Follow-up note. Sending a brief, specific thank-you note to your recruiter contact within 24 hours of your interview is uncommon among fresher candidates. Done well, one focused paragraph with no spelling errors, it surfaces your name again during the calibration window.
• Clarity on role specifics. Candidates who can articulate what they want to work on at that specific company, rather than offering generic enthusiasm for the brand, are easier to advocate for in a calibration discussion.

None of these are secret. They are observable signals that a calibration participant can cite when making the case for a specific candidate. The goal is to give one person in that room a specific, concrete reason to advocate for you.

AI Fluency Is Entering the Technical Rubric

The five factors above apply across company types and hiring years. There is one shift specific to 2026 that changes how freshers targeting product-tier roles should plan their preparation.

At product-tier companies, the technical interview rubric now often includes applied AI as an evaluated area. Not theory, but practical output: have you built something with an LLM API, evaluated model outputs for a real use case, or worked with retrieval-augmented generation at a level where you can explain the tradeoffs? This is less common at mass-hire IT services companies, where DSA and aptitude remain the dominant technical filter. But for candidates targeting product roles, applied AI skills have moved from a differentiator to an expected baseline.

This connects directly to the initiative signals and technical depth dimensions in the panel rubric. A deployed AI project with concrete, describable results is the kind of answer that scores well on both simultaneously. The applications that score highest on technical depth in 2026 product-company rubrics increasingly include demonstrated output, not coursework alone. A GitHub link with a working project gets discussed in the calibration meeting. A list of online certifications gets noted and set aside.

TinkerLLM at ₹299 is the entry point. It gives you a structured environment to go from reading about LLMs to something built and ready to discuss in a technical round. For the HR round, the HR interview guide covers how to present project work once you have it.

If campus placements didn’t produce an offer, see FACE Prep’s guide on what to do after campus placements. It covers how the hiring decision logic shifts for direct applications.