Cracking a tech interview in India demands more than textbook knowledge. With lakhs of B.Tech graduates competing for the same roles at companies like TCS, Infosys, Flipkart, and startups, standing out requires a structured approach. The gap between what colleges teach and what interviewers ask has only widened. This guide breaks down a realistic, week-by-week preparation plan — covering DSA, system design basics, behavioral rounds, and the tools Indian students actually use. No motivational fluff. Just the exact steps that have helped students land roles at product companies and service firms alike.
Begin with arrays, strings, and linked lists — these form the foundation of 70% of coding rounds. Dedicate two weeks to mastering the top 50 LeetCode problems tagged Easy and Medium. Use the Striver SDE Sheet (created by Raj Vikram Aditya) which organises 180 problems by pattern, not by difficulty. This pattern-based approach helps you recognise similar problems during the actual test.
Once comfortable, move to trees, graphs, and dynamic programming. Solve 3-5 problems daily and maintain a revision tracker in Google Sheets. Every Sunday, revisit problems you solved earlier in the week without looking at the solution. Students who revise weekly retain 60% more patterns than those who only solve new problems. Aim to solve at least 120-150 quality problems over two months before any campus placement drive.
Most campus placement coding tests follow a predictable structure: 2-3 DSA problems in 90-120 minutes on platforms like HackerRank or HackerEarth. TCS NQT, Infosys InfyTQ, and Wipro WILP all test basic-to-intermediate DSA. Product companies like Flipkart, Razorpay, and Freshworks go deeper — expect graph problems, sliding window questions, or a medium-difficulty DP problem.
Beyond coding, expect a technical discussion around your projects. Interviewers will ask about the database schema you used, why you chose a particular framework, and how you handled edge cases. If you built a campus lost-and-found app using Django and PostgreSQL, know how you would scale it to handle 50,000 users. Prepare two-minute explanations for each project with concrete numbers: response time, number of users, or lines of code.
Most students underestimate behavioural rounds. Prepare 5-6 STAR-format stories covering teamwork, conflict, leadership, failure, and learning. Use the PAR framework: Problem, Action, Result. Indian interviewers value humility and self-awareness — saying 'I missed the deadline because I underestimated testing time, and now I always add buffer days' scores higher than claiming you never fail.
Research the company before every interview. If applying to Infosys, mention their recent AI-first strategy or EdgeVerve platform. For startups, talk about their product on Product Hunt or a recent funding round. This 30-minute research sets you apart from the 200 other candidates giving generic answers. Also, practice with a friend or use platforms like InterviewBuddy for mock HR rounds.
LeetCode remains the gold standard for problem practice. Use its company-tagged problem lists to focus on roles at your target employer. GeeksforGeeks is excellent for theory — their articles on system design basics and OS concepts explain things clearly. For mock interviews, Pramp offers free peer-to-peer sessions, while Interviewing.io lets you practise with anonymous engineers.
Track everything in a spreadsheet: date, problem solved, time taken, whether you solved it independently, and topics to revise. Students who track progress are 2x more likely to complete their targets. Also, join communities like r/IndianDevelopers on Reddit or Discord servers like DevSpace India where peers share interview experiences and referral opportunities. Consistency beats intensity — two focused hours daily outperforms weekend cramming.
Begin 8-12 weeks before your target placement season. Start with daily DSA practice in the first four weeks, then layer in system design basics, mock interviews, and company-specific preparation in the following weeks.
LeetCode covers the problem patterns well, but also practise on HackerRank for timed coding tests. Many Indian companies conduct rounds on HackerRank, so familiarity with that interface helps you avoid surprises on test day.
You should know basic concepts: client-server architecture, databases, caching, and API design. Fresher-level interviews rarely ask deep system design questions, but mentioning these concepts in project discussions shows depth.
Three to five quality problems daily is a realistic target for most students. Focus on understanding the pattern behind each solution rather than churning through 10 problems without reflection.
Yes, especially for behavioural and communication skills. Even solving a problem correctly matters less if you cannot explain your approach clearly. Practise thinking aloud while coding, either with a peer or a platform.
Referrals can fast-track your application past the initial screening pile. Build connections on LinkedIn, attend company webinars, and ask alumni from your college. One genuine referral increases your callback rate significantly.
Free to start · 100% online · Verified certificates