Campus Placement Preparation Guide: Aptitude, Coding, Group Discussion and HR Rounds

By Preeti Verma

Campus placement season feels chaotic: tests, shortlists, group discussions and interviews, often in the same week. Students who do well are rarely the smartest in the class. They are the ones who knew what to expect and practised each round on purpose.

This guide gives you a plan. It explains how a typical campus drive is structured, what to study for each round, how to split your time over 12 weeks, and what to do in the final week. Company processes differ, so use this as a template and adjust it using the official process of each company that visits your campus.

How a campus drive usually works

Most drives follow the same shape, although the names and order change:

  1. Pre-placement talk and registration: the company explains the role, eligibility and process.
  2. Online assessment: aptitude, reasoning, verbal and often coding or pseudocode. This is the biggest filter.
  3. Group discussion (sometimes): a few companies use it to test communication and teamwork.
  4. Technical interview: fundamentals, projects and sometimes a coding problem.
  5. HR interview: communication, attitude and fit.
  6. Offer and documents.

Most students are eliminated at the online assessment, so that is where the preparation should start.

Round 1: aptitude and reasoning

Aptitude tests reward speed and accuracy, and both come only from practice. The usual sections are:

  • Quantitative aptitude: percentages, profit and loss, ratio and proportion, time and work, time speed and distance, simple and compound interest, averages, number systems, permutations and probability.
  • Logical reasoning: number and letter series, coding and decoding, blood relations, directions, seating arrangement, syllogisms.
  • Verbal ability: reading comprehension, grammar, sentence correction, synonyms and antonyms, para jumbles.

How to prepare:

  1. Learn the formulas once. Write them on one page. For example: Profit % = (Profit / Cost price) x 100, and Speed = Distance / Time.
  2. Practise by topic first, then in mixed timed sets. Topic practice builds skill, and mixed sets build exam stamina.
  3. Track your accuracy and time per question. If a question takes more than two minutes, skip it and come back.
  4. Do not guess blindly. Check whether the test has negative marking. Some do not, and knowing that changes your strategy.
  5. Take a full mock test every week in test conditions.

A useful target for most online tests is 60 to 70 percent attempted with high accuracy, not 100 percent attempted with many mistakes.

Round 1b: coding and pseudocode

Companies test coding in two ways. Pseudocode questions ask you to trace logic and predict the output. Coding questions ask you to write a working solution.

For pseudocode, practise by tracing code by hand with a table of variable values after each step. Many marks are lost to careless tracing in loops.

x = 5, y = 0
while x > 0:
    y = y + x
    x = x - 2
print y

Trace: x=5, y=5; x=3, y=8; x=1, y=9; x=-1, stop. Output: 9. Always write the table.

For coding, build a base with arrays, strings, loops, hash maps and sorting. Our top 50 coding questions for freshers is a good starting list, and the DSA patterns guide is the next step up.

Round 2: group discussion

A group discussion (GD) tests how you communicate with others under time pressure. You are not being asked to win. You are being watched for clarity, listening and teamwork.

A simple structure that works:

  1. Start with a short, clear point. If you can, open with a definition or a fact. Starting is good only when you have something useful to say.
  2. Give two or three points, each with one example or number.
  3. Respond to others by name. "I agree with Priya's point on costs, and I would add..." shows you listen.
  4. Bring the group back if the discussion drifts.
  5. Close with a short summary if the moderator allows it.

What to avoid: interrupting, shouting, repeating the same point, going off-topic, and staying silent. A calm, relevant contribution every few minutes beats constant noise.

Practise with five or six friends. Pick topics from current affairs, technology and social issues, set a ten-minute timer, and give each other feedback.

Round 3: technical interview

For the technical round, prepare in three layers:

  1. Fundamentals: your main language, OOP, SQL and DBMS, operating system basics and basic networking. See our technical interview questions for freshers.
  2. Projects: be able to explain every line of your resume. Know the problem, the design, the technology choices and one bug you fixed.
  3. A small coding problem: reversing, searching, counting and basic data structures.

If you do not know an answer, say what you do know, then say how you would find out. That works better than a confident guess.

Round 4: HR interview

Prepare short, structured answers for the common questions: tell me about yourself, strengths and weaknesses, why this company, where do you see yourself, and your questions for them. We cover all of them with sample answers in HR interview questions and answers for freshers.

Your resume for campus drives

Recruiters spend seconds on a fresher resume, so keep it to one page. Include education, skills, two or three projects with what you built and the result, internships if any, and certifications that are relevant. Avoid a long objective paragraph and a photo unless the format requires it. See our fresher resume guide, and run a quick check with the free ATS resume checker, because many companies use an applicant tracking system for off-campus and referral applications.

