Turn system knowledge into an answer you can defend.
Search the complete question catalog first, then browse by interview format or system specialization when you want a wider drill set.
Filter the question, then open the exact answer.
Combine format, system domain, difficulty, concept, and keywords. The URL keeps the same view when you refresh, go back, or share it.
Choose the kind of reasoning being tested.
Use these routes when you want a complete drill set instead of one filtered question.
Fundamentals & Breadth
Explain mechanisms, formulas, boundaries, and trade-offs without reciting definitions.
Transformer · GPU · Serving 02 · QUANTITATIVECoding & Quantitative Reasoning
Implement primitives and derive memory, communication, throughput, and latency bounds.
Python · PyTorch · Estimation 03 · ARCHITECTURESystem Design
Frame requirements, estimate capacity, draw the data path, and defend reliability choices.
Training · Serving · Platform 04 · OPERATIONSDebugging & Operations
Diagnose OOMs, hangs, low utilization, long-tail latency, queue pressure, and recovery.
Evidence · Failure isolation · SLOsThen choose the system you want to be tested on.
Every question receives a format, domain, difficulty, and canonical-concept mapping.
Use the same evidence-first loop every time.
- ScopeState the workload, constraints, and success metric.
- MechanismName the state and operation that dominate the behavior.
- EstimateWrite one resource ledger or back-of-the-envelope bound.
- ValidateName the trace, metric, experiment, or failure signal that would confirm it.