Campus Placement Preparation: A 90-Day Plan

68 percent of engineering graduates in India don’t get placed through campus drives. That’s not some made-up figure I’m pulling for drama — it comes from AICTE data and various employability surveys that keep repeating the same pattern year after year. Roughly two-thirds of students who sit through placement season walk away without an offer.

Which means the students who do get placed are doing something differently. Probably not something magical or secret. Just… structured preparation, started early enough, covering the right stuff. That’s what this 90-day plan is about.

I’ve broken it into three 30-day phases. You don’t need to quit everything else in your life. You do need to show up consistently. Skipping a week in the middle is the kind of thing that compounds badly.

Phase 1: Days 1 through 30 — Foundations

Aptitude and Reasoning

Almost every company that comes to campus — IT giants like TCS, Infosys, Wipro, Cognizant, or non-tech firms like Deloitte, EY, KPMG — starts their selection with an aptitude test. Get eliminated here and nothing else matters. Your coding skills, your projects, your personality — none of it gets seen if you can’t clear the aptitude round.

The three sections you’ll face are quantitative aptitude, logical reasoning, and verbal ability. Quant covers percentages, profit and loss, time and work, time speed distance, permutations and combinations, probability, number series. Logical reasoning covers seating arrangements, blood relations, coding-decoding, syllogisms, direction sense. Verbal covers reading comprehension, sentence correction, fill in the blanks, para jumbles.

Get R.S. Aggarwal’s “Quantitative Aptitude” — it’s not glamorous, but it covers every topic you’ll encounter. For logical reasoning, the same author’s reasoning book works. Supplement with online platforms: IndiaBix and PrepInsta both have company-specific question banks that are genuinely useful.

Target: 50 aptitude problems per day. Not 50 new concepts — 50 problems. Speed matters as much as accuracy. Time yourself. If a problem takes more than 2 minutes and you’re stuck, look at the solution, understand the approach, and move to the next one. After a week, you should start noticing patterns. After three weeks, most standard problem types should feel familiar.

Verbal ability is harder to grind through practice alone. Read. Read articles, read editorials from The Hindu or Economic Times, read anything in English that’s written at a professional level. Your reading comprehension will improve as a side effect of regular reading in a way that drilling exercises alone can’t match.

Resume Preparation

Build your resume now, in week one. Not because you’re going to submit it immediately, but because the act of writing your resume exposes gaps in your profile that you still have time to fill.

One page. No fancy templates with graphics and colored sidebars — many ATS systems choke on those. Clean formatting, clear sections: Education, Technical Skills, Projects, Internships (if any), Achievements/Extracurriculars.

Every bullet point on your resume should demonstrate something measurable if possible. “Built a web application using React and Node.js that reduced manual data entry time by 40% for a local business” works. “Developed a website” does not. Numbers make things concrete. If you don’t have numbers, describe the scope or impact in specific terms.

Have your resume reviewed by a senior, a professor who’s involved in placements, or someone who’s worked in industry. Multiple eyes catch things your own eyes skip over. I’ve seen resumes with typos in the candidate’s own email address. That kind of thing is preventable.

Start Technical Foundations (Light)

Don’t dive deep into technical prep yet — that’s Phase 2. But start reviewing the basics of your core CS subjects: DBMS, Operating Systems, Computer Networks, and OOP concepts. Just reading through notes or watching summary videos for an hour daily is enough in this phase. You’re priming your memory, not mastering content.

LinkedIn and Online Presence

Set up a LinkedIn profile this month if you don’t already have one. Fill it out properly — professional photo, a headline that says more than “Student at XYZ Engineering College,” a summary that describes what you’re good at and what you’re looking for. Connect with alumni from your college who are working at companies you’d like to join. Follow those companies’ pages. A surprising number of campus recruiters check LinkedIn profiles during the screening process, and having a blank or sloppy profile creates a negative impression you won’t even know about.

If you’ve done any coding, put it on GitHub. Even small projects. It shows you actually write code outside of assignments, and some interviewers will look at it. Clean up any repos that are just forked without modification — they add noise without value.

Phase 2: Days 31 through 60 — Technical and Domain Skills

For IT and Tech Roles

This is the month where technical preparation takes center stage. If you’re targeting tech companies, here’s what you need to cover.

Data Structures and Algorithms. Arrays, linked lists, stacks, queues, trees (binary trees, BSTs), graphs, hash maps. Algorithms: sorting (know at least bubble, merge, and quick sort), searching (binary search), recursion, basic dynamic programming concepts, BFS and DFS for graph traversal. You don’t need to solve LeetCode Hard problems for campus placements (those are more for FAANG-level companies). LeetCode Easy and Medium, or the equivalent difficulty on HackerRank and GeeksforGeeks, is the right level.

