The 60-second answer
Clarify operations and consistency: point updates, top-K queries, rank-of-item, time windows, ties, and expected read/write volume. For a single process, combine a key→score map with an ordered structure/heap depending required operations; for windows, account for expiration/decrements.
Build the answer in this order
Clarify operations and consistency: point updates, top-K queries, rank-of-item, time windows, ties, and expected read/write volume.
For a single process, combine a key→score map with an ordered structure/heap depending required operations; for windows, account for expiration/decrements.
At scale, shard updates, aggregate counters, and maintain approximate or materialized top-K views with clear staleness bounds.
Test tie semantics, duplicate updates, late events, rank churn, and recovery from missed/replayed events.
A useful interview mental model
This is the shape of a strong answer—not a script to memorize.
Senior-level signal
- Senior answers choose exact vs approximate ranking from product tolerance and scale.
- Discuss event idempotency, time-window semantics, and how hot items affect partitioning.
What the interviewer is really testing
Likely follow-up questions
Common weak-answer patterns
- Jumping to a model before defining the product contract.
- Listing components without bottlenecks, metrics, or failure handling.
- Ignoring data quality, serving latency, monitoring, and iteration.