Katkat

Topic

System Design interview questions

1311 System Design questions from 230 companies, with hints, runnable code and solution walkthroughs.

Questions1311

60 easy819 medium432 hard

Your progress0/1311

System Design interview questions by the numbers

Last updated

Katkat has 1,311 System Design interview questions from 230 companies; the most come from OpenAI (8%), Meta (5%) and Amazon (4%). By difficulty: 5% easy, 62% medium and 33% hard. The most common round is Onsite (55%). Frequent concepts include System Design, Distributed Systems, Scalability and Caching.

Companies (230)

Difficulty

  • Easy5% · 60
  • Medium62% · 819
  • Hard33% · 432

Interview rounds

  • Onsite55% · 721
  • Technical Screen39% · 517
  • Online Assessment3% · 38
  • Other2% · 21
  • HR Screen1% · 13

Roles

  • Software Engineer91% · 1189
  • Machine Learning Engineer2% · 31
  • Data Engineer2% · 26
  • Backend Engineer2% · 25
  • Frontend Engineer1% · 19

Frequent concepts

  • System Design31% · 400
  • Distributed Systems24% · 316
  • Scalability15% · 196
  • Caching7% · 95
  • Concurrency7% · 91
  • system-design6% · 83

Showing 1081–1110 of 1311 results

  • This question tests the ability to design a distributed, fault-tolerant job scheduling system capable of meeting strict SLAs and providing audit-ready logging.

    RobinhoodSoftware EngineerSystem DesignTechnical Screen
  • A system design question that asks for a stock quote API serving live prices at about 10 million requests per second and one-day, one-month and one-year history at about 1 million, fed by two redundant exchange trade connections. It tests sequence-number arbitration, gap replay, fan-out of live state, bar aggregation and caching at scale.

    RobinhoodSoftware EngineerSystem DesignOnsite
  • This System Design question evaluates secure cloud-based architecture on AWS, covering competencies in authentication and authorization, PII handling and auditability, API and data model design, and scalable low-latency market-data retrieval.

    RobinhoodSoftware EngineerSystem DesignTechnical Screen
  • This question tests the ability to design a distributed, fault-tolerant job scheduler that guarantees tasks are executed no more than once, focusing on state management and concurrency control.

    RobinhoodSoftware EngineerSystem DesignOnsite
  • A system design question about building the order execution system for a retail brokerage, where users place market and limit orders and can cancel them. It tests order execution flow, order state transitions with partial fills and cancels, failure handling, tracking user balances, and scaling the design to millions of orders.

    RobinhoodSoftware EngineerSystem DesignOnsite
  • This question tests your ability to design a scalable, low-latency authorization framework and a reliable, tamper-proof audit logging system for a financial platform.

    RobinhoodSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a distributed data processing pipeline that handles large-scale text files by balancing memory constraints, horizontal scalability, and data integrity.

    RobinhoodBackend EngineerSystem DesignTechnical Screen
  • Design a distributed, low-latency rate limiting service capable of enforcing multi-dimensional limits (e.g., by user ID, IP address, and endpoint) across a large-scale gaming platform.

    RobloxSoftware EngineerSystem DesignTechnical Screen
  • Design a scalable social-proof service that tracks unique player counts per experience and computes real-time friend-intersection summaries under high write throughput and low read latency.

    RobloxSoftware EngineerSystem DesignTechnical Screen
  • Design a real-time collaborative to-do list supporting concurrent edits, task reordering, fast write confirmations, and seamless reconnect recovery.

    RobloxSoftware EngineerSystem DesignTechnical Screen
  • Tests a candidate's ability to architect a production-grade, reusable UI component library element with consideration for flexible API design, accessibility (WAI-ARIA), state management, and large dataset performance.

    RobloxFrontend EngineerSystem DesignOnsite
  • This question tests the ability to design a high-throughput, eventually consistent counting system that handles massive concurrent write volumes while maintaining low-latency read access.

    RobloxSoftware EngineerSystem DesignOnsite
  • This question tests your ability to design a high-throughput, distributed service for tracking user engagement, focusing on write-heavy loads and read-consistency trade-offs.

    RobloxSoftware EngineerSystem DesignTechnical Screen
  • This problem tests your ability to design a distributed rate-limiting service that maintains request counts across multiple application nodes while balancing system performance and accuracy.

    RobloxSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates proficiency in designing a reliable, scalable scheduled payment service, testing competencies in distributed systems, API design, scheduling and execution workflows, idempotency and deduplication, time semantics, transactional consistency, security and compliance, and operational monitoring.

    RobloxSoftware EngineerSystem DesignOnsite
  • A system design question about an in-app notification center that turns product events into per-user notifications, shows an unread badge and a recent list, and pushes new items to online users. It tests fan-out strategy, inbox data modeling, unread counts, real-time delivery, reliability, and client design.

    RobloxSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a scalable, low-latency system for managing user-specific lists (favorites) and integrating real-time social signals into a game recommendation engine.

    RobloxSoftware EngineerSystem DesignOnsite
  • Design in-game payment wallet 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.

    RobloxSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's competence in designing scalable, low-latency distributed systems and matchmaking algorithms, including skills in queue management, skill-based matching, regional sharding, SLO-driven latency targets, consistency models, failure handling, and monitoring.

    RobloxSoftware EngineerSystem DesignOnsite
  • This question evaluates system design and distributed-systems competencies including resource management, async concurrency, caching and eviction, streaming and partial loads, dependency resolution, failure isolation, observability, and pub/sub concerns such as topic/schema/versioning, discovery, QoS, ordering, replay, partitioning, latency, clock semantics, and security. Commonly asked to assess architectural reasoning about scalability, low-latency trade-offs, fault tolerance, and deployment/topology choices, it is categorized under System Design and tests both high-level conceptual understanding and practical application-level design decisions; English.

    RobloxSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a low-latency, high-throughput distributed system capable of managing real-time bidding (RTB) auctions for streaming video advertisements.

    RokuBackend EngineerSystem DesignOnsite
  • This problem tests your ability to design a distributed video-on-demand platform, focusing on content ingestion, delivery at scale, and media processing pipelines.

    RokuSoftware EngineerSystem DesignOnsite
  • Architect serving and storage for recommender 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.

    SalesforceSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's ability to design a highly available, scalable emergency-calling platform covering real-time call flow, accurate caller location validation, PSAP routing, interoperability with telephony/SIP providers, and regulatory/security considerations.

    SalesforceSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's competence in designing large-scale analytics backends, covering data ingestion, event and metric schemas, near-real-time and historical analytics, metric computation and slicing, data freshness and deduplication, privacy and access control, operational monitoring, and the API/query layer.

    SalesforceBackend EngineerSystem DesignOnsite
  • Design a distributed order-management system for a multi-location coffee shop chain, focusing on transactional order states, menu snapshotting, idempotent payment processing, and resilient preparation workflows.

    SalesforceSoftware EngineerSystem DesignOnsite
  • Design a concurrent car reservation service with availability search, temporary holds, confirmation, cancellation, and status lookup. Explain interval conflicts, atomic inventory claims, retry safety, hold expiry, stale search results, substitutions, partitioning, and double-booking prevention.

    SalesforceSoftware EngineerSystem DesignOnsite
  • Design a multi-tenant enterprise messaging system with direct messages, multiple channel types, durable history, real-time delivery, offline catch-up, search, presence, and read positions. Explain ordering, permissions, fan-out, storage, and strict tenant isolation.

    SalesforceSoftware EngineerSystem DesignOnsite
  • Design a multi-vendor integration platform for authorized actions and inbound events across providers with different APIs. Define an extensible connector contract, secure credential handling, durable retries, rate isolation, webhook and polling ingestion, deduplication, and schema evolution.

    SalesforceSoftware EngineerSystem DesignOnsite
  • Design the core of a ride-hailing platform, covering driver location ingestion, matching riders with nearby drivers, the offer and acceptance flow with timeouts and reassignment, and surge pricing per area. It tests geospatial indexing, state machines and consistency under concurrent updates.

    SalesforceSoftware EngineerSystem DesignOnsite

More topics