Snap system design interview questions
One question on this site is reported in Snap software engineer interviews. Each is a guided run through requirements, back-of-envelope numbers, an interactive design, user flows and deep dives with interviewer follow-ups. Patterns covered: fan-out, ranking, caching, social.
Attribution comes from public interview guides and candidate reports, not from Snap. It indicates where a question has been asked, nothing more.
How to prepare for a Snap system design interview
Large-company loops run 45 to 60 minutes, expect numbers, and spend most of the time on deep dives. Work each question above in practice mode until you can produce the requirements, the estimates and the flows 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 Snap interviews under different names.
- Design a URL Shortenerkey-generation · caching · cdn
- Design Slackreal-time · websockets · fan-out
- Design a Payment Systemconsistency · idempotency · ledger
- Design YouTubetranscoding · cdn · adaptive-bitrate
- Design Google Mapsgeospatial · routing · graphs
- Design a Matchmaking Systemqueues · scheduling · latency
- Design Ubergeospatial · matching · streaming
- Design a Notification Systemfan-out · multi-channel · idempotency
- Design a Web Crawlerfrontier · politeness · dedupe
- Design a Rate Limiteralgorithms · counters · redis