Design a URL Shortening Service
Last updated: January 25, 2026
Quick Overview
Design a low-latency url shortening system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
Slack
January 25, 20267
5
1,572 solved
Design a low-latency url shortening system that handles millions of requests. Discuss trade-offs in consistency, availability, and performance.
ML system design at Slack goes beyond model selection. This Technical Screen question evaluates your ability to design end-to-end ML pipelines, from data collection to model serving, while considering production constraints like latency and reliability.
What the Interviewer Expects
- Map the business problem to a concrete ML objective
- Propose reasonable features and a baseline model
- Discuss basic model evaluation metrics
- Outline a simple serving architecture
Key Topics to Cover
How to Approach This
- Start by clarifying functional and non-functional requirements with the interviewer.
- Estimate the scale: QPS, storage, bandwidth. This drives your design decisions.
- Draw a high-level architecture first, then deep dive into 1-2 critical components.
- Discuss trade-offs explicitly (e.g., consistency vs availability, SQL vs NoSQL).
- Address failure scenarios, monitoring, and how the system handles 10x traffic spikes.
Possible Follow-up Questions
- What would you do if model performance degrades over time?
- How would you ensure fairness and reduce bias in the model?
- How would you handle a 10x increase in prediction requests?
Practice a Similar Problem on Codemia
Solve a related problem with our interactive workspace, get AI feedback, and view detailed solutions.
Solve on CodemiaSample Answer
Requirements Clarification
Before diving into the architecture, clarify the scope with the interviewer. For URL Shortening Service, key functional requirements include: what are...
Capacity Estimation
Estimate the scale to drive design decisions. Assume 100M DAU with an average of 10 actions per user per day = 1B requests/day ~ 12K QPS average, ~36K...