System design
From one overloaded server to staff level design questions. The path IndGeek is built around, and every topic on it has a chapter.
What is system design, and who needs it?
System design is the skill of deciding how a product holds up when real people use it: where the data lives, what happens when traffic jumps ten times, which part fails first and what you trade to stop it.
It is also the round that separates mid level from senior offers. This roadmap goes from the numbers every design starts with, through the building blocks and the databases underneath them, to the questions interviewers ask, the India scale systems and the AI systems now being designed everywhere.
- Stage 01Start here
The vocabulary every design question is answered in.
6 of 6 written - Stage 02How databases behave
Most designs succeed or fail in the database. Know what it is doing.
6 of 6 written - Stage 03Building blocks
The parts every large system is assembled from.
6 of 6 writtenCheckpointDesign a URL shortener - Stage 04The classic questions
The ones every interviewer has asked at least once.
8 of 8 writtenCheckpointDesign a file sync service - Stage 05Location, media and real time
Questions where geography, bandwidth or concurrency is the hard part.
6 of 6 written - Stage 06India scale
A billion users and one very busy morning.
4 of 4 written - Stage 07Staff level
Where the hard part is the trade-off, not the boxes.
6 of 6 written - Stage 08Systems with a model inside
The design questions every company is now asking about AI.
6 of 6 written