Topic
System Design interview questions
1311 System Design questions from 230 companies, with hints, runnable code and solution walkthroughs.
60 easy819 medium432 hard
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
Most mentioned in interview experiences
- 1.Design delivery driver payment system3 reports
- 2.Debug round-robin request router2 reports
- 3.Design a basic bank system API2 reports
- 4.Design a delivery cost system2 reports
- 5.Design a Distributed Key-Value Store for a Small Company's Internal Use2 reports
- 6.Design a Donation System for a Three-Day Fundraising Campaign2 reports
- 7.Design a file search module like UNIX find2 reports
- 8.Design a Food Review System for a Delivery App, Focused on the Database Schema2 reports
- 9.Design a Job Scheduler for ML Training and Batch Inference on a Shared Cluster2 reports
- 10.Design a Menu Item Review and Rating System for a Food-Delivery Platform2 reports
Counted from 393 candidate interview experiences on Katkat. How we collect and count
Showing 1231–1260 of 1311 results
This problem tests the ability to design a scalable, low-latency leaderboard system that handles high-frequency write throughput from reviews and supports read-heavy leaderboard queries.
UberSoftware EngineerSystem DesignOnsiteThis question tests the ability to design a distributed, low-latency, and fault-tolerant shopping cart service for a high-concurrency food delivery platform.
UberSoftware EngineerSystem DesignOnsiteThis problem evaluates your ability to design a distributed system that manages real-time interactions between three distinct user types: customers, restaurants, and couriers, with a focus on geospatial querying and high-concurrency event streaming.
UberSoftware EngineerSystem DesignTechnical ScreenThis question tests your ability to design a distributed, highly available system that handles high-read traffic and ensures data integrity for short-URL mappings.
UberSoftware EngineerSystem DesignOnsiteThis question tests the ability to design a highly available and scalable real-time chat service, focusing on persistent connections, message routing, and reliable delivery mechanisms.
UberSoftware EngineerSystem DesignOnsiteTests the ability to architect a high-throughput, low-latency geospatial ingestion and query service that tracks millions of moving entities, handles state transitions, and avoids boundary/hot-spot bottlenecks.
UberSoftware EngineerSystem DesignOnsiteThis problem tests your ability to design a distributed calendar system, focusing on data modeling for recurring events, time zone handling, and frontend state management for a high-concurrency scheduling UI.
UberFrontend EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's competency in large-scale system design, covering distributed systems architecture, data modeling, real-time location streaming, matching algorithms, scalability, fault tolerance, and secure payment handling.
UberSoftware EngineerSystem DesignOnsiteThis system design question evaluates the ability to architect a large-scale search autocomplete service, testing knowledge of prefix data structures, distributed indexing, and latency-sensitive serving pipelines. It is commonly asked in senior engineering interviews to assess trade-off reasoning between freshness, read performance, and system complexity at scale.
UberSoftware EngineerSystem DesignOnsiteThis question evaluates object-oriented system design and domain modeling skills related to cart operations, item customizations, composable pricing rules (surge, promotions, membership) and producing an itemized receipt.
UberSoftware EngineerSystem DesignOnsiteThis question evaluates system design and backend engineering competencies, focusing on data modeling, indexing strategy, concurrency control, transactional correctness, and scalability for a multi-device cart lifecycle and one-time checkout.
UberSoftware EngineerSystem DesignTechnical ScreenThis interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design driver heat map and discuss consensus states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
UberSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's ability to design real-time distributed systems for geospatial aggregation, covering skills in spatial partitioning, high-throughput streaming ingestion, low-latency cell counting, WebSocket-based client updates, and top-K ranking within a fault-tolerant multi-region architecture.
UberSoftware EngineerSystem DesignOnsiteA system design interview question asking you to design the data flow behind a food delivery app's restaurant list for a customer's delivery address. It tests geographic indexing of delivery areas, propagating restaurant status and delivery-time changes, read-path latency, caching, and freshness trade-offs.
UberSoftware EngineerSystem DesignOnsiteDesign how to store and check which people can access which resources using a graph database, including the vertex and edge schema, access-check traversals, and scaling with caching and partitioning. It also covers migrating from the existing database without downtime, testing access modeling, bounded traversals and safe data migration.
UberSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's ability to design a real-time room allocation and ranking service in the System Design domain, testing competencies in architectural design, ranking and scoring functions, data sourcing and freshness, fairness mechanisms, and online evaluation and experimentation.
UberSoftware EngineerSystem DesignOnsiteA system design interview question asking you to design a distributed URL shortener. It tests API design, unique short-code and distributed ID generation, collision handling, storage and sharding, caching for very high redirect traffic, availability, fault tolerance, and link expiration.
Uber FreightSoftware EngineerSystem DesignOnsiteThis problem tests the ability to design a distributed, low-latency analytics pipeline capable of handling high-throughput event ingestion, time-windowed aggregations, and efficient cache retrieval.
Uber FreightSoftware EngineerSystem DesignOnsiteThis question evaluates proficiency in database design and consistency concepts, covering competencies such as data modeling, datastore selection, partitioning and indexing strategies, consistency semantics, operational trade-offs, validation and testing, and privacy/compliance considerations.
UiPathSoftware EngineerSystem DesignTechnical ScreenA systems-design interview about correct stateful processing for sparse records, out-of-order loan events, investor payment allocation, and authenticated APIs. It emphasizes idempotency, ledgers, exact arithmetic, recovery, and auditability.
ValonBackend EngineerSystem DesignOnsiteSystem design question about a loan system in which borrowers make repayments and the investors who own the loans are paid on a schedule. It tests loan and ownership modeling, repayment allocation, exact ledger accounting, idempotent payout runs, cent-level splitting among investors, and handling of payments reversed after a payout.
ValonSoftware EngineerSystem DesignOnsiteA Vanta software-engineer system-design interview question: design a scalable pipeline to compute and serve DAU and MAU engagement metrics for a large consumer app. It tests event ingestion, identity and de-duplication, exact vs. approximate distinct counting (HyperLogLog/bitmaps), handling of time zones and late/out-of-order events, streaming-vs-batch correctness, dashboard serving, and monitoring/privacy.
VantaSoftware EngineerSystem DesignOnsiteDesign web metrics around precise view, URL, identity, cohort, and conversion definitions with durable aggregation and late-event handling.
VantaSoftware EngineerSystem DesignOnsiteThis question tests your ability to design a distributed system capable of handling concurrent, low-latency document edits using conflict resolution strategies.
VercelSoftware EngineerSystem DesignOnsiteDesign a service that turns long URLs into short, shareable links and redirects visitors to the original destination with minimal latency. Tests capacity estimation, collision-free code generation under concurrent writes, a read-optimized data model, and how to scale and harden the redirect path.
VercelSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's competency in designing scalable, near-real-time monitoring systems, covering high-throughput heartbeat ingestion, compact per-device state management, detection of missing events, and handling duplicates, late arrivals, and ordering issues.
VerkadaSoftware EngineerSystem DesignTechnical ScreenThis problem tests the ability to design a high-throughput ingestion system and a real-time state management strategy for time-sensitive IoT heartbeats.
VerkadaSoftware EngineerSystem DesignTechnical ScreenThis interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Design camera access-control service states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
VerkadaSoftware EngineerSystem DesignTechnical ScreenThis question tests the ability to design a distributed system capable of aggregating real-time device heartbeat events into status counts while handling event-time latency and fault tolerance.
VerkadaSoftware EngineerSystem DesignTechnical ScreenDesign a fault-tolerant, distributed system to transpose massive matrices that exceed single-machine memory using block tiling, idempotent worker execution, and completion tracking.
VerkadaSoftware EngineerSystem DesignTechnical Screen