How do you reason about tail latency when the model calls a feature store and then a second ranker?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
End-to-end p99 is not the sum of p99s
WHY — Latency and Throughput instead of guessing?
Why interviewers care about Latency and Throughput:
question about Latency and Throughput.
trade-offs, and what you would actually do on a MLOps project - not buzzwords.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1End-to-end p99 is not
the sum of p99s
- 2you need traces and
a latency budget per hop.
- 3Parallelize independent lookups, set
aggressive timeouts, and degrade features rather than waiting.
- 4A single retry policy
that multiplies load can melt the store during incidents.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
End-to-end p99 is not the sum of p99s you need traces and a latency budget per hop.