Campus Placement Preparation: A 90-Day Plan

Ninety days from now, you could be sitting in front of a recruiter from TCS, Infosys, Wipro, Deloitte, or any of the dozens of companies that come to Indian campuses every year. Ninety days. That's about 12 weekends, give or take. Three months of actual preparation time, minus the days you'll lose to college assignments, exams, and the inevitable week where you lose motivation and wonder if any of this will work.

It's enough time. I'm not going to sugarcoat it — 90 days isn't a lot, and if you spend the first 30 days "planning to start tomorrow," you'll be scrambling at the end. But if you use the time well, it's absolutely enough to go from unprepared to placement-ready. I've seen it happen dozens of times with students who started with nothing special and ended up with solid offers.

I'm not 100% sure on this, but here's the plan, broken into three phases. Each phase builds on the previous one. Don't skip ahead — the sequence matters.

Phase 1: Days 1-30 — The Foundation

Aptitude and reasoning (your daily grind)

Almost every company that recruits through campus placements starts with an aptitude test. TCS, Infosys, Wipro, Cognizant, Accenture, Deloitte, EY — they all filter through some version of quantitative aptitude, logical reasoning, and verbal ability. The test is designed to be time-pressured, which means speed matters as much as accuracy. You can know the concepts perfectly and still fail if you can't solve problems fast enough.

Get R.S. Aggarwal's Quantitative Aptitude book. Yes, it looks like it was designed in 1995. Yes, everyone recommends it because it works. Start from the basics even if you think you already know the material. Percentages, ratios, time-and-work, profit-and-loss, averages, mixtures, probability, permutations and combinations. Solve at least 50 problems a day. Not 50 new concepts — 50 problems. The first week, you'll be slow and make mistakes. By week three, your speed will have doubled. By the end of month one, you should be able to solve standard aptitude questions in 45-60 seconds each.

For logical reasoning, the same author's Verbal and Non-Verbal Reasoning book covers everything you need: coding-decoding, blood relations, direction sense, syllogisms, seating arrangements, and pattern recognition. Practice platforms like IndiaBix and PrepInsta have thousands of free problems organized by topic. Do 20-30 reasoning problems daily alongside your aptitude practice.

Verbal ability is the section students from non-English-medium backgrounds worry about most. It covers reading comprehension, sentence correction, para-jumbles, fill-in-the-blanks, and sometimes vocabulary. If English isn't your strongest language, dedicate extra time here — read one editorial from The Hindu or Indian Express daily (seriously, just one, it takes 10 minutes), and practice sentence correction questions from any competitive exam prep book. The patterns repeat, and once you recognize them, the section becomes manageable.

Resume preparation (do this in week 1, not week 12)

Your resume needs to be ready before placement season starts. Not "almost done" or "I'll finish it this weekend" — actually done, reviewed, and polished. One page. Clean formatting. Professional font. No selfie photo. No objective statement that says "seeking a challenging position in a dynamic organization." Every recruiter in India has read that sentence a million times and it communicates exactly nothing.

From what I've seen, what should be on it: your education (college, branch, CGPA), technical skills (be honest — only list things you can discuss in an interview), projects (2-3, with brief descriptions focusing on what you did and what the outcome was), internships if any, certifications if any, and 1-2 extracurricular activities that show some dimension of your personality beyond academics.

The projects section is where most students either undersell themselves or write vague descriptions that don't communicate anything. "Built a web application using React" tells me nothing. "Built an expense tracker web app using React and Firebase that handles user authentication, budget categorization, and monthly spending visualizations — used by 50+ students in my hostel" tells me a lot. Be specific about what it does, what tech you used, and ideally what impact it had.

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

For IT and tech roles (this is the hard part)

If you're targeting IT companies — which, statistically, most engineering students in India are — the technical interview is where you'll face the most meaningful evaluation. Aptitude tests filter out the unprepared, but technical interviews are where companies actually decide if they want you.

Data structures and algorithms are the core of technical interview prep. At minimum, you need to be comfortable with: arrays, strings, linked lists, stacks, queues, trees (especially binary trees and BSTs), basic graph concepts, sorting algorithms (at least know quicksort, mergesort, and when to use which), and searching algorithms. At service companies like TCS and Infosys, the DSA bar isn't as high as at product companies — they're not going to ask you to implement Dijkstra's algorithm on a whiteboard. But they will ask you to solve basic problems, trace through code, and explain how common data structures work.

Let me break down the specific study approach for each topic, because "learn data structures" is vague and overwhelming. For arrays and strings, start with basic traversal and manipulation problems — reverse an array, find the second largest element, check if a string is a palindrome. Then move to slightly harder patterns: two-pointer technique, sliding window problems, and frequency counting using hash maps. These three patterns alone cover about 40% of array/string questions you'll see at service companies. Spend the first week of Phase 2 on just arrays and strings — about 20-25 LeetCode Easy problems focused on these topics.

