AI Infra Interviews logo
Practice tests · 30 questions

AI Infrastructure System Design: the practice test

Design an inference platform at 10k requests per second, a 10,000-GPU training cluster, a job scheduler with preemption and checkpointing, a serverless GPU runtime with sub-second cold starts, a multi-tenant fine-tuning service, an eval pipeline. The whiteboard round at OpenAI, Anthropic, Baseten and Together. This test drills exactly that: 10 easy, 10 medium and 10 hard questions, every one explained, every explanation linking into the worked material.

Set up your test
Topic
How confident are you feeling?
Questions
10 in this pool · about 7 min
Reveal answers
Sign in to startFree account · your questions rotate between takes

Sample questions, answered

easy · sample
Which seven boxes make up the reference shape of an LLM inference platform?
Load balancer, web servers, a relational database, a cache, a message queue, workers and a CDN
Gateway, router, engine scheduler, replicas, KV tier, autoscaler, observability
Tokenizer, embedding store, vector index, reranker, generator, guardrails and a logging bus
Prefill pool, decode pool, a weight store, a checkpoint store, a job queue, a scheduler and a dashboard

The gateway authenticates, rate-limits and validates; the router picks a replica by prefix locality and load; the engine's scheduler batches and admits requests; replicas hold model copies across one or more GPUs; the KV tier is the paged pool on GPU with optional offload; the autoscaler sizes the pool with cold starts in mind; observability tracks TTFT, TPOT, goodput and KV utilization. A design answer names each box's job and its failure mode, then sizes the pool with a stated chain of arithmetic.

easy · sample
Why is a least-connections load balancer the wrong router for LLM replicas?
Because it cannot read the model name from the request, so every replica must hold every model
Because it needs sticky sessions, which HTTP/2 does not support without a proxy in front of every replica
Requests differ 100× in cost and replicas differ in which prefixes they hold
Because LLM engines only accept one connection at a time per GPU

A 300-token completion and a 30,000-token summary are one connection each, but differ by two orders of magnitude in prefill work and KV footprint; and a replica that already holds a conversation's prefix answers in 12 ms of prefill where a cold one needs 200 ms. A cost-aware router scores each replica as expected prefill after cache hits plus expected queue wait, reading pending tokens, running sequences and KV occupancy from the engines, and picks the minimum; near saturation the queue term overrides affinity.

Go deeper than the quiz

A practice test measures recall. The material it draws from teaches the reasoning: