Intervjui za dizajn sustava procjenjuju vašu sposobnost dizajniranja velikih sustava — česti su za srednje/starije pozicije. Uspjeh uključuje strukturirani pristup: razjasniti zahtjeve, dizajnirati na visokoj razini, zaroniti u detalje i razmotriti kompromise i skalabilnost.
Strukturirani pristup
1. CLARIFY requirements → functional (what it does) + non-functional (scale, latency,
availability); ask about scope, users, constraints (don't assume — narrow the problem)
2. ESTIMATE scale → users, requests/sec, data volume (informs the design)
3. HIGH-LEVEL design → main components and data flow (API, services, database, cache,
etc.); draw the architecture
4. DEEP DIVE → detail key components; data model; specific challenges
5. SCALE & TRADE-OFFS → identify bottlenecks; discuss scaling (caching, load balancing,
sharding, replication); trade-offs of choices
