Skip to content
RED SAGSkills
hardAI Engineer (LLM & Generative AI) interview question

You must self-host an open-weights LLM for a high-traffic product. How do you plan memory, throughput and latency?

What the interviewer wants to hear

  • Size weights by parameter count and precision, and choose quantization carefully
  • Budget KV cache memory from layers, KV heads, context and concurrency
  • Use an inference server with continuous batching and paged KV cache
  • Balance throughput against time to first token and per-token latency
  • Load test with realistic prompt and output lengths, then autoscale

Model answer

I start with memory. Weights need parameters times bytes per parameter, so a model in 16-bit needs about 2 bytes per parameter, and 8-bit or 4-bit quantization cuts that but must be checked on our evals. Then the KV cache: per token it is 2 × layers × KV heads × head size × bytes, multiplied by context length and concurrent sequences, and it often dominates at long contexts. I would use a serving engine with continuous batching and paged KV cache, which raises throughput a lot. The key trade-off is throughput versus latency: bigger batches lower cost per token but raise time per token, so I set limits from our latency targets. Prefix caching and speculative decoding can help further. Finally I load test with realistic prompt and output lengths, and autoscale on queue depth.

Can you answer it under time pressure?

Take a timed hard round and get scored on every answer.

Start mock interview

More hard AI Engineer (LLM & Generative AI) questions