Campus placement season in India is unlike anything else — hundreds of students competing for limited slots, multiple companies visiting on the same day, offers with 24-hour deadlines, and the pressure of knowing your first job will shape your trajectory for the next 3-5 years. This guide gives you a clear, realistic prep plan from the semester before placements through offer day.
At most engineering colleges, 80% of placements happen in the first 2-3 weeks of the season. Students who aren't ready by Day 1 miss the best opportunities. Preparation starts at least 6 months before.
Understanding the Placement Process
- 1Online Assessment (OA): Aptitude + coding round, sometimes on HackerRank or Cocubes. Typically 60-120 mins.
- 2Technical Interview (1-2 rounds): DSA problems, CS fundamentals (OS, DBMS, CN), and project discussions.
- 3HR Interview: Behavioral questions, 'tell me about yourself,' offer details.
- 4Group Discussion (GD): Required by some consulting firms (Deloitte, PwC, KPMG) and PSUs.
6-Month Preparation Timeline
| Month | Focus Area | Target Output |
|---|---|---|
| Month 1-2 | DSA foundations | Complete arrays, strings, linked lists, stacks, queues, trees. 40-50 Leetcode Easy/Medium. |
| Month 3 | DSA intermediate + CS subjects | Graphs, DP, backtracking. Revise OS, DBMS, CN, OOPs basics. |
| Month 4 | Project + resume | Build or polish 1-2 strong projects. Update resume with metrics and GitHub links. |
| Month 5 | Mock interviews + aptitude | Practice on Pramp, InterviewBit. Do timed aptitude tests on IndiaBix. |
| Month 6 | Company-specific prep | Research visiting companies. Practice their previous OA patterns. Mock GDs if consulting companies visit. |
What Companies Actually Test
| Company Type | Examples | Primary Test Focus |
|---|---|---|
| FAANG/Top Product | Google, Microsoft, Amazon, Atlassian | Strong DSA, problem-solving, system thinking |
| Indian Unicorns | Flipkart, Swiggy, PhonePe, CRED, Razorpay | DSA + practical coding, culture fit |
| Mid-Product | Juspay, Groww, BrowserStack, Postman | DSA + project depth, ownership mindset |
| Service Giants | TCS, Infosys, Wipro, HCL | Aptitude, basic coding, communication |
| Analytics/Consulting | Deloitte, EY, PwC, McKinsey | Case studies, GD, aptitude, communication |
Your Resume for Campus Placements
- Keep it to 1 page — always. Recruiters will discard multi-page fresher resumes.
- Put your strongest section first: if your projects are stronger than your internship, lead with projects
- For each project, mention: what you built, the tech stack, the scale or impact, and a link to the code
- Include your CGPA if it's 7.5+ (out of 10). If below 7, omit it
- List competitive programming achievements prominently: CodeChef ratings, Codeforces, LeetCode contest rankings
- Relevant coursework, technical clubs, hackathon wins — all valuable for freshers
What makes a project stand out
1. You can explain every line of code. 2. It has a real use case, not 'a todo app.' 3. It involves at least one non-trivial technical decision (why this DB, why this architecture). 4. It's deployed somewhere live — even Render or Railway's free tier. 5. The GitHub README explains what it does and how to run it.
If You Don't Get Placed on Campus
Off-campus opportunities are often better than on-campus ones. Companies like Zepto, Meesho, and dozens of Series A/B startups hire freshers off-campus year-round with better packages than what many colleges see. LinkedIn jobs, Naukri, AngelList India, and direct company careers pages are your channels. The placement season ending doesn't close the job market.