A campus placement drive in India almost always runs in the same order: registration and eligibility screening, a pre-placement talk, an online aptitude or coding assessment, sometimes a group discussion, then one or two technical interviews and an HR round on the same day. The whole thing is usually compressed into a single day on campus, and each round is elimination based, so a weak aptitude score ends your drive before anyone reads your resume. The other half of campus placement is policy rather than performance: CGPA cutoffs, active backlog rules, dream company slots and the one offer rule your placement cell enforces. This guide walks through every round, what each one is actually testing, what to prepare for it, and how the placement policy quietly decides which companies you are even allowed to sit for. Read your own cell's rules early, because they are not negotiable later.
Eligibility and registration: the round before the rounds
Before any interview happens, the company sends criteria to the placement cell and the cell filters the batch. The usual filters are a minimum CGPA or percentage across tenth, twelfth and graduation, no active backlogs at the time of the drive, and sometimes a cap on total education gap years. Branch eligibility is set here too, which is why circuit branches often see more software drives than core branches.
Two practical consequences. First, clear pending backlogs before the placement season starts, because an active backlog on drive day removes you from companies you would otherwise have cleared. Second, get your documents ready early: marksheets from tenth onward, an updated resume in the format your cell demands, and identity documents. Every year people miss drives over a missing marksheet, and the cell will not make an exception at nine in the morning.
- Typical filters: CGPA cutoff, no active backlogs, capped gap years, eligible branches.
- Some companies also apply a percentage cutoff on tenth and twelfth separately.
- Registration is usually through a portal with a hard deadline, often days before the drive.
- Resume format is frequently fixed by the placement cell, so do not submit your own design.
- Keep scanned marksheets, ID proof and a passport photo ready in one folder.
- Confirm whether the drive is on campus, at a pooled campus, or virtual.
The pre-placement talk
The pre-placement talk is the company presenting itself: business lines, training programme, locations, the package structure and often the service agreement. Attendance is usually mandatory and sometimes tracked. Students treat it as a formality and then, three hours later, cannot answer why do you want to join our company. Everything you need for that answer is in the talk. Sit near the front, stay off your phone, and write down what is said rather than trusting your memory three hours later in the interview room.
Take notes on four things: what the company actually does for its clients, what the training period looks like, which locations and roles freshers get, and the exact package breakup. Then ask one specific question at the end if there is time. Recruiters do notice, and it costs you nothing. A good question sounds like: how are freshers allocated to projects after training, and can we express a technology preference.
- Note the business lines and at least one client domain you can mention later.
- Note the training duration, location and whether there is an exit test.
- Note the package: fixed, variable, joining bonus, and any service agreement.
- Note the base locations offered, since relocation will be asked in the HR round.
- Write one sentence you can reuse as your why this company answer.
- Ask a question that is about the work, not about leave or salary.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksThe online assessment: aptitude, verbal and coding
This is where most of the batch is eliminated. A typical assessment has quantitative aptitude, logical reasoning, verbal ability, and for software roles a coding section with one to three problems. Many are sectionally timed, which means you cannot borrow time from an easy section for a hard one, and several have sectional cutoffs, so scoring brilliantly in coding does not rescue a failed verbal section.
Preparation is unglamorous but reliable. Quant is a fixed syllabus: percentages, ratio and proportion, time speed distance, time and work, profit and loss, permutations, probability, number system. Logical reasoning is pattern practice. Verbal is grammar, vocabulary and reading comprehension. The single most useful habit is doing timed full length mocks rather than untimed topic practice, because the real constraint is the clock and not the difficulty.
- Expect sectional timers and, often, sectional cutoffs.
- Practise a fixed quant syllabus rather than random questions.
- For coding sections, get comfortable reading input from standard input in your language.
- Learn to skip. One stubborn question can cost you five easy ones.
- Some assessments are proctored with webcam and screen monitoring, so read the instructions.
- Check whether there is negative marking before you start guessing.
The group discussion round
Not every company runs a group discussion, but many mass recruiters still do, usually with eight to twelve students and a topic given on the spot. Topics are typically abstract, current affairs, or a business case. The panel is scoring participation, clarity, whether you listen, and whether you can move the group forward. It is not scoring who talked loudest, though every year several students believe otherwise.
The dependable strategy is to enter early with a structured point, then contribute two or three more times with something that builds on what others said. Sample opener: I would like to frame this in two parts, the economic side and the social side, and I will start with the economic side. If the discussion turns into a shouting match, the highest scoring move available is often to bring it back: we have three points on the table already, can we settle one before adding more.
- Speak within the first ninety seconds if you can, since it is harder to enter later.
- Structure beats volume: name two or three angles, then take one.
- Reference other speakers by what they said, since listening is being scored.
- Do not interrupt, and do not let anyone monopolise without a polite redirect.
- Carry one or two facts, but never invent a statistic to sound authoritative.
- If you get the summary, cover both sides and end with a conclusion, not a list.
Technical interview
The campus technical round is usually twenty to forty minutes and centres on your resume, your final year project and core subjects. Interviewers move fast across subjects rather than going deep on one. Expect OOP, DBMS, one programming language, basic data structures, and often a small pen and paper coding problem such as reversing a string or finding duplicates in an array.
The single biggest scoring lever is your project. Be able to explain what it does, why you chose the stack, what part you personally built, and what broke. If you list a technology on your resume, expect two questions on it, so cut anything you only touched in a workshop. When you do not know something, say so and reason out loud toward the nearest thing you do know. That scores better than a confident wrong answer, which is the fastest way to invite a harder follow up.
- Know your project end to end, including the parts teammates wrote.
- Prepare OOP with your own examples rather than textbook definitions.
- DBMS: joins, keys, normalisation, indexes, ACID properties.
- Be able to write simple code without an IDE and state its time complexity.
- Carry printed copies of your resume and a pen, since panels often work on paper.
- Answer the point first, then explain, rather than narrating your way to a conclusion.
HR round, offers and placement policy
The campus HR round is short and mostly checks commitment. Expect relocation anywhere in India, rotational or night shifts, willingness to sign a service agreement, comfort with the standard package, active backlogs, and whether you are sitting for other companies. Answer plainly, and only say yes to relocation and shifts if you mean it, because the posting arrives regardless of what you hoped for.
Then there is policy, which decides more outcomes than most students realise. Many cells operate a one offer rule that removes you from further drives once you clear a company, sometimes with an exception for a dream company slot above a stated package threshold. Companies are often slotted by day, with the highest paying visiting first. Read the rules in the first week of the season and plan which drives to sit for, because opting out of an early drive to chase a later one is a bet, and it is one you can only make knowingly.
- One offer rule: clearing one company commonly ends your eligibility for the rest.
- Dream offer or dream company slots may allow one further attempt above a package threshold.
- Day 1, day 2 slotting usually puts the higher packages earliest in the season.
- Some cells require you to attend every drive you registered for or face a penalty.
- Offer letters may arrive weeks later, and joining dates can be months after that.
- Keep applying off campus in parallel unless your cell explicitly forbids it.
Frequently asked questions
When do campus placements usually start?
For most Indian engineering colleges the main season opens in the final year, commonly from around July to September, with drives continuing through the academic year. Exact timing varies by institution and by company. Ask your placement cell for the season calendar early, because eligibility documents, resume formats and registration deadlines all land before the first drive.
Can I sit for more companies after getting placed?
That depends entirely on your placement cell policy. Many colleges run a one offer rule that removes you from the pool once you clear a company, sometimes with an exception for a dream company above a stated package. Get the rule in writing at the start of the season, since students regularly discover it after they have already accepted an offer.
Do backlogs disqualify me from campus placements?
Active backlogs at the time of the drive commonly do disqualify you, since many companies state no active backlogs as an eligibility criterion. Cleared backlogs are usually acceptable, though a few companies cap the total number across your degree. Clear everything pending before the season starts, and be ready to explain the backlog in one honest sentence.
Is a group discussion still part of campus placements?
Some mass recruiters still run one, and many have replaced it with a communication assessment or a versant style spoken test in the online round. Assume it might happen. The preparation overlaps anyway: structured speaking, listening to others, and being able to take a position and defend it without dominating the conversation.
What if I am from a non circuit branch?
Mass IT recruiters commonly hire across branches, so mechanical, civil and electrical students do get placed into software roles. What you need is proof: a real project, one language you can defend, and a clear answer to why you want a software role instead of your core branch. Prepare that answer properly, because you will be asked it in every round.
Paste the actual job description; Indian postings have their own patterns. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions