Interviewers want to watch you draw connections and reason about tradeoffs, which you can do without having run the thing in production: https://t.co/F1NM5H3ssJ
One event needs to hit billing, analytics, and 3 other services. Spinning up a queue per consumer duplicates the message everywhere. Use one Kafka topic with a consumer group per service; each one reads the same log at its own pace.
A recording of a real senior system design interview, anonymised and shared with the consent of both the candidate and the interviewer. The problem is designing an e-commerce platform.
What moves people is zooming out for company context, scaling yourself through projects other engineers run, and sometimes a team change to build the leadership perception you do not currently have.
In manager interviews it is easy to open a negative assumption in your interviewer's head without noticing, usually by describing what you did and never why.
Shard splitting fixes the root cause when a physical node is the bottleneck, but it's operationally painful. Reach for it last, after replicas and key copies fall short.
Stefan talks to Jordan, who runs Jordan Has No Life, about how he actually learned system design and why personal projects taught him more than reading did.