System design for freshers and new grads: is it asked, and what to learn first
An honest answer on whether new grads get system design rounds, and a 30-day plan if you do.
Is system design asked for new grads? Sometimes, and usually lightly. At most product companies, from the US and Europe to India, new-grad and 0–2 year roles are mostly judged on DSA, projects and CS basics. Some add a short design question: "how would you build a URL shortener?" Full system design rounds are much more common from mid-level (SDE-2, about 3+ years) upward.
What a new-grad round looks like. Expect 20–30 minutes, often inside a project or "low-level plus a bit of high-level" round. The interviewer wants to see that you ask what the system must do, guess rough numbers, draw a few sensible boxes (app servers, a database, a cache) and say what breaks first. Nobody expects you to know how a big company really runs it.
What to learn first. Not a list of tools. Learn the order of decisions (the five stages) and about ten core ideas. Everything else is these ideas at a bigger size.
Week 1: the basics. Read What is system design?, How the interview works and The five stages. Then the concepts: latency numbers, back-of-envelope maths, load balancing, caching, SQL vs NoSQL and indexes.
Week 2: data and scale. Replication, partitioning, consistent hashing, CDN, API design and rate limiting. Solve your first two problems end to end: URL shortener and rate limiter.
Week 3: async and correctness. Message queues, idempotency, transactions and locking, fan-out and CAP and PACELC. Solve news feed, chat app and notification system.
Week 4: practise like the real thing. Solve ticket booking, typeahead, nearby places, web crawler and key-value store. Do the daily question every day, and at least two timed mock interviews, out loud, as if someone is listening.
The 10 problems new grads get most. (1) URL shortener, (2) rate limiter, (3) news feed, (4) chat app like WhatsApp, (5) notification system, (6) ticket booking like Ticketmaster or BookMyShow, (7) search autocomplete, (8) nearby places, (9) web crawler, (10) key-value store. This list is from what the problems teach, not a survey: they are small enough for 30 minutes and cover the core ideas.
How to practise. Write your own answer before reading ours, every time. The daily question builds the habit in ten minutes a day. The mock interview adds a clock, which is where most beginners find they spend too long on boxes and too little on requirements and numbers.
Do not drop DSA for this. For entry-level roles, DSA and your projects still decide most offers. Treat system design as the round that turns a "maybe" into a "yes", and spend about a fifth of your prep time on it.
- New grads get light design questions at some product companies; full rounds are mostly mid-level and up.
- Learn the five-stage order and about ten core concepts before any big problem.
- Ten small problems cover almost everything a new-grad round asks.
- Practise out loud, with a clock, writing your answer before reading ours.
- Keep DSA and projects as your main prep; design is the tie-breaker.