Design Strava
Record runs and rides offline, process each upload into a map, stats and segment efforts, and rank them for 100 M athletes.
One question on this site is reported in Strava software engineer interviews. Each has a full reference design (requirements, back-of-envelope numbers, components, user flows and deep dives with interviewer follow-ups). Each one can be walked through turn by turn and then sat as a mock. Patterns covered: geospatial, async-pipeline, spatial-matching, leaderboards, privacy.
Attribution comes from public interview guides and candidate reports, not from Strava. It indicates where a question has been asked, nothing more.
Record runs and rides offline, process each upload into a map, stats and segment efforts, and rank them for 100 M athletes.
Large-company loops run 45 to 60 minutes, expect numbers, and spend most of the time on deep dives. Walk through a question to see how a strong candidate paces the hour, sit the same question as a mock until you can produce the requirements, the estimates and the design without looking, then read the interview framework guide for how to structure the hour. The other questions on the site teach patterns that show up in Strava interviews under different names.
The question reported in Strava system design interviews is Strava. It tests geospatial, async pipeline, spatial matching, leaderboards and privacy. The reports come from public interview guides and candidate accounts, not from Strava, so practise the patterns rather than memorising one list.
Practise the questions reported there out loud, under a 45-minute clock: requirements with numbers first, then estimates, a high-level design, and deep dives into the two or three hardest parts. Start with Strava: watch a strong candidate answer it turn by turn, then sit it yourself. Then cover the patterns the round leans on (geospatial, async pipeline, spatial matching and leaderboards) with one more question each.