Design Spotify
Stream songs on demand, build playlists and search a huge catalog, like Spotify.
Functional requirements
- Search for songs, artists and albums
- Stream a song with little delay
- Create and share playlists
Non-functional requirements
- Playback starts in under 300 ms
- Works on spotty mobile networks
- The catalog is searchable worldwide
Scale
- 500M users, 100M songs
- About 5 MB per song at high quality
- The top 1% of songs get most plays
How you’ll be scored
11 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design Spotify”, that starts with: Search for songs, artists and albums; Stream a song with little delay; Create and share playlists. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (500M users, 100M songs; About 5 MB per song at high quality; The top 1% of songs get most plays) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: Playback starts in under 300 ms; Works on spotty mobile networks; The catalog is searchable worldwide. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe streaming, cdn and search here. This is a medium problem, so interviewers expect you to weigh two reasonable options, such as consistency against latency, and to say why you picked one.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.