Design Strava
Record runs and rides with GPS, share them with friends and compete on route segments, like Strava.
Functional requirements
- Upload an activity recorded on a phone or watch
- See stats, a map and a feed of friends’ activities
- Leaderboards for popular route segments
Non-functional requirements
- Recording works with no signal
- Activities processed within a minute
- No activity data is ever lost
Scale
- 100M users
- 5M activities uploaded per day
- Each activity has thousands of GPS points
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 Strava”, that starts with: Upload an activity recorded on a phone or watch; See stats, a map and a feed of friends’ activities; Leaderboards for popular route segments. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (100M users; 5M activities uploaded per day; Each activity has thousands of GPS points) 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: Recording works with no signal; Activities processed within a minute; No activity data is ever lost. 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 geo data, uploads and leaderboards 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.