It is 7:40 in the morning and the seminar hall is already full. Two hundred students in borrowed blazers, a printed list of eligible roll numbers taped to the door, and a placement coordinator reading out lab allocations for the online test. You cleared the eligibility cut-off by a small margin. You have practised aptitude for a month. What you have not done is think about what happens if you clear the test at 11, sit a group discussion at 2, a technical interview at 5 and an HR round at 8 in the evening, all on the same day, on two cups of canteen tea.
That is what a placement drive is: not one interview but a chain of different tests, each eliminating people for different reasons. Most students prepare hard for the first link and very little for the rest.
The short answer
Campus placement interview preparation means preparing for every stage of the drive, not just the online test. Start eight to ten weeks before placement season. Practise aptitude a little every day, commit to one programming language, cover DSA basics and the four CS fundamentals (OOP, DBMS, operating systems and computer networks), build a one-page resume where every line is something you can defend, and be able to explain your projects in detail. Then rehearse the human rounds out loud, because the technical and HR interviews are where most shortlisted students are actually lost. On the day, carry your documents, arrive early, and treat each round as a fresh start.
If you are earlier in your preparation and want the broader picture first, start with our interview preparation guide for freshers. This article is about the campus drive specifically.
How a typical placement drive runs
Every company runs its drive a little differently, and your placement cell will share the details closer to the date. In general terms, most drives follow some version of this sequence.
- Pre-placement talk. The company presents itself: what it does, the roles on offer, the locations, the bond or service agreement if there is one, and the selection process. Attend it and take notes. Interviewers sometimes ask what you know about the company, and the answer was given to you in this talk.
- Eligibility criteria. Most companies set conditions on academic scores across school and college, active backlogs, the branches allowed, and sometimes gaps in education. The placement cell filters the list before the test. Know your own numbers exactly, including how your college converts CGPA to percentage.
- Online assessment. Usually aptitude (quantitative), logical reasoning and verbal ability, often with a coding section and sometimes a short technical MCQ section on programming and CS basics. Some tests have sectional cut-offs, so a strong score in one section cannot rescue a weak one in another.
- Group discussion. Used by some companies, not all. A group of eight to twelve students discusses a topic for fifteen to twenty minutes while evaluators watch.
- Technical interview, sometimes two. Programming concepts, a coding question or two, CS fundamentals, and a long conversation about your projects.
- HR interview. Your background, your motivation, your attitude to relocation and shifts, and whether you will actually join if given an offer.
Results may come the same evening or weeks later. Do not read meaning into the wait.
Service companies and product companies run different drives
Broadly, campus recruiters in IT fall into two groups, and their drives feel different.
Large service companies typically hire in high volume. Their drives are often open to many branches, the online test carries a lot of weight, and the interviews tend to check that you have solid basics: one language, OOP concepts, simple SQL, a coding question of moderate difficulty, and clear communication. Technical and HR rounds are sometimes combined into one conversation. Because they assess so many students, consistency and clarity matter more than brilliance.
Product companies and smaller tech firms usually hire fewer people per campus, and many set stricter eligibility. The online test leans heavily on coding, often two or three problems against hidden test cases. The interviews go deeper on data structures and algorithms, and an interviewer may push on one problem for forty minutes with follow-up after follow-up. Projects are questioned closely.
These are tendencies, not rules. Some service companies run a separate, harder track for higher-paying roles, and some product companies keep their process light. Read what your placement cell circulates for each company and prepare for that drive, not for a stereotype.
A ten-week plan before placement season
This plan assumes you are still attending classes and can give it two to three hours on weekdays and more at weekends. If you have only eight weeks, compress weeks 1 and 2 into one and weeks 9 and 10 into one. The non-negotiable rule throughout: some aptitude every single day, even twenty minutes. Aptitude speed comes from repetition, not from a cram in the final week.
Weeks 1 and 2: Aptitude base and one language
Revise the quantitative topics that keep appearing: percentages, ratios, profit and loss, time and work, time and distance, averages, simple and compound interest, permutations and probability. Do logical reasoning sets (series, coding-decoding, blood relations, seating arrangements, syllogisms) and read something in English daily for the verbal section. In parallel, pick one language, Java, C++ or Python, and stay with it. Write small programs every day until loops, strings, arrays and functions feel automatic.
Weeks 3 and 4: DSA basics
Arrays, strings, hashing, sorting and binary search, then linked lists, stacks and queues. Aim for easy problems first and a few mediums by the end of week 4. We have a full topic order and a six-week coding plan in coding interview preparation for freshers, so we will not repeat it here. Follow it for this block and keep going with it alongside the weeks below.
Weeks 5 and 6: CS fundamentals
This is the block most students skip and most interviewers ask about. Cover the four subjects at the level of clear definitions plus one example each.
- OOP: the four pillars, classes and objects, overloading versus overriding, abstract classes versus interfaces. Our OOPs interview questions list is a good checklist.
- DBMS: keys, normalisation up to 3NF, joins, ACID properties, and writing basic SQL queries by hand. Use the DBMS interview questions to test yourself.
- Operating systems: processes versus threads, scheduling, deadlock and its conditions, paging and virtual memory.
- Computer networks: the OSI and TCP/IP layers, TCP versus UDP, what happens when you type a URL, DNS and HTTP basics.
Week 7: Resume and projects
Write your resume (more on that below) and then prepare to talk about every project on it for ten minutes without notes: the problem, your exact role, the stack and why you chose it, one hard bug and how you fixed it, and what you would do differently. Our guide on how to explain your project in an interview gives a structure for this.
Week 8: HR preparation and group discussion
Prepare your self-introduction, your answers on strengths, weaknesses, why this company, relocation and higher studies. Do not memorise scripts; prepare points and say them differently each time. Join or organise two or three practice group discussions with classmates.
Weeks 9 and 10: Full rehearsals and full-length tests
Take full-length online assessments under exam conditions, at least two a week. Rehearse full interviews out loud with seniors, friends, faculty or on your own recording: one technical, one HR, back to back, the way a drive runs them. Spend the rest of the time on whatever the rehearsals exposed.
Resume tips for campus placements
Your resume is the script for most of your technical interview. Interviewers have a few minutes with it before you walk in, and they ask about what they see.
- One page. As a fresher you do not have enough material to need two, and a second page usually means padding.
- Projects near the top. After education, put projects before certifications and extracurriculars. For each, one line on what it does, your role and the stack, and one line on something specific you built or solved.
- Every skill must be defensible. If you list a language, a framework or a database, assume you will be asked a question on it. If you could not answer three basic questions on it today, remove it. A short list you can defend beats a long one you cannot.
- Plain formatting. A clean single-column layout, readable fonts, no photos unless your college asks for them, no rating bars for skills.
- Accurate numbers. Write your scores exactly as they appear on your mark sheets. A mismatch found during document verification is a serious problem.
Bring several printed copies on the day, identical to the version you submitted.
Group discussion tips
Where a GD is part of the process, evaluators are usually looking for clarity, relevance, listening and the ability to move the group forward, not for the loudest voice.
- Speak early, but only with substance. Opening the discussion helps if you can frame the topic well; it hurts if you open with filler.
- Make two or three strong points rather than ten weak ones. Back each with a reason or an example.
- Build on others. "Adding to what she said about cost..." shows you are listening, which evaluators notice.
- Do not interrupt or argue personally. Disagree with the point, calmly, and give your reason.
- Bring quiet members in. Asking someone who has not spoken for their view is a sign of maturity, not weakness.
- Summarise if you get the chance. A balanced thirty-second summary at the end is often remembered.
For topics, read technology and business news for a few minutes a day. You need a sensible, structured view, not expertise.
On the day
- Documents. Carry your college ID, a government photo ID, printed resumes, passport-size photos, mark sheets and any document the company or placement cell has listed, with photocopies. Keep them in one folder.
- Be early. Arrive well before the reporting time. Lab allocations change, lists get reprinted, and walking into the test hall flustered costs you marks.
- Charge everything. Phone, and laptop if the test is on your own device. Check the test link and your login the night before if the assessment is remote.
- Between rounds. Eat something, drink water, and do not spend the gap comparing answers with friends. It only adds anxiety about a round that is already over. Instead, look over your resume and project notes, because the next round will be built on them.
- Each round is a fresh start. A shaky GD does not mean your technical interview will go badly. Interviewers usually see only that you are in front of them, not how you felt an hour ago.
- In the HR round, be honest. If asked about relocation, night shifts or higher studies, give a true answer. The HR interview questions for freshers guide covers the common ones and how to approach them.
Handling rejection, and the next company next week
Placement season is long, and almost everyone is rejected by some companies. Students who end up with good offers are often not the ones who cleared the first drive; they are the ones who learned from it.
After every drive, write down within a day: which stage you were eliminated at, the questions you were asked, and where you hesitated. If it was the online test, look at which section and adjust your daily practice. If it was the technical round, find the concepts you could not explain and revise them before the next company visits. If it was the HR round, think about whether an answer came across differently from what you meant.
Then let it go. The next company may be on campus in a week, with a different process and different interviewers. Carrying the last rejection into the next test hall is the most expensive mistake of the season.
Dream company or first offer
Many students face this choice: accept the first offer, or hold out for a company they want more. There is no universally right answer, and the rules are not yours to decide.
Colleges have very different placement policies. Some allow a student to sit for only one company after receiving an offer, some allow further attempts only for higher-category roles, some apply a "one student, one offer" rule, and some have no restrictions at all. Policies can also differ for dream or super-dream categories. Check your college's policy before the season starts, ideally in writing from the placement cell, so you know what accepting or even sitting for a company commits you to.
With the rules clear, the choice becomes personal. A first offer gives security and lets you prepare for the rest of the season without pressure, if your college permits it. Holding out is a reasonable bet if you are well prepared and your policy allows it. Talk it through with people who know your situation, and decide before the offer arrives.
Putting it together
A placement drive tests aptitude, coding, fundamentals, communication and judgement, one after another, often in a single day. The students who do well are rarely the ones who prepared hardest for the online test alone. They are the ones who also rehearsed the human rounds out loud, until explaining a project or an OOP concept felt ordinary.
If you want to rehearse those rounds before your first drive, on 99interview you can take scored practice rounds with Sia, an AI interviewer who asks one question at a time and follows up on what you actually said. You choose the difficulty (Beginner, Standard or Senior) and the round length. Sia's rounds are technical; practise the HR answers with a friend or senior. When you finish you get a written breakdown. Start with the DSA track.
When you want a human read before the season, a live 40-minute Zoom interview with a working engineer is scored on the same five criteria, technical depth (35%), problem solving (25%), communication (20%), behavioural (12%) and code quality (8%), and comes with a numbered certificate.