You already know: the system design method, capacity estimation, and the four LLM platform designs from the previous case (enterprise RAG, serving, gateways, agents). This lesson takes the first of those and goes all the way down, the way a staff-level interview does.
How to read this lesson. There is no code here, on purpose. A system design interview is a conversation about requirements, numbers, components and trade-offs. Every section follows the same rhythm: what you say, why you say it, what the interviewer asks next, and what you would change if the numbers changed. Numbers marked assumed are assumptions you state out loud in the interview; they are chosen to be realistic, not quoted from any company.
1. The prompt, and the questions that change the design
A mid-level candidate starts drawing a vector database. A staff-level candidate notices that the prompt hides four hard problems (permissions, freshness, tenant isolation and cost) and asks the questions whose answers change the architecture. Asking twenty questions is not the goal; asking the five that move boxes is.
Then you state the assumptions you will design to, so the interviewer can correct you early: