Campus Recruitment Day: A Round-by-Round Prep Guide

Campus placement day compresses months of preparation into a single 8 to 10 hour window, and the students who do well are the ones who know what’s coming before they walk in.

The typical campus placement day: what actually happens

The sequence is usually the same, whether the company is a large IT services firm or a mid-size product company visiting campus:

1. Registration and document verification — You submit copies of your marksheets, ID, and resume. At a large drive with 200 or more candidates, this alone can take 45 to 60 minutes.
2. Pre-placement talk (PPT) — The recruiter walks through the company’s work, culture, compensation, and the role on offer. Pay attention. Interviewers commonly ask “what do you know about us?” and the PPT is the intended answer.
3. Aptitude test — Online or paper-based. Tests quantitative ability, verbal reasoning, logical reasoning, and often a coding section. Duration ranges from 60 to 120 minutes depending on the company.
4. Group discussion (GD) — Not all companies run this. Those that do use it to screen communication, listening, and the ability to hold a position without shouting everyone else down.
5. Technical interview — One or two rounds. Covers branch fundamentals, data structures and algorithms, and your resume projects.
6. HR interview — Behavioural questions, compensation discussion, and offer confirmation.

Companies shortlist after each stage. Not every candidate goes through all six steps. The ones who reach the HR round have already cleared three filters. By that point, every person still in the room is reasonably capable. Communication and self-awareness then decide the final cut.

One practical note on logistics: placement days often run in parallel across departments and sometimes across multiple companies. Your college’s placement cell coordinates this, but gaps in communication are common. Confirm your venue and time slot the day before. Don’t assume the room is where it was last semester.

The week before: round-specific preparation

Aptitude test

The single most useful thing you can do is identify which aptitude platform the company uses, then practice that format specifically. TCS NQT, AMCAT, CoCubes, Mettl, HirePro, and proprietary tests each have different section weightings, question types, and time limits. Practicing a generic aptitude set when the company uses TCS NQT is solving for the wrong exam.

Once you know the format:

• Do 20 to 30 timed questions daily in each section where you’re weak, for at least 5 days before the drive.
• Prioritise accuracy over speed in the first two days, then add time pressure from day three onward.
• For coding sections: practice basic loops, strings, and math problems in Python or C++ on HackerRank or LeetCode Easy. Most campus-drive coding rounds are not DSA-hard.

For critical reasoning questions, the key is pattern recognition: once you understand the logical structure of argument-based questions, your accuracy on them improves faster than on quantitative sections.

Group discussion

GD rounds favour candidates who listen as much as they speak. The common mistake is treating a GD like a debate, where the goal is to “win” by talking the most. Interviewers are watching for something different:

• Making a clear, concise point in under 90 seconds.
• Acknowledging what a previous speaker said before building on it or disagreeing.
• Staying calm when interrupted, and re-entering the conversation without aggression.

Spend a few minutes each day reading the editorial page of The Hindu or Economic Times. You won’t always get a current-events topic, but the habit of structured argumentation is what transfers.

Technical interview

Know your projects well enough to explain them without notes. If you built something for a lab assignment but can’t describe the architecture, the logic flow, or what you would change: remove it from your resume before the drive. Interviewers who see a candidate go blank on their own project note it immediately.

Revise your strongest 3 to 4 DSA topics rather than doing a shallow pass over 20. Depth on arrays, strings, and recursion handles the majority of campus-drive technical questions at IT services companies.

HR interview

Prepare 3 to 4 STAR-format answers (Situation, Task, Action, Result) for standard behavioural questions: handling a difficult team situation, a project that didn’t go as planned, and why this specific company. These don’t need to be dramatic. Interviewers want evidence of self-awareness, not proof of heroism.

On the day: logistics and mindset

Arrive early

30 to 45 minutes before the stated start time is the minimum. Document verification queues at large drives can run longer than students expect. Being in the room early also gives you a few minutes to settle before the aptitude test starts, which matters more than most students admit.

Documents to carry

Prepare this the evening before:

• 8 to 10 printed copies of your updated resume (not last year’s version)
• College ID card
• Government-issued photo ID (Aadhaar, PAN, or passport)
• 10th and 12th marksheets: originals plus 2 photocopies each
• All semester marksheets: originals plus 2 photocopies each
• 4 recent passport-sized photographs (formal)
• Any internship certificates or offer letters

If you’re not sure whether a specific document is needed, carry it anyway. Running back to your hostel or home mid-drive is not an option.

Between rounds

Most students spend the waiting periods between rounds on their phones. A better use: review the 3 to 4 DSA topics you prepared, check what the company announced in the last quarter, and drink water. Drives are physically tiring, and candidates who appear flat in the HR round often got there because they skipped lunch or didn’t rest between the aptitude test and the interview.

Managing nervousness

A small amount of anxiety is useful. It sharpens attention. What hurts performance is trying to suppress it. When you feel nervous before an interview, acknowledge it directly to yourself, take two slow breaths, and focus on the first question only. Every subsequent question gets easier from there.

What interviewers are actually checking

Most campus interviewers are not looking for perfection. They’re looking for:

• Clarity of thought: Can you work through a problem you haven’t seen before, out loud, in a logical sequence?
• Honesty about gaps: “I don’t know, but here’s how I’d approach finding out” is a stronger answer than a confident wrong one.
• Project ownership: If you built it, you should be able to explain it. If you worked in a team, know your specific contribution cold.
• Communication: Not fluency, but clarity. A candidate who speaks with an accent but explains their reasoning clearly will outperform a fluent speaker who rambles.

The campus-to-corporate transition involves a real shift in expectations, and the interview is the first test of it. Interviewers are not just screening for technical skill; they’re checking whether you can communicate a problem and a solution to someone who wasn’t in the room when you wrote the code.

One pattern interviewers consistently mention: candidates who go wrong mid-explanation, notice the error, and self-correct out loud often rank higher than candidates who give the correct answer by rote. The former shows how you think. The latter shows you memorised something.

AI skills in campus hiring: what’s changed in 2026

This is worth addressing directly because it’s a specific, measurable shift that affects what technical rounds test from 2026 onward.

In FY26, AI-skilled graduates made up 60% of TCS’s fresher hires, up from 10 to 15% three years prior. That number comes from TCS CHRO Sudeep Kunnumal at the AI Impact Summit in March 2026. The pattern is not TCS-specific. Other large IT services companies are making similar adjustments to what they screen for in technical rounds.

What this means practically: you don’t need to be an ML engineer to pass a campus technical interview. You do need to know what a large language model is, how API-based AI tools work, and ideally have built something with one. Candidates who can say “I used an LLM API to build X in this project” are now at an advantage over candidates who can only show traditional coding skill in the same CGPA band.

If you’ve cleared your aptitude prep and you’re thinking about getting placed at a company you want, your project portfolio is the next layer to work on, and that includes at least one AI-adjacent project.

TinkerLLM is where you build that first project. For ₹299, you get live API access to multiple LLM models: enough to build a functioning micro-project (a resume screener, a GD topic summariser, a mock interview prep tool) that you can put on GitHub before your next drive. Project ownership in the interview room starts with having something real to point to.