Scale Lab — Interview problem: URL shortener Intermediate

A classic interview problem, played over 4 rounds. Your design carries over from one round to the next, like a real system growing: don’t overbuild in the first round, but every decision must survive the next one.

The board offers every component, including ones you don’t need yet. Knowing when not to add anything is a skill too.

Load estimation, code generation and why 302 was chosen over 301 are covered in the URL shortener case study. Capacity and pricing assumptions are the same as in Scale Lab.