Getting everything ready for you…

Loading courses, problems and your progress. This takes just a moment.

0s

Guides › Placements

Campus Placement Process Explained: From Registration to Offer Letter

Every stage of campus placements — eligibility, PPT, online test, group discussion, technical and HR interviews, offer letters and dream-company rules.

If this is your first placement season, the process can feel confusing: pre-placement talks, online tests, group discussions, technical rounds, HR, offer letters, "dream" rules… This guide walks through every stage from registration to joining, and what to do at each one.

The big picture

Register with the placement cell
   → Company announces a drive (eligibility, role, package)
   → Pre-placement talk (PPT)
   → Online assessment (aptitude / coding / technical)
   → (sometimes) Group discussion
   → Technical interview(s)
   → HR interview
   → Results → Offer letter → Onboarding / joining

Not every company has every step, but almost all follow this order.

1. Before the season starts

2. The drive announcement

Each company shares:

Apply only if you'd actually join — backing out after selection can get you blocked by the placement cell.

3. Pre-placement talk (PPT)

The company explains its work, roles and process. Attend it: you learn what the interviewers value, and asking one good question is noticed. Note the names of the teams and technologies they mention — use them in your HR answer to "Why do you want to join us?".

4. Online assessment

Usually some mix of:

Part Service companies (TCS, Infosys, Wipro…) Product companies
Aptitude Large part of the score Sometimes none
Coding 1–3 Easy/Medium problems 2–4 Medium/Hard problems
Technical MCQs OS, DBMS, networks, OOP, output prediction CS fundamentals, sometimes
English / essay Common Rare

Preparation:

Online tests are usually proctored: webcam on, no switching tabs, quiet room. Test your system a day before.

5. Group discussion (some companies)

8–12 students discuss a topic for 10–15 minutes. Evaluators look for clear points, listening and leadership — not the loudest voice.

6. Technical interview

One or more rounds, 20–60 minutes each. Typical content:

Area Examples
Introduction 60–90 second summary of you
Projects Architecture, your role, a bug you fixed, why that tech
Coding 1–2 problems on paper/editor; explain your approach first
CS fundamentals OOP, DBMS & SQL, OS, networks
Your main language Java/C++/Python specifics

Prepare with interview questions, the new detailed notes (OOP, DBMS, OS, networks) and the topic guides — Java, OOP, DBMS, OS, SQL.

How to behave in a coding question:

  1. Repeat the problem and ask about constraints.
  2. Say a brute-force idea, then improve it.
  3. Write clean code while talking.
  4. Test it with a small example and an edge case.

Practise this with the AI mock interview and a few Code Battles for speed under pressure.

7. HR interview

Checks attitude, communication and fit: tell me about yourself, strengths and weaknesses, why this company, relocation, shifts, bond, higher studies. See 20 HR interview questions. Be honest — HR is good at spotting rehearsed answers.

8. Results and the offer letter

9. Before joining

If you don't get placed in the first few drives

It's very common. After each rejection:

  1. Write down what went wrong (aptitude cut-off? coding? nerves in the interview?).
  2. Fix that one thing for the next drive.
  3. Keep applying off campus — see how to get your first internship.

The process rewards preparation and consistency. Start early, prepare each round deliberately, and treat every drive as practice for the next one.

More guides