The tech interview is a peculiar ritual: months of preparation for a few hours that decide your career trajectory and salary for years. Product companies in India, from Bengaluru startups to the Indian offices of global giants, run candidates through a gauntlet of strikingly similar rounds: coding, system design, and behavioural evaluation. Each round tests something different, rewards different preparation, and eliminates candidates for different reasons. Understanding what interviewers are actually looking for in each round is the difference between preparing hard and preparing right.

DSA: the coding rounds

Data Structures and Algorithms rounds ask you to solve coding problems live, on arrays, strings, trees, graphs, dynamic programming, while explaining your thinking aloud. What interviewers really assess is not memorised solutions but problem-solving process: clarifying the question, proposing a brute force, optimising it, analysing time and space complexity, and writing clean, working code. Preparation is well understood: 200 to 300 problems on LeetCode or CodeChef, progressing from easy to medium, with patterns recognised rather than solutions memorised. Consistency beats cramming; an hour daily for four to six months transforms most candidates. The commonest failure is silence: candidates who think quietly instead of narrating leave interviewers unable to give partial credit, and partial credit decides close calls.

System design: the senior rounds

For experienced roles, and increasingly for strong freshers at top companies, system design rounds ask you to architect large systems: design WhatsApp, design a URL shortener, design a food-delivery backend. There is no single right answer; interviewers evaluate how you handle ambiguity, make trade-offs, and reason about scale. The expected structure: clarify requirements, estimate scale, sketch high-level components, then dive deep into databases, caching, load balancing, and failure handling. Preparation means studying real architectures, the classic Grokking-style resources, engineering blogs, and practicing aloud until the vocabulary, sharding, replication, consistency, CDNs, becomes fluent. Freshers should know the basics; experienced candidates are expected to discuss trade-offs from real battle scars.

The HR and behavioural rounds

Candidates treat these as formalities; interviewers treat them as filters. Behavioural rounds assess culture fit, communication and genuine motivation through questions about past projects, conflicts, failures and teamwork. The STAR method, Situation, Task, Action, Result, structures answers that would otherwise ramble. Prepare five to seven real stories from your experience covering leadership, conflict, failure, and impact; authentic specifics beat polished generalities. For freshers, project discussions serve the same purpose: deep, honest knowledge of your own projects impresses more than claimed expertise in ten technologies. And always prepare thoughtful questions for the interviewer; having none signals indifference, the quietest rejection reason.

How recruiters shortlist resumes

Before any round, your resume faces a six-second scan. What survives: a clean one-page format, quantified impact, “built X used by Y users” or “improved Z by N per cent”, relevant skills matching the job description, and links to GitHub and deployed projects. What dies: dense paragraphs, buzzword soup, exaggerated claims that collapse under questioning, and sloppy formatting. Referrals multiply your chances enormously in the Indian market; a referred resume gets read, a cold application joins thousands. Build your network before you need it: seniors, alumni, community contacts. And tailor each application lightly; mass-applying the same resume everywhere is visible and ineffective.

The preparation timeline

Work backwards from your target date.

• 6+ months out: DSA fundamentals daily, one programming language deeply, core CS subjects for campus placements.
• 3-6 months: LeetCode mediums by pattern, first projects completed, system design basics for experienced candidates.
• 1-3 months: timed mock interviews, behavioural story bank, resume refinement, targeted applications.
• Final weeks: revise patterns not new topics, rest properly, research each company specifically.

The meta-skill is treating preparation as a system: track problems solved, review mistakes weekly, and do mock interviews with peers, because performing under observation is a separate skill from solving alone.

FAQs

How many LeetCode problems are enough? Quality over quantity: 200-300 well-understood problems across all patterns beats 800 skimmed ones. Interviewers detect memorisation instantly.

Do service companies ask system design? Rarely for freshers; they focus on basic coding, CS fundamentals and communication. Product companies and startups are where DSA and design dominate.

What if I blank out in the interview? Say so honestly and think aloud; interviewers help candidates who communicate. Ask clarifying questions to buy thinking time legitimately.

Tech interviews measure a learnable skill set, not innate genius: structured problem-solving, communicated clearly, backed by genuine project experience. Prepare the process, not just the content, and the ritual becomes winnable. Thousands of Indian engineers crack it every year; with systematic preparation, there is no reason you cannot be one of them.

Source: GeeksforGeeks