For students
How to prepare for campus placements: a 12-week plan for final-year students
Three months is enough to change how you do in placements, if you spend it on the things the tests actually check. A week-by-week plan.
Campus placements feel like one event, but they are a sequence of tests, each looking for something different. An online test checks aptitude and coding under time pressure. A technical interview checks whether you understand what you know. An HR round checks whether you can talk about yourself and your work. You can prepare for each of them, and twelve weeks is enough to make a real difference, if you prepare for the tests you will actually face.
This plan assumes you have a few hours a day around classes. Adjust the weeks to your timetable, but keep the order: it builds each skill before the next one leans on it.
Weeks 1 and 2: find out where you stand
Before you study anything, take a full timed practice test that mirrors a mass recruiter's pattern: quantitative aptitude, logical reasoning, verbal ability and a coding problem or two. Do it under real conditions, in one sitting, with a timer. The score matters less than the breakdown. Most students discover they are fine at one section and losing most of their marks in another.
Pick one programming language for the coding rounds and stay with it. Choose the one you already know best; the tests allow the common ones, and switching costs more than it gains.
Weeks 3 to 6: build the foundations
Spend these weeks on the weakest section from your first test, while keeping the others warm.
- Aptitude: learn the standard methods for percentages, ratios, time and work, speed and distance, and probability, then practice them against a timer, because speed is half of what is tested
- Reasoning: series, arrangements, blood relations and data interpretation reward practice more than talent
- Verbal: read something in English every day, and practice comprehension passages at test speed
- Coding: work through arrays, strings, hashing, sorting, recursion and basic trees and graphs, solving problems yourself before you look at any solution
Practice a little every day rather than a lot on weekends. Recruiter tests reward fluency, and fluency comes from repetition spread over time.
Solving a problem after reading the solution teaches you the solution. Solving it before teaches you how to solve problems.
Weeks 7 and 8: your resume and your projects
Write a one-page resume. Put your projects near the top, and for each one, say what you built, what you used, and one thing you would do differently. An interviewer will ask about everything on the page, so remove anything you cannot talk about for five minutes.
Then practice explaining your projects out loud. Most students know their project well and describe it badly. Explain the problem it solves, the hardest decision you made, and what broke along the way.
Weeks 9 and 10: timed practice and mock tests
Now shift from learning to performing. Take a full mock test every few days under test conditions, and review every question you got wrong or answered slowly. Keep a list of the mistakes you repeat; it is the most useful document you will own this season.
In the coding rounds, practice getting a working solution first and improving it second. A correct slow solution earns more than an elegant one that does not finish, and hidden test cases punish solutions that ignore edge cases such as empty input, duplicates and large values.
Weeks 11 and 12: interviews
Do at least three mock interviews, with a friend, a senior or a mock interview tool, and ask for honest feedback after each. Prepare to explain your code line by line, your projects decision by decision, and why you want the job in plain words. For the HR round, prepare short, true stories about a problem you solved, a time you worked in a team, and something you learned from a mistake.
Through all twelve weeks
- Read every drive notice carefully and apply before the deadline, only to roles you would accept
- Keep your profile, CGPA and resume up to date with the placement cell
- Sleep before test days; a tired brain loses more marks than an unprepared one
- Treat each rejection as data: note which round you fell in, and practice that round next
The short version
Find out where you stand, fix the weakest section first, practice daily against a timer, build a resume you can defend, take mock tests and review every mistake, and rehearse interviews out loud. If your college uses Assessly, the daily problems, practice tests, mock interviews and the drives board are all in the Assessly app; your placement cell can tell you how to sign in.
Was this page helpful?