Sentry.io·Software Engineer·Onsite - System Design / Architecture
Jun 2026
System design round at Sentry.io focused entirely on a URL shortener, but don't let that fool you into thinking it was easy. The interviewer kept pushing deeper into production concerns, caching, sharding, metrics, and diagnosing real issues, so it turned into a pretty exhausting back-and-forth.
- Design a URL shortener system from scratch. Walk through the basic working version first, then scale it up to handle production concerns.
- How would you structure the service layer for the URL shortener? What responsibilities should it own?
- Which database would you choose for storing shortened URLs, and why? What are the tradeoffs?
- Where would you add caching in this system, and what caching strategy would you use?
- How would you shard the database as the system grows? What are the tradeoffs of different sharding strategies?
- If users are reporting that redirects are suddenly slow, how would you diagnose the root cause?
- What metrics would you track to confirm whether a performance issue is caused by the database versus the cache versus the application layer?
“Started fine with the basics, hash function, redirect logic, a simple key-value store.”