Build fundamentals first — load balancers, caching, SQL vs NoSQL databases, message queues, sharding and replication — then study classic designs like a URL shortener, chat app, news feed and rate limiter. Give yourself 4–6 weeks: 1–2 weeks for concepts, the rest for designing 15–20 problems end to end while consciously weighing trade-offs, since that is what interviewers grade you on.

Treat every session like the real thing: pick one problem, set a 40–45 minute timer, draw the architecture while talking through your decisions, and finish with a deep dive into one bottleneck. Compare your design with reference solutions afterwards and note the gaps. Practising aloud in mock interviews with a peer, mentor or senior engineer is the fastest way to fix communication gaps, which is where most candidates lose points.

Follow a clear structure: clarify functional and non-functional requirements, estimate scale (users, QPS, storage), define the API, sketch a high-level design, and then deep dive into database choices, caching and failure handling. Interviewers evaluate how you handle ambiguity and justify trade-offs more than whether you land on a single "correct" design, so keep narrating your reasoning throughout.

The most frequent prompts are designing a URL shortener, a chat app like WhatsApp, a social media feed, a food delivery or ride-sharing platform, a ticket booking system, a payment/UPI system, a rate limiter and a notification service. Practice 15–20 of these end to end and you will notice the underlying patterns repeat quickly.

Grokking the System Design Interview is a widely used online course that teaches a repeatable framework for design rounds and walks through classic problems such as a URL shortener, chat system and web crawler. It is a solid starting point for beginners, but pair it with self-driven practice because interviewers often pick problems outside the well-known classics.

The System Design Interview books by Alex Xu (Volumes 1 and 2) are among the best resources for concepts and step-by-step designs, with Volume 2 covering advanced topics like microservices and consistency. On their own, though, they are not enough — the real interview is interactive, so you also need to design unseen systems out loud and get feedback through practice sessions.

Revise core topics in order — arrays, strings, hashing, linked lists, stacks and queues, trees, heaps, graphs, recursion and dynamic programming — and solve a mix of easy, medium and hard problems daily. Focus on recognising patterns like two pointers, sliding window, BFS/DFS and top-down DP rather than memorising individual problems, and always practise explaining your approach and complexity aloud.

Questions on arrays and strings (two pointers, sliding window), hashmaps, linked lists, stacks, binary trees and BSTs, heaps, and graph traversal come up most often, with dynamic programming appearing in mid and senior rounds. Expect a follow-up on time and space complexity for every solution you give.

For freshers, interviewers stay close to fundamentals: array and string manipulation, linked list operations like reversal and cycle detection, stack-based problems, basic tree traversals, simple recursion and complexity analysis. Campus placements and entry-level drives in India often add aptitude, pseudo-code output questions and CS fundamentals such as OS, DBMS and networks alongside the DSA round.

At that level, interviewers expect you to reach the optimal approach quickly, justify trade-offs under constraints, and handle harder variations across graphs, dynamic programming and large-scale data handling. They also probe depth — for example, why a particular data structure fits a real production problem — so be ready to connect theory to systems you have actually built.

Run two tracks in parallel: technical depth (system design and, at many companies, coding) and leadership storytelling. Prepare 6–8 STAR stories covering team building, delivery under deadlines, handling underperformance, conflicts and stakeholder pushback, and rehearse them in mock interviews. The most common mistake is talking only about technology and never demonstrating people outcomes.

Work backwards from the company's interview loop: refresh system design and DSA if the role tests them, build a story bank around your team's measurable outcomes, and tighten your resume so every bullet shows impact rather than responsibilities — a proper resume review at this stage can decide whether you get shortlisted. Finish with company research and two or three thoughtful questions of your own.

Most engineering manager interviews run 3–5 rounds: a recruiter or hiring manager screen, one or two technical rounds (coding and/or system design depending on seniority), and deep behavioural rounds on people management, delivery and cross-team work. For senior EM roles in India, the behavioural and leadership rounds usually carry as much weight as the technical ones.

The recurring ones include: how you handled an underperformer, a conflict within your team, a project slipping past its deadline, how you prioritise when everything is urgent, how you hire and retain talent, and why you moved into management. Technical rounds often start from the architecture of the last system you owned, so be ready to defend its design decisions.

The engineering manager interview at Google typically includes coding rounds, a system design round, and behavioural rounds assessing people management along with communication, collaboration and leadership signals, followed by a hiring committee review of the feedback. Preparing crisp leadership stories alongside technical practice matters as much as DSA for this loop.