Design Top K ranking system

Quick Overview

Design Top K ranking system evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

Design Top K ranking system

Company: LinkedIn

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Onsite

##### Question Design a system that can continuously identify the Top K elements from a large or streaming dataset. Discuss data structures, scalability considerations, update handling, and how to support high-throughput queries.

Quick Answer: Design Top K ranking system evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

|Home/System Design/LinkedIn
LinkedIn logo
LinkedIn
Jul 29, 2025, 8:05 AM
hardSoftware EngineerOnsiteSystem Design
18
0

Design Top K ranking system

System Design: Real-time Top-K from a Large/Streaming Dataset

Context

You receive a continuous, high-volume stream of events, each referencing an item (e.g., item_id). The system must continuously identify the Top K most frequent items and serve low-latency queries. Assume:

  • Data volume is large (potentially millions of events per second), item cardinality can be high, and K is small (e.g., 10–1,000).
  • Queries may request Top K for different time windows (e.g., last 1 minute, 1 hour, 1 day) and potentially by a grouping key (e.g., per region, per tenant).
  • Results should be near-real-time with bounded staleness.

Requirements

Design a system that:

  1. Ingests a large/streaming dataset and continuously identifies the Top K elements.
  2. Chooses suitable data structures for exact and approximate solutions.
  3. Scales horizontally across shards/partitions.
  4. Handles updates: insertions, deletions/expirations (e.g., sliding windows), out-of-order/late events.
  5. Supports high-throughput, low-latency queries (read path), including caching/materialization.
  6. Discusses consistency, fault tolerance, and operational considerations.

Provide the design, trade-offs, and key algorithms/data structures. Include complexity and accuracy considerations.

Clarifying Questions to Ask Guidance

  • Clarify users, core use cases, read/write patterns, scale, latency, availability, and data retention.
  • State explicit assumptions before making sizing or architecture decisions.
  • Prioritize the functional path first, then address reliability, security, observability, and rollout.

What a Strong Answer Covers Guidance

  • A scoped requirements summary with concrete non-goals and success metrics.
  • API, data model, architecture, consistency, capacity, and operations.
  • Reasoned trade-offs among simple and scalable designs, including bottlenecks and failure modes.
  • A validation, monitoring, migration, and launch plan appropriate for the risk level.

Follow-up Questions Guidance

  • What breaks first at 10x traffic or data volume?
  • How would you degrade gracefully during dependency failures?
  • What metrics and alerts would prove the design is healthy after launch?

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...