Target: 3 to 5 problems daily. Write actual code, not just pseudocode. Make it compile. Test edge cases. Track which problem types give you trouble and revisit them weekly.

Core CS subjects. DBMS: normalization (up to 3NF), SQL queries (SELECT, JOIN, GROUP BY, subqueries, aggregation), ACID properties, difference between SQL and NoSQL. Operating Systems: process scheduling algorithms (FCFS, SJF, Round Robin), deadlocks (conditions, prevention), virtual memory, paging. Computer Networks: OSI model, TCP vs UDP, HTTP vs HTTPS, basic DNS understanding. OOP: four pillars (encapsulation, inheritance, polymorphism, abstraction) with real examples, not textbook definitions.

You’ll be asked about these in technical interviews. The questions aren’t usually trick questions. They’re checking whether you actually understand the concept or just memorized a definition. Being able to explain normalization using a concrete example (like a student database with redundant data) is worth more than reciting the formal definition.

Know one programming language well. Not three languages at a surface level — one language with depth. If you pick Java, know collections, exception handling, multithreading basics, JVM memory model. If Python, know data types, list comprehensions, decorators, difference between shallow and deep copy, how memory management works. If C++, know pointers, memory allocation, STL containers. Interviewers will ask language-specific questions, and “I know a little bit of everything” is not an impressive answer.

For Non-Tech Roles

If you’re targeting consulting firms (Deloitte, EY, Accenture), FMCG companies (HUL, P&G, ITC), or finance roles, your prep looks different.

Business fundamentals: understand basic financial statements (balance sheet, income statement, cash flow), know what EBITDA means, understand how supply chains work at a high level, be aware of major economic indicators (GDP, inflation, interest rates).

Current affairs: read the Economic Times or Business Standard daily. Know what’s happening with major Indian companies, government economic policies, and global events that affect Indian business. When Deloitte asks you about a recent business trend during an interview, “I don’t follow the news” is a deal-breaker.

Case studies: consulting firms love case studies. Practice the basic frameworks — profitability analysis, market entry, pricing strategy. Victor Cheng’s case interview prep materials are the standard recommendation, and they’re free online. Practice with friends. Do at least 10 mock cases before placement season.

Group Discussion Preparation

A lot of companies include GD rounds, especially for management and non-tech roles. GDs test your communication, structured thinking, ability to listen, and how you function in a group setting.

Common GD topics: Indian economic policy, technology’s impact on employment, education system reform, current business controversies, social issues. Read editorials from multiple perspectives to form nuanced opinions.

In the actual GD, here’s what gets you noticed (from what I’ve gathered from placement committee members and recruiters). Making the first or second point in the discussion gives you visibility. Referencing specific data or examples makes you sound prepared. Summarizing others’ points before adding your own shows you’re listening, not just waiting for your turn. Staying calm when someone disagrees with you shows maturity. Talking too much is as bad as not talking at all.

Practice GDs with your friends weekly during this phase. Record them and watch back. It’s cringeworthy but instructive.

One thing I’ve noticed from talking to people on placement committees: the biggest GD killer isn’t lack of knowledge. It’s aggression. Getting into a shouting match with another participant, interrupting constantly, or dismissing other people’s points — that gets you eliminated even if your arguments are technically correct. Panelists are watching for people who can disagree respectfully and bring the group toward a conclusion. That’s a workplace skill, and they’re testing for it directly.

Phase 3: Days 61 through 90 — Interview Mastery

Technical Interview Prep

At this point, your foundations should be solid. Now you’re polishing your delivery.

Your projects are going to come up in every technical interview. Know each project cold. What was the problem? What was your approach? What technologies did you use and why? What would you do differently? If you worked in a team, what was YOUR specific contribution? Interviewers can tell immediately if you actually built something versus if you copied code from YouTube and slapped your name on it. Be honest about what you did and what you learned.

Prepare to explain technical concepts simply. If an interviewer asks “What’s a deadlock?” don’t launch into the formal definition. Say something like “A deadlock is when two or more processes are each waiting for the other to release a resource, so none of them can proceed. Like two people meeting in a narrow hallway, both waiting for the other to step aside.” Clear, simple, demonstrates understanding.

Practice writing code on paper or a whiteboard. This seems old-fashioned, but many campus interview rooms don’t have computers. Writing syntactically correct code by hand is a skill you need to practice. It’s different from typing in an IDE where autocomplete catches your mistakes.

HR Interview Prep

Questions you’re almost certain to face:

“Tell me about yourself.” Keep it to 90 seconds. Name, education, key skills or interests, one notable achievement or project, what you’re looking for in your career. Not your life story. Not “I was born in Patna in 1999…”

“Why do you want to join [company]?” Do your research. Know what the company does beyond the obvious. If it’s Infosys, maybe mention their Infosys Springboard initiative or their recent work in AI. If it’s TCS, mention something about their innovation labs or global reach. Specificity signals genuine interest.

“What are your strengths and weaknesses?” Pick real ones. A strength that you can demonstrate with an example. A weakness that’s genuine but that you’re actively working on. “I’m a perfectionist” is not a real weakness answer — everyone says it and nobody believes it.

“Where do you see yourself in 5 years?” They’re checking if you’ll stick around. You don’t need to pledge your life to the company, but showing that you want to grow within the organization, take on more responsibility, and build expertise is what they want to hear.

Mock Interviews — Non-Negotiable

Do at least 10 mock interviews in this phase. With friends, with seniors who’ve been placed, through online platforms like Pramp or InterviewBit’s peer mock interview feature. Treat them seriously. Wear formal clothes. Sit at a desk. Time your responses. Get harsh feedback.

Record at least two or three of these mocks. Watching yourself on video is painful but incredibly useful. You’ll notice nervous habits (playing with a pen, saying “basically” every other sentence, not making eye contact) that you never noticed in real time.

The Week Before Placement Day

Stop cramming new material. At this point, you know what you know. Trying to learn new topics in the last week creates anxiety without adding meaningful preparation.

Instead: review your key talking points. Read through your project descriptions one more time. Go over your most-practiced aptitude problem types for confidence. Research the specific companies scheduled for your placement week — their services, their CEO, any recent news.

Practical stuff: iron and lay out your formal outfit the night before. Print 5 extra copies of your resume on good quality paper. Charge your phone and laptop. Set two alarms. Sleep for at least 7 hours. Eat a proper breakfast.

Arrive at the venue 30 minutes early. Being late to a placement drive is one of those things that shouldn’t happen but does happen to at least a few people every year because they assumed they had more time.

A Few Things Most Guides Won’t Tell You

Companies that come early in placement season tend to hire more generously. They’re filling larger batches and the competition from other companies hasn’t peaked yet. If you’re offered a role by a Day 1 or Day 2 company but were hoping to hold out for a “better” company later, think carefully. A bird in hand and all that. Many colleges also have policies where accepting an offer blocks you from sitting for subsequent companies.

Your CGPA matters more for getting past the initial filter than for the actual interview. Most companies have a cutoff — usually 6.0 to 7.0 CGPA. Below the cutoff, you can’t sit for the drive. Above the cutoff, the interview performance matters far more than whether you’re at 7.2 or 8.5. If you’re currently below common cutoffs and have time, focus on getting above the threshold in remaining semesters.

Soft skills matter more than most engineering students believe. Two candidates with identical technical skills — the one who communicates clearly, makes eye contact, asks good questions, and seems genuinely engaged will get the offer over the one who mumbles through correct technical answers. This isn’t fair necessarily, but it’s how human evaluation works.

Placement season is stressful, and comparing yourself to peers who get placed before you is natural but destructive. Everyone’s timeline is different. Someone getting placed in Company A on Day 1 says nothing about your chances with Company B on Day 5. Focus on your own preparation and your own interviews. That’s the only part you control.

Keep your phone away from WhatsApp group chats where people are broadcasting their placement results in real time. I’ve heard from multiple students that those groups were the single biggest source of anxiety during placement week. Mute them if you can’t leave them.

And if Day 1 doesn’t go well — if you get eliminated in the aptitude round or stumble in an interview — remember that placement season isn’t one day. Companies keep coming. Some of the best offers come in the second or third week when the initial frenzy has died down and there’s less competition per slot. Your preparation over 90 days wasn’t for one company. It was for all of them.

90 days. Three phases. Foundations, technical depth, interview polish. Start today, stay consistent, and you’ll walk into placement season as one of the students who’s actually ready for it.

And honestly, one thing I almost forgot to bring up — mock interviews with friends can feel awkward, but they are probably the single best thing you can do in those last few weeks before placements. I think most students skip this because it feels silly, but the ones who actually practice out loud tend to do way better when the real pressure hits. Maybe it is just me, but I have noticed that confidence in interviews comes more from repetition than from raw talent.