Skip to content

Placements · Aptitude · Study plan

Campus Placement Preparation: A 6-Week Plan

Most placement drives test the same five areas in the same order. This guide breaks them down and gives you a six-week plan, a daily schedule and a way to learn from every mock test.

By the TestLab team · · 10 min read

Campus placement season compresses months of hiring into a few weeks. One company’s drive can move from an online test to a technical interview to an HR round in two days, and the next drive starts on Monday. Students who do well are rarely the ones who studied the most hours. They are the ones who knew what each round checks, practised under the same conditions, and fixed their weak spots early instead of re-reading their strong ones.

This guide covers what a typical placement process looks like, what each round actually tests, and a six-week plan that fits around classes. It assumes you have basic programming knowledge and roughly two to three hours a day.

What a typical placement process looks like

Every company runs its own process, and patterns change from year to year, so always read the current pattern for the company you are applying to. That said, most service and product companies that hire freshers in India build their process from the same blocks:

  1. Online assessment. A timed test, usually 60 to 120 minutes, with sections for quantitative aptitude, logical reasoning and verbal ability. Many companies add a technical MCQ section and one to three coding problems.

  2. Technical interview. Questions on your projects, one or two programming languages, data structures, and core subjects: operating systems, DBMS, computer networks and object-oriented programming.

  3. HR or managerial interview. Your background, why this company, relocation and shifts, situational questions, and how you talk about your own work.

Some drives add a group discussion, a written communication test, or a second coding round. The important point is that the online assessment is the filter with the largest drop-off. Most applicants leave the process at that stage, so it deserves a large share of your time even though it feels less “serious” than the interviews.

What each section really tests

Quantitative aptitude

Placement aptitude is school mathematics under time pressure. The topics are predictable:

  • Percentages, profit and loss, simple and compound interest

  • Ratio and proportion, averages, mixtures and alligation

  • Time and work, pipes and cisterns, time, speed and distance (including trains and boats)

  • Number system: divisibility, remainders, HCF and LCM

  • Permutations, combinations and probability

  • Data interpretation: tables, bar charts and pie charts

The difficulty is not the concepts. It is doing 20 questions in 25 minutes without losing marks to arithmetic slips. That is why aptitude rewards daily practice more than any other section. You can understand time and work in an evening, but you only get fast at it after a few hundred problems.

A useful habit is to learn the percentage-to-fraction table by heart (12.5% = 1/8, 16.67% = 1/6, 37.5% = 3/8, and so on). A large share of percentage, profit and interest questions become one-line calculations once those fractions are automatic.

You can drill these topics in the quantitative aptitude practice test, which gives instant feedback and an explanation for every answer.

Logical reasoning

Reasoning sections usually include seating arrangements, blood relations, coding-decoding, number and letter series, syllogisms, direction sense and puzzles built on a grid of conditions. These questions are slow the first time and fast the tenth time, because each type has a standard way to lay out the information. For arrangements and puzzles, always draw the grid before reading the questions. Students who try to hold five conditions in their head make most of their reasoning mistakes there.

Verbal ability

Reading comprehension, sentence correction, fill in the blanks, para-jumbles and vocabulary in context. Verbal is the section where steady reading pays off more than cramming. Reading one long-form article a day (an editorial, a technology essay) for six weeks improves comprehension speed more than memorising word lists. For grammar, focus on the errors tests actually use: subject-verb agreement, tense consistency, prepositions, articles and parallel structure.

Technical MCQs

When a test has a technical section, it draws on the same four core subjects the interviews use. Typical questions:

  • Operating systems: process vs thread, scheduling algorithms (FCFS, SJF, round robin), deadlock conditions, paging and page replacement, semaphores and mutexes.

  • DBMS: keys, normalization up to BCNF, joins, ACID properties, transactions and isolation, indexing.

  • Computer networks: the OSI and TCP/IP models, TCP vs UDP, IP addressing and subnetting, DNS, HTTP and common port numbers.

  • Programming and OOP: output-prediction questions in C, C++, Java or Python, pointers, recursion, and the four OOP principles.

These are fact-heavy, so they suit spaced practice: short sessions spread over weeks rather than one long session the night before. TestLab has free practice tests for operating systems, database management systems, TCP/IP and data structures and algorithms.

Coding

Fresher coding rounds mostly test whether you can turn a clear problem statement into working code within the time limit. The common patterns are arrays and strings, hashing (counting frequencies, finding pairs), two pointers, sorting with a custom key, basic recursion, stacks and queues, and simple dynamic programming. You do not need competitive-programming depth for most drives. You need to solve easy and medium problems reliably, handle edge cases (empty input, one element, duplicates, very large values), and know the time complexity of what you wrote.

Pick one language and stay with it for the whole season. Switching languages between drives costs you the standard-library fluency that saves minutes in a timed round.

The six-week plan

The plan below assumes about two and a half hours on weekdays and four hours on weekends. Adjust the split if you already know which sections are your weakest. The rule of thumb is to give your weakest section the most time but never drop a section completely, because every section has a cut-off.

Week 1: Baseline and foundations

  • Take one full-length mock test on day one, before you study anything. It feels uncomfortable, but it is the only honest way to find out where you stand.

  • Score each section separately and note your accuracy and the time you spent per question.

  • Start the aptitude basics: percentages, ratios, averages, number system.

  • Revise one core subject (start with DBMS or OS, whichever is weaker) at the level of definitions and diagrams.

  • Solve two easy coding problems a day in your chosen language.

