Campus Placement Preparation Strategy India 2026: Complete Timeline and Checklist

Campus placement timeline for Indian engineering colleges: Most top-tier colleges (IITs, NITs, IIITs, top private colleges) have placement seasons beginning in July-August. Most other colleges (tier-2 and tier-3) have placement seasons running September-January. The gap matters for preparation time.

Ideal start time: end of 6th semester (after May exams for a July-August placement season). This gives 2-3 months of focused preparation. Start any earlier (in 5th semester or before) if you are targeting FAANG India or top product companies: they require deeper DSA and system design preparation that takes 4-6 months to build adequately.

What happens in placement season week-by-week: Day 0 (company visit): aptitude/coding test. Day 1-2: results announced. Day 2-3: technical interviews (1-3 rounds). Day 3-4: HR interview. Day 4-5: offer or rejection letter. Multiple companies visit in the same week; you may have a Day 0 test for Company A on the same day as a technical interview for Company B. Managing this calendar is itself a skill.

Month 1 (Fundamentals): (1) DSA: 3-4 LeetCode easy problems per day. Cover arrays, strings, linked lists, stacks, queues, trees (BFS/DFS, in/pre/post order traversal), and basic graph traversal. Target: 90-120 problems with solutions you can explain. (2) CS fundamentals: OOP (all 4 pillars with code examples in Java or Python), DBMS (15 key SQL queries from memory: SELECT, JOIN, GROUP BY, HAVING, subquery, aggregate functions; ACID; normalisation), OS (process vs thread, deadlock, virtual memory, scheduling algorithms), networks (OSI model, HTTP/TCP/UDP, what happens when you type a URL). (3) Resume: finalise 1-page resume. Every project bullet must have: action verb + specific technology + specific outcome. (4) Company identification: list your target companies by tier. Tier 1 (dream): 2-3 companies requiring deep preparation. Tier 2 (strong preference): 3-5 companies with moderate preparation. Tier 3 (mass recruiters): TCS, Infosys, Wipro, Cognizant, Capgemini, Accenture (general preparation is sufficient).

Month 2 (Company-Specific): (1) Aptitude: TCS NQT mocks on PrepInsta/IndiaBIX (if TCS is a target), Infosys Hackwithinfy practice papers, Wipro NLTH mocks. (2) Intermediate DSA: dynamic programming (memoisation and tabulation for classic problems: fibonacci, knapsack, LCS, LIS, coin change), backtracking (generate permutations, N-queens), sliding window (maximum sum subarray of size k), two-pointer (pair sum, 3Sum). (3) Projects: deploy your top project with a live URL. Record a 3-minute demo video. Practise the 5-minute project walkthrough. (4) Communication: 5 mock interviews on HireStepX (HR + behavioural rounds), 5 on Pramp (technical coding rounds).

Month 3 (Integration): (1) Full placement simulation: mock the full process (aptitude test + coding + 2 technical interviews + HR) in one 4-hour session. Do this 2-3 times. (2) GD preparation: form a group of 5-6 peers; practise 2-3 GDs per week on technology and current affairs topics. (3) Company research: for each company visiting your campus, prepare 3 talking points (why this company, one product feature you use, one recent news).

Practical strategies for the chaos of placement season: (1) The placement tracker spreadsheet: columns: company name, visit date, current stage, CTC offered, location, role title, offer deadline, your priority (1-5). Update after every event. This prevents the common mistake of forgetting an offer deadline or missing a scheduled call. (2) Offer prioritisation: classify offers before placement season starts. Decide your threshold: 'I will accept any product company offer of 10 LPA or above. I will hold IT services offers until I have exhausted product company processes.' Most colleges have a convention around how many offers you can hold simultaneously; check with your placement committee. (3) HR communication: if you cannot attend a scheduled interview due to a conflict with another company visit, email the HR contact immediately. 'I have a scheduling conflict with another company's process on [date]. I am very interested in [Company] and would like to attend [alternative slot]. Is that possible?' Most companies accommodate this during campus season. Do not simply not show up without communication. (4) Mental health: placement season is high anxiety. The best preparation is: clear definition of success ('I will be satisfied with any offer above X LPA'), maintaining a routine (sleep, exercise, not just interview prep), and peer support (group preparation helps reduce isolation).

One week before a company visit: (1) Company research (2 hours): products the company builds, recent funding or news announcements, the specific role requirements, any engineering blog posts or technical content the company has published. Prepare 3 talking points for 'why this company'. (2) Resume audit (30 minutes): re-read your resume as the interviewer will. Can you speak to every item for 2+ minutes? If not, either prepare or remove the item. (3) Project demo check (45 minutes): open your project, run it, verify the live URL works. Prepare the 3-minute verbal walkthrough: what it does, how it works technically, the hardest part, and what you would do differently. (4) CS flash review (2-3 hours): OOP 4 pillars with code examples, 5 SQL queries, deadlock definition and 4 conditions, OSI model 7 layers, HTTP status code mapping. Not to learn new content; to activate what you already know. (5) Mock interview (1-2 hours): 1 technical coding mock (Pramp or HireStepX technical mode), 1 behavioural/HR mock (HireStepX). Day-before-drive goal: be at 80-85% confidence, not 100% cramming. Cramming the night before increases anxiety without increasing capability. (6) Logistics: document folder (college ID, resume x5, marksheet, passport photo x4), professional dress prepared, commute plan, 15 minutes early arrival.