A 12-week preparation plan

Weeks 1 to 4: build the base

  • Aptitude: learn formulas and do topic-wise practice, 45 minutes a day.
  • Coding: arrays, strings and loops, one or two problems a day.
  • Update your resume and list your projects.

Weeks 5 to 8: go deeper and mix

  • Aptitude: mixed timed sets, one full mock test a week.
  • Coding: hash maps, sorting, searching, linked lists, stacks.
  • Technical: revise OOP, SQL, DBMS and OS basics, one subject every two days.
  • Join one GD practice session a week.

Weeks 9 to 11: simulate the real thing

  • Two full aptitude plus coding mock tests a week.
  • Two mock technical interviews and two mock HR interviews. Do at least some of them spoken, because writing answers is not the same as saying them. A spoken practice tool such as the GenQuest AI mock interview works if you cannot find a partner.
  • Revise your weak areas from the mock results.

Week 12: polish and rest

  • Light revision, formula sheet, project explanations and company research.
  • Sleep. A tired candidate loses easy marks.

The last-week checklist

  • Printed or digital copies of your resume, ID and documents ready.
  • Formula sheet reviewed, not newly learned.
  • Two projects explained clearly in under two minutes each.
  • Company research done: what they do, the role and the stages.
  • Laptop, charger, internet backup and a quiet space ready for online tests.
  • A confirmed time and link for every online round.
  • An early night before each round.

Mistakes to avoid

  1. Starting only after the first company arrives. Start at least 10 to 12 weeks before.
  2. Only practising aptitude or only coding. You need both.
  3. Ignoring speaking practice. Interview rounds are spoken.
  4. Applying to one company. Apply to many drives, because each is a fresh chance.
  5. Not reading the official instructions. Missed deadlines and wrong documents cost real candidates their chances.
  6. Falling for fake offers. Genuine employers do not charge candidates fees for hiring, and official emails come from the company's own domain.

Sample aptitude questions with worked solutions

Seeing a method work is the fastest way to learn it. Here are five typical questions.

1. Percentages. A price goes up by 20 percent and then falls by 20 percent. What is the net change?

Start with 100. After the rise it is 120. A 20 percent fall takes off 24, leaving 96. The net change is a fall of 4 percent. The lesson: equal percentage rises and falls do not cancel out, because the second change applies to a different base.

2. Time and work. A can finish a job in 10 days and B in 15 days. How long do they take together?

A does 1/10 of the job a day and B does 1/15. Together that is 1/10 + 1/15 = 3/30 + 2/30 = 5/30 = 1/6 per day, so the job takes 6 days.

3. Speed and distance. A train 150 metres long passes a pole in 15 seconds. What is its speed in km/h?

Passing a pole means covering its own length. Speed = 150 / 15 = 10 m/s. To convert to km/h, multiply by 18/5: 10 x 3.6 = 36 km/h.

4. Ratio. Rs 7,000 is shared between two people in the ratio 3 to 4. How much does each get?

The total ratio is 3 + 4 = 7 parts, so one part is 7,000 / 7 = 1,000. The shares are 3,000 and 4,000.

5. Number series. What comes next: 2, 6, 12, 20, 30, ?

The differences are 4, 6, 8, 10, so the next difference is 12, and the answer is 30 + 12 = 42.

Notice that each solution takes under a minute once you know the idea. Speed comes from recognising the pattern, not from calculating faster.

Managing the clock in an online test

  • Scan the section first and answer the questions you find easy.
  • Set a limit per question, about 60 to 90 seconds for aptitude, and move on when you pass it.
  • Mark and return to the skipped ones with whatever time is left.
  • Do not leave the last two minutes empty. If there is no negative marking, answer everything.
  • Check the instructions on navigation. Some tests do not let you go back.

A calm, steady pace beats a panicked sprint, and it is something you can practise in mock tests.

Frequently asked questions

Is CGPA more important than skills?

CGPA often decides eligibility, because many companies set a minimum. After that, your test and interview performance decide the outcome. Skills win once you are eligible.

What if I do not get placed in my campus?

Use off-campus drives, referrals and company career pages. The preparation you did still counts. See our guide to your first software developer job without experience.

How do I improve my English quickly?

Read a little daily, speak out loud, and practise answers to common questions. Short, clear sentences are better than complicated ones.

Should I prepare for product companies too?

If you want product companies, start data structures and algorithms earlier and go deeper. The basics in this guide still apply.

The takeaway

Campus placements are a process you can prepare for. Start early, treat the online assessment as the biggest filter, practise speaking, and check each company's official process. A steady 12 weeks beats a panicked two.