Week 2: Aptitude depth and reasoning patterns

  • Aptitude: time and work, time-speed-distance, interest, profit and loss. Do timed sets of 15 questions.

  • Reasoning: arrangements, blood relations, coding-decoding. Learn one layout per question type.

  • Core subject: finish the first subject, start the second.

  • Coding: arrays, strings and hashing. Move from two easy problems to one easy and one medium.

Week 3: Fill the gaps

  • Aptitude: permutations, combinations, probability and data interpretation.

  • Verbal: start daily reading, and one sentence-correction set a day.

  • Core subjects: networks, then OOP. By the end of this week you should have touched all four once.

  • Coding: two pointers, sorting and stacks.

  • Weekend: a second full mock test. Compare section by section with week 1.

Week 4: Speed

The goal this week is to move from “I can solve it” to “I can solve it in time”.

  • Do every aptitude and reasoning set with a timer, at about one minute per question.

  • Learn to skip. In a timed section, a question you cannot start within 20 seconds should usually be marked and left for the end.

  • Core subjects: switch from reading to answering MCQs. Answering questions shows you what you don’t know far better than re-reading notes does.

  • Coding: one medium problem a day under a 30-minute limit.

Week 5: Interviews

  • Write a one-page summary of each project: the problem, your role, the stack, one hard bug you fixed, and what you would do differently. Interviewers ask about projects more than anything else.

  • Prepare clear spoken answers to the classic core-subject questions: process vs thread, what normalization is and why we do it, TCP vs UDP, what happens when you type a URL into a browser, and the four pillars of OOP with an example of each.

  • Practise answering out loud. Explaining a concept in a sentence or two is a different skill from recognising the right option in an MCQ.

  • Keep one timed aptitude set a day so your speed does not fade.

Week 6: Mocks and review

  • Take three full mocks, spaced two days apart, at the same time of day as the real test.

  • Spend more time reviewing each mock than taking it (see the error log below).

  • Revise from your error log and your notes, not from new material. Starting a brand new topic in the last week rarely pays off.

  • Prepare your HR answers: a two-minute introduction, why this company, your strengths with evidence, and one failure you learned from.

A daily schedule that fits around classes

Here is a weekday template for about two and a half hours:

Time Block What to do
30 min Aptitude One timed set of 15 to 20 questions on the week’s topic
20 min Reasoning or verbal Alternate days: one reasoning set, one verbal set
40 min Core subject Read one topic, then answer 20 to 30 MCQs on it
45 min Coding One or two problems, then read one better solution
15 min Error log Write down every mistake from today and why it happened

Two short blocks of 20 to 30 minutes work better than one long block for aptitude. Accuracy drops noticeably after about 40 minutes of continuous calculation, and the purpose of practice is to build accurate habits, not to practise being tired.

Mock tests: how to actually learn from them

Most students take mocks and only look at the score. The score tells you very little. What helps is the review:

  1. Re-attempt every wrong question without a timer. If you get it right untimed, the problem was speed or a careless slip. If you still get it wrong, the problem is the concept.

  2. Classify each mistake. Use four labels: concept (did not know the method), careless (knew it, slipped), time (ran out) and misread (answered a different question than the one asked).

  3. Look at the questions you got right slowly. A question you solved in three minutes is a question you will skip in a real test. Learn the faster method.

  4. Check your section order. Many tests let you move between sections. Start with the section where your accuracy is highest, to bank marks early.

The error log

Keep one running document, a notebook or a spreadsheet with these columns: date, section, topic, the question (or a short description), the mistake type, and the fix in one line. For example: “Compound interest, half-yearly: forgot to halve the rate and double the periods.” Review the log every Sunday. After three or four weeks you will see that most of your lost marks come from a small number of repeated mistakes, and those are the cheapest marks you can win back.

Common mistakes that cost offers

  • Studying only what feels productive. Re-solving topics you are already good at feels like progress. It isn’t.

  • Ignoring negative marking. If a test has negative marking, a blind guess has an expected value below zero when the penalty is high. Check the rules before every test.

  • Memorising answers without understanding them. Interviewers follow up. “Why is BCNF stricter than 3NF?” is a common follow-up to “What is 3NF?”, and a memorised definition has no answer for it.

  • Overselling projects. If your résumé says “built a scalable microservice architecture”, expect questions about scaling. Describe what you actually did.

  • Skipping the HR round preparation. Candidates who clear every technical round still lose offers in HR by being vague about relocation, shifts or why they want the job.

How TestLab fits in

TestLab’s MCQ practice tests are free. You can start answering easy questions without an account. Signing in saves your progress and unlocks medium and hard questions as your accuracy grows. Every question shows an explanation after you answer, which is exactly what you need for the error-log review above.

For the interview stage, the interview questions section has technical questions with a short answer you can say in an interview and a full answer for depth. The interview plan turns your interview date into a day-by-day schedule, and the daily review brings back the questions you read earlier, spaced out so they stay in memory. You can read a few full answers free; full access, the plan and the review are part of the paid interview plan.

Six weeks is enough time to make a real difference if you spend it on your weak sections, practise under time pressure, and learn from every mistake. Start with the baseline mock today.

Share this guide