Frame the problem
Syllabus
Detailed content
A repeatable interview approach
Treat the interview as a design conversation. Confirm the problem, identify the most important constraints, and keep a visible list of assumptions. Work from a simple baseline toward improvements. Explain why each component exists, what it costs, and what failure it addresses. Reserve time to summarize the design and its trade-offs.
Functional requirements and user journeys
Write down the actions the system must support before selecting technologies. Identify the actors, their main journeys, and the data each action creates or reads. Separate essential behavior from optional features. A short list of explicit use cases gives the design a boundary and prevents unrelated features from taking over the interview.
Quality attributes and constraints
Translate words such as “fast” and “highly available” into measurable targets: latency percentiles, availability, durability, privacy, and expected growth. Ask about region, compliance, budget, and operational limits. These constraints determine which architecture is appropriate; without them there is no defensible reason to choose one design over another.