How would you design a link shortening service that has to handle millions of redirects a day? Talk me through the main pieces and trade-offs.

What the interviewer is looking for

• This question tests system design. Starts from requirements and scale, sketches the main components, names trade-offs like consistency versus availability, and explains what they would change as load grows.
• Strong answers: Clarifying requirements, generating unique codes, choice of storage, heavy caching for reads, handling scale and hot links, and discussing analytics and abuse.
• Likely follow-up: What breaks first if traffic grows tenfold overnight?

Another way it may be asked: Imagine building a service that turns long web addresses into short codes and sends people to the right page. How would you structure it?

A structure to follow: Requirements, sketch, deep-dive, trade-offs

1. Step 1

   Requirements

   Ask who uses it, what it must do, and which qualities matter most: speed, reliability, cost, consistency.

2. Step 2

   Sketch

   Draw the main parts and the path one request takes through them before adding detail.

3. Step 3

   Deep-dive

   Pick the riskiest part (storage, queueing, failure handling) and go deeper there.

4. Step 4

   Trade-offs

   Name what you gave up for each choice, and what you would do first if it needed to grow.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Naming tools before establishing requirements.
• Drawing every box at the same depth instead of going deep where it matters.
• Presenting one design as the only answer, with no trade-offs.

How to practise it

Time yourself: two minutes on requirements, five on the sketch, five on one deep-dive, two on trade-offs.

Related questions

• Tell me about a technical decision where you chose a simpler design over a more flexible one. How did it play out?
• When would you pick a hash map over a list to store data, and what does that choice cost you?
• Imagine your code works on your laptop but fails in the test environment. Walk me through how you would start figuring out why.
• How do you usually use Git day to day, from starting a piece of work to getting it merged?
• How do you decide what to test in a new feature, and how do you balance unit tests against integration tests?

Browse all questions