← All questions
Technicalwarm-up
What's the difference between latency and throughput, and how would each show up for users?
How to approach it
Use a highway analogy: latency is how long one car takes to arrive; throughput is how many cars get through per hour.
How a strong answer opens
“Think of a highway: latency is how long one car takes to make the trip, and throughput is how many cars get through per hour. Users feel each one differently.”
Outline of a strong answer
Try answering out loud for a few minutes before you open this.
- Latency: how long one request takes, such as 300 milliseconds to load search results
- Throughput: how many requests the system handles per second
- High latency shows up as slow screens and abandoned searches even on quiet days
- Low throughput shows up as errors or queues during peaks, such as a flash sale
- They can trade off: batching work raises throughput but can add delay
- PM angle: set targets for both and test them at expected peak traffic
Where this question usually goes wrong
Using the two terms as if they mean the same thing, or defining them without saying how each shows up for users.
Learn the method
Technical trade-offs in Module 6, Technical for PMs.
The full kit has worked answers in full, start to finish, for every round type. $129 once.
More technical questions
- What is a cache, and what could go wrong if your product relies on one?
- Should we build our mobile app natively or with a cross-platform framework?
- How would you handle technical debt on your roadmap?
- Explain how a third-party login like 'Sign in with Google' works.
- Write a SQL query to find the top 10 customers by number of orders last month, and explain how you would check the result.