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 271–300 of 1311 results

  • This question evaluates a data engineer's competency in business analytics, unit-economics P&L modeling, risk-versus-revenue trade-off analysis, and experiment-driven evaluation of credit product changes.

    Capital OneData EngineerSystem DesignTechnical Screen
  • This question evaluates understanding of virtual credit card product trade-offs and the ability to design data models and deterministic validation logic for encoded transaction attributes, testing competencies in payment systems, data encoding/decoding, and rule-based validation.

    Capital OneMachine Learning EngineerSystem DesignOnsite
  • This question evaluates system design and backend engineering skills, including API design, data modeling for time-series attendance, payroll computation logic, consistency guarantees, integration/synchronization with external sources, and strategies for handling high-volume, bursty traffic.

    CarvanaSoftware EngineerSystem DesignOnsite
  • This question evaluates understanding of data modeling for multi-tag messages, set-based subscription semantics, scalable system design, and algorithmic complexity for operations such as enqueue, dequeue, subscribe/unsubscribe, and intersection queries.

    CerebrasSoftware EngineerSystem DesignTechnical Screen
  • Design a semantic caching and computation deduplication system that identifies similar inputs, prevents duplicate expensive processing under concurrent load, and maintains consistent, versioned outputs.

    Charta HealthSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a high-throughput, low-latency risk engine capable of atomic exposure validation before orders reach an exchange, while balancing concurrency and strict fault tolerance.

    Chicago Trading CompanySoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's competency in designing scalable, reliable backend architectures, specifically focusing on load balancing strategies, multi-layer caching, and idempotent API design.

    ChimeSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's ability to design end-to-end, production-grade mobile check deposit systems, assessing competencies in system architecture, distributed systems, security and fraud prevention, regulatory compliance (Reg CC, Check 21), data durability, and operational observability.

    ChimeSoftware EngineerSystem DesignOnsite
  • This 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 banking payment scheduling system states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    CircleSoftware EngineerSystem DesignOnline Assessment
  • Design flight-price search service 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.

    CircleSoftware EngineerSystem DesignOnline Assessment
  • A Circle software-engineer take-home: design a versioned in-memory key→(field→value) database with per-field TTL, append-only history and delete tombstones, lexicographically ordered scan and scanPrefix (correct even with special characters), and snapshot backup/restore counters. It exercises data modeling, time-travel visibility semantics, ordered indexing, garbage collection, and per-operation complexity trade-offs.

    CircleSoftware EngineerSystem DesignOnline Assessment
  • A practical curl interview question on tracing and reducing redundant HTTP requests: instrumenting a curl-based client, finding duplicate calls, and cutting request volume. Includes a full worked solution.

    CircleSoftware EngineerSystem DesignOnline Assessment
  • Design e-commerce inventory availability and order reservation without overselling under concurrent requests. Define on-hand, reserved, and available invariants; atomic multi-item placement; idempotent retries; expiration; and optimistic versus pessimistic control for hot SKUs.

    CitadelSoftware EngineerSystem DesignTechnical Screen
  • Design a course registration system with relational models and APIs for enrollment, dropping, schedules, waitlists, and course browsing. The solution explains transactional capacity protection, idempotent retries, re-enrollment without duplicate rows, FIFO promotion, outbox notifications, and tests for final-seat races.

    CitadelSoftware EngineerSystem DesignOnsite
  • Design a high-throughput, multi-tenant metrics ingestion and alerting engine capable of triggering critical alerts within two seconds. The question evaluates your knowledge of streaming architectures, time-series storage, cardinality management, and fault-tolerant notification delivery.

    CitadelSoftware EngineerSystem DesignOnsite
  • This question tests the ability to architect a high-throughput, sub-millisecond trading system while balancing strict deterministic latency requirements with necessary safety checks.

    CitadelSoftware EngineerSystem DesignOnsite
  • This question evaluates expertise in designing low-latency, high-determinism electronic trading systems, covering order matching, market data ingestion and publish, partitioning/sharding, persistence for auditability, idempotency, pre-trade risk controls, and operational reliability.

    CitadelSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates understanding of real-time stream processing, alerting policy design, and distributed state coordination for application-to-exchange mappings, testing competencies in scalability, correctness under partitioning and duplication, and efficient aggregation of high-volume event streams.

    CitadelSoftware EngineerSystem DesignOnsite
  • Design an authenticated online shopping service with secure signup and login, user-owned carts, product browsing, and retry-safe order creation. The solution covers password hashing, session rotation, CSRF defenses, resource-level authorization, idempotency keys, immutable order snapshots, recovery tokens, and horizontal-access tests.

    CitadelSoftware EngineerSystem DesignOnsite
  • This question evaluates understanding of distributed messaging systems, delivery semantics, push versus pull consumption models, NoSQL versus relational storage trade-offs, and concurrency control including deadlock concepts.

    CitadelSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's understanding of operating system and networking fundamentals, covering processes, threads and context switching, concurrency versus parallelism, TCP/UDP and flow versus congestion control, and the end-to-end web request and browser rendering pipeline.

    CitiSoftware EngineerSystem DesignOnsite
  • This question evaluates understanding of scalable system architecture, integration with external ML services, handling rate limits, reliable scheduling and delivery, data modeling for aggregation and deduplication, and fault-tolerant ranking under load.

    ClickupSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's competency in designing real-time backend systems, emphasizing concurrency control, stateful resource allocation, time-sensitive freshness constraints, efficient eviction policies, and action logging.

    CloudKitchensSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a distributed, high-throughput ingestion pipeline that ensures log confidentiality and integrity using encryption at rest and in transit.

    CloudflareSoftware EngineerSystem DesignOnsite
  • A choose-your-own system design round: present a core project you owned end to end at a previous job, then defend its architecture, technology choices and hardest challenges under detailed probing. Tests depth of ownership, trade-off reasoning and the ability to move from a diagram to concrete mechanisms.

    Cockroach LabsSoftware EngineerSystem DesignOnsite
  • Design enterprise AI question answering across internal and external sources with permission-aware retrieval, entity mapping, evidence-grounded synthesis, and freshness controls.

    CohereSoftware EngineerSystem DesignTechnical Screen
  • Design optimistic real-time comments with temporary identities, idempotent posting, response/event reconciliation, visible failure states, and durable history.

    CohereFrontend EngineerSystem DesignOther
  • Front-end system design for a real-time comment feed, centered on optimistic updates: a new comment is appended to the list before the backend confirms it, so the user can keep typing. It tests client state modeling, reconciliation with live echoes, failure and retry handling, ordering, reconnection and rendering performance.

    CohereFrontend EngineerSystem DesignOnsite
  • This question evaluates a candidate's ability to architect distributed, low-latency, and fault-tolerant order-placement and routing systems for cryptocurrency trading, covering consistency guarantees, external integration with heterogeneous venue protocols, fund reservation, execution reconciliation, and auditability.

    CoinbaseSoftware EngineerSystem DesignOnsite
  • This question evaluates competency in frontend architecture for real-time trading UIs, covering state management, rendering strategies, real-time data flow, performance, reliability, security, testing, and observability.

    CoinbaseFrontend EngineerSystem DesignOnsite

More topics