System Design Mock Interview
Sample session
- Hire @ Mid-level · High confidence
- No hire @ Senior · Average confidence
Question asked
Design a URL shortener that handles 100 million new links per month.
Summary
You designed a URL shortener with a sensible structure and explained your choices clearly. Your API and data model were solid. The main gap was scale: you picked a datastore before estimating traffic, and you did not revisit it when I raised read-heavy load. With a little more rigor on estimates and caching, this is a Senior-level answer.
Key takeaways
Estimate before you choose
State rough numbers for requests per second, storage and read/write ratio out loud first. They justify every later decision and show the interviewer how you think.
Go deeper on one component
You covered the whole system evenly. At Senior, pick the riskiest part (here, ID generation) and walk through failure modes and trade-offs in detail.
Competency breakdown
Problem Navigation
You clarified scope quickly and kept the conversation organised.
Positives
- Asked about custom aliases and expiry before designing
- Kept a clear outline
Areas to improve
- Skipped capacity estimates until prompted
Solution Design
A clean, workable design with a sensible API and data model.
Positives
- Simple, correct schema
- Good separation of read and write paths
Areas to improve
- Cache invalidation was not discussed
Technical Excellence
Sound fundamentals; depth on ID generation was thin.
Positives
- Knew the trade-offs between hashing and counters
Areas to improve
- Did not cover collisions or multi-region generation
Technical Communication
Clear, calm and easy to follow.
Positives
- Thought out loud
- Summarised decisions as you went