For linked lists, understand the node structure first. Draw it out on paper — literally draw boxes with arrows. Then implement insertion, deletion, reversal, and cycle detection. The "reverse a linked list" question appears in an absurd number of campus interviews because it tests whether you actually understand pointers or just memorized syntax. If you can reverse a linked list on paper without hesitation, you're ahead of 70% of candidates. Spend 3-4 days here.

Stacks and queues are conceptually simpler but the application questions trip people up. Know the basic operations cold, then practice problems like balanced parentheses checking, implementing a queue using two stacks, and next greater element. These are common interview questions that seem hard until you've seen the pattern, and then they become almost mechanical. Two to three days is enough.

I think trees deserve a full week. Start with binary tree traversals — inorder, preorder, postorder — and make sure you can do them both recursively and iteratively. Then move to Binary Search Trees: insertion, deletion, searching, and finding the lowest common ancestor. The questions that actually show up in campus interviews tend to be: find the height of a tree, check if a tree is balanced, and level-order traversal using a queue. Don't go down the rabbit hole of advanced tree topics like AVL rotations or red-black trees — service companies aren't testing that. Focus on the basics until they feel automatic.

For sorting, you don't need to memorize ten different algorithms. Know bubble sort (because they sometimes ask you to trace through it), merge sort (understand the divide-and-conquer logic and know the time complexity), and quicksort (know the partition step and average vs worst case complexity). Be able to answer "when would you use merge sort over quicksort?" — the answer involves stability and worst-case guarantees. That's sufficient for 95% of campus placement sorting questions.

Practice on LeetCode (Easy problems are your target — do 50-75 of them), HackerRank, or GeeksforGeeks. Aim for 3-5 problems daily. Don't just solve them — make sure you understand why the solution works. If you can explain your approach out loud to an imaginary interviewer, you're in good shape.

Core CS subjects come up in almost every technical interview. The big four: DBMS (normalization, SQL queries, joins, transactions, ACID properties), Operating Systems (processes vs threads, scheduling algorithms, memory management, deadlocks), Computer Networks (OSI model, TCP vs UDP, HTTP, DNS — just the basics), and Object-Oriented Programming (four pillars, can you explain polymorphism with a real example, abstract class vs interface). You don't need to know these at PhD level. You need to know them well enough to answer questions confidently and explain concepts in your own words.

For non-tech roles

If you're targeting consulting firms, FMCG companies, banks, or other non-tech recruiters, your preparation looks different. Strengthen your knowledge of business fundamentals — basic finance, marketing concepts, supply chain, and current industry trends. Read the Economic Times or Business Standard daily. Practice case study analysis if targeting consulting (frameworks like SWOT, Porter's Five Forces, and basic profitability analysis).

Group Discussion preparation (yes, this needs practice)

Many companies include a Group Discussion round, especially for management trainee and non-tech positions. The biggest mistake students make is thinking GD is about being the loudest person in the room. It's not. Recruiters are watching for structured thinking, the ability to listen and build on others' points, respectful disagreement, and whether you can move the discussion forward rather than just repeating your own point.

It seems like practice with friends — pick a topic (AI's impact on employment, India's digital economy, startup culture vs corporate stability), set a timer for 15 minutes, and discuss. Record it on your phone and watch it back. You'll notice things you don't notice in the moment: how often you interrupt, whether you're actually responding to what others say, your body language, your verbal tics. Do this at least twice a week throughout Phase 2.

Company-Specific Interview Patterns (What Nobody Posts on YouTube)

Here's where generic placement advice falls short: every company has a different hiring pattern, and knowing what to expect gives you a genuine edge. I've compiled this from conversations with recent hires, placement coordinators, and my own experience helping students prepare. Take it as a guide, not gospel — companies tweak their processes, but the broad patterns hold.

TCS uses the TCS NQT (National Qualifier Test) as their primary filter, and it's divided into two parts. The Foundation section covers verbal ability, reasoning, and numerical ability — standard aptitude. The Advanced section, which you need for Digital roles (higher package), includes programming logic and coding questions. The coding questions in NQT aren't LeetCode Hard — they're pattern printing, basic array manipulation, and string processing. But they're timed, and students who haven't practiced under time pressure fumble here. After clearing NQT, the interview round at TCS tends to be relatively conversational. They'll ask about your projects, one or two CS fundamentals questions, and HR questions. TCS interviewers, in my experience, care a lot about whether you seem trainable and adaptable. They're hiring for potential, not for existing expertise.

Infosys has shifted in recent years. Their InfyTQ platform is now a significant hiring channel — if you perform well on InfyTQ assessments and courses, you can get a direct interview call, sometimes bypassing the on-campus process entirely. The aptitude test is standard, but their technical interview goes slightly deeper than TCS. Expect questions on DBMS (they love normalization and SQL queries), OOP concepts with code examples, and at least one question where they give you a code snippet and ask you to find the output or the error. For the Power Programmer and DSE roles, the bar is meaningfully higher — you'll face actual coding rounds with medium-difficulty problems. If you're targeting the standard SP role, solid basics are enough. If you want PP or DSE, you need LeetCode Medium-level preparation.

Wipro's NLTH (National Level Talent Hunt) is their mass hiring channel, and their online assessment includes an essay writing component that surprises students who only prepared for quant and coding. The essay isn't graded on literary quality — they're checking if you can construct a coherent argument in English. Wipro's technical interviews tend to focus on one or two subjects deeply rather than surface-level questions across many subjects. If your resume says you know Java, expect 15 minutes of Java-specific questions — not just "what is inheritance" but "explain the difference between abstract classes and interfaces with a scenario where you'd use each." Know your resume claims cold.

Consulting firms like Deloitte, EY, KPMG, and PwC have a completely different feel. The aptitude test is similar, but interviews emphasize communication skills, business awareness, and cultural fit much more than deep technical knowledge. For Deloitte's USI (US-India) tech consulting roles, they'll ask basic technical questions but spend more time on situational questions: "Tell me about a time you disagreed with a team member" or "How would you handle a client who keeps changing requirements?" Prepare 4-5 STAR-format stories (Situation, Task, Action, Result) from your college projects, internships, or even club activities. These firms want to see that you can think on your feet and communicate clearly under pressure — because that's literally the job.

Product companies that come to campus — Amazon, Microsoft, Google (at select colleges), Flipkart, PhonePe — are a different league. The coding rounds are genuinely challenging: LeetCode Medium to Hard, sometimes two or three problems in 60-90 minutes. If you're at a college where these companies recruit, you need to start DSA preparation well before this 90-day window. The interview process typically includes 2-3 technical rounds focused entirely on problem-solving and system design basics. If these are your targets, Phase 2 of this plan needs to be significantly more intense — 5-7 LeetCode problems daily, with a focus on dynamic programming, graph algorithms, and advanced tree problems.

Phase 3: Days 61-90 — Interview Mastery

Technical interview practice

Probably by now, you should know your material. This phase is about delivering it under pressure. The gap between "I know the answer" and "I can articulate the answer clearly in an interview setting while someone stares at me" is bigger than you think.

Practice explaining your projects out loud. Not reading from notes — talking about them naturally, the way you'd explain them to a friend. What problem were you solving? Why did you choose that technology? What challenges did you face? What would you do differently? If it was a team project, what specifically was your contribution? Interviewers can tell immediately when someone is talking about work they actually did versus work they copied and put their name on.

Practice writing code on paper or a whiteboard, not just on your laptop. Many interviews still use this format, and it's surprisingly difficult if you've never done it. You don't have autocomplete, you don't have syntax highlighting, you can't run the code to check — you need to get it right (or close to right) from logic alone. Practice 5-10 problems this way.

HR interview preparation

Prepare answers for: "Tell me about yourself" (60-90 seconds, structured, rehearsed but not robotic), "Why this company?" (specific to EACH company — don't give the same answer to TCS and Wipro), "Where do you see yourself in 5 years?" (realistic growth within the company), "What are your strengths and weaknesses?" (honest, specific, and for weaknesses, include what you're doing about it).

Research every company before their interview date. Know their services, recent projects, CEO, company values, and at least one specific initiative you can reference. This takes 30 minutes per company and separates you from the 80% of candidates who can't answer "What do you know about us?" with anything beyond "You're a leading IT company."

Mock interviews — non-negotiable

Do at least 10 mock interviews in the final month. With friends, seniors, professors, or through online platforms. Record yourself on your phone. Watch the recordings — I know it's uncomfortable, but the feedback is invaluable. Time your answers: most should be 60-120 seconds. If you're going over two minutes on a single answer, you're losing the interviewer's attention.

Ask your mock interviewer for specific feedback: Was I clear? Did I ramble? Did my body language convey confidence? Was my "Tell me about yourself" compelling or did it put you to sleep? Honest feedback from someone who's been through the process is worth more than any guidebook.

The Night Before and The Day Of

Night before: lay out your formal clothes, print extra copies of your resume (bring 3-4), charge your phone, review your key talking points (not studying new material — just reviewing what you already know), and sleep for at least 7 hours. Seriously. A well-rested brain performs dramatically better than one running on anxiety and caffeine.

Day of: arrive 15 minutes early. Not 30 (that's awkward). Bring a pen. Carry a folder with your resumes and copies of important documents. Put your phone on silent and keep it in your bag. Look people in the eye, offer a firm handshake, and smile. Remember that every interview is a conversation between two people trying to figure out if they're a good match — it's not an interrogation.

Ninety days of preparation brought you to this room. Trust the work you've put in. Give your best answers. Ask your best questions. And then, regardless of the outcome, know that you showed up prepared — which puts you ahead of most candidates who walked through the same door.