How to prepare for campus placements
Campus placements reward students who know what each round tests and have practised it under real conditions. This guide walks through a typical process, round by round, and what to work on for each.
Updated
How a typical placement process runs
Every company runs its drive a little differently, so always read the drive notice from your placement office. Most follow a pattern close to this:
- Eligibility. A CGPA or percentage cut-off, eligible branches and batch, and often a rule about active backlogs. If you don't meet it, you can't sit the drive, however well you have prepared.
- Pre-placement talk. The company explains the role, location, package and any service agreement or bond. Take notes: these answers matter later.
- Online assessment. Aptitude, logical reasoning and verbal ability, plus coding questions for most software roles.
- Group discussion, in some drives.
- Technical interview, one or more rounds.
- HR interview, then the offer.
Start with the timeline, not the syllabus
Ask your placement office when the season starts and which companies visited last year. Then work backwards. Coding and core subjects take the longest to build, so start those first; aptitude improves quickly with daily timed practice; interview skills need the last few weeks of regular mock interviews.
Aptitude and reasoning
The usual topics are percentages, ratios, profit and loss, time and work, time, speed and distance, permutations and probability; series, coding-decoding, seating arrangements, blood relations and syllogisms; and reading comprehension and sentence correction. Practise in timed sets rather than one question at a time, and check whether a test has negative marking before you guess.
Technical rounds
For software roles, pick one language and know it well. Cover the data structures interviewers ask about most often (arrays, strings, hashing, linked lists, stacks and queues, trees, recursion and sorting), then DBMS (SQL joins, keys, normalisation), operating systems (processes and threads, scheduling, deadlock), computer networks basics and object-oriented programming.
For core engineering roles, revise the fundamentals of your branch and the subjects the job description names. In every case, expect questions on anything you have written on your resume. If a project is listed, be ready to explain why you built it the way you did and what you would change.
Group discussions
Evaluators look for clear thinking and how you work with others, not who speaks most. Open with a structure if you can, back points with facts you are sure of, bring quieter members in, and summarise near the end. Never invent numbers to sound convincing.
The HR interview
Prepare a two-minute answer to "Tell me about yourself": who you are, what you have built or done, and why this role. Have one honest example ready for strengths, a weakness you are working on, a conflict and a failure. Answer questions about relocation, shifts or a service bond truthfully, and read the bond terms before you apply rather than after you are selected.
Practise out loud
Knowing an answer and saying it clearly under pressure are different skills. Ask seniors, friends or your placement cell for mock interviews. On ApplyX, Ada, our AI interviewer, runs spoken mock interviews (behavioural, technical theory or a mix) and gives you a report afterwards. The free plan includes one, so you can try it before your first drive.
Keep a placement tracker
Keep a simple sheet of every company: date, role, package, eligibility, rounds cleared and what you were asked. Patterns show up quickly. Placements aren't the only route either: keep an eye on fresher jobs off campus, and see our guide to writing an ATS-friendly resume before you apply.
On the day
- Printed copies of your resume, college ID, mark sheets and any documents the notice asks for.
- For online tests at home: a charged laptop, a stable connection and the test link opened early.
- Read the notice for the reporting time and dress code.
Frequently asked questions
When should I start preparing for campus placements?
Ideally a semester or two before your college's placement season. Coding and core subjects take the longest, so start those first; aptitude and interview practice can follow in the last few months.
Do non-computer science students need to learn coding for placements?
Not for every role. Many core engineering, analyst and sales roles test aptitude and branch subjects instead. Read the job description: if it lists a programming language, prepare it.
What if I have a backlog?
Many companies require no active backlogs, and some also look at backlog history. Read each drive's eligibility, clear backlogs as early as you can, and look at off-campus roles, where criteria often differ.