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 91–120 of 1311 results

  • This question evaluates system design and algorithmic skills related to real-time distributed pricing, API and data-flow architecture, carpooling logic, fairness constraints, and experimentation support.

    AmazonSoftware EngineerSystem DesignOnsite
  • This question evaluates cloud systems design competencies including multi-tier network architecture, IP addressing and capacity planning, security controls, centralized server management, shared storage trade-offs, and identity and access integration within a production-scale virtual private cloud.

    AmazonSoftware EngineerSystem DesignTechnical Screen
  • This problem tests your ability to design a resilient database architecture that minimizes downtime and data loss during node failures.

    AmazonSoftware EngineerSystem DesignOnsite
  • This question assesses your ability to design a telemetry and feedback system for an internal developer platform to measure adoption, identify friction points, and drive cross-team migration.

    AmazonSoftware EngineerSystem DesignOnsite
  • This question tests the ability to analyze a distributed system architecture for single points of failure, scalability bottlenecks, and operational risks, while balancing engineering trade-offs.

    AmazonSoftware EngineerSystem DesignOnsite
  • Design an end-to-end distributed metrics collection and monitoring pipeline capable of ingesting millions of data points per second, handling label cardinality risks, and supporting low-latency time-series queries.

    AmperitySoftware EngineerSystem DesignTechnical Screen
  • Design an online service that runs user-submitted SQL statements against data stored in Apache Iceberg tables. Covers the query lifecycle and API, metadata-driven planning with snapshots and manifests, distributed execution, multi-tenant admission control, commits for writes, and table maintenance.

    AmperitySoftware EngineerSystem DesignOnsite
  • This question tests your ability to design a high-security, distributed system for managing digital asset custody, focusing on secure key storage, transaction authorization, and auditability.

    Anchorage DigitalSoftware EngineerSystem DesignOnsite
  • This question evaluates understanding of designing asynchronous, batched request handling in a single-threaded event-loop, covering batching windows, key deduplication, response-to-callback correlation, consistency boundaries, error handling, timeouts/retries, cancellation, and backpressure.

    AnrokSoftware EngineerSystem DesignTechnical Screen
  • Design a high-throughput, fault-tolerant artifact distribution system to deploy a 500 GB large language model across thousands of GPU worker nodes under strict time and bandwidth constraints.

    AnthropicMachine Learning EngineerSystem DesignOnsite
  • This question evaluates a candidate's ability to design and implement a Python-based solution within a cloud-hosted notebook environment, covering requirements elicitation, component and data-structure selection, modularization, testing, dependency and environment management, and basic performance analysis.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design Web-only one-to-one messaging at 100 million DAU with durable deduplication, chat sharding, membership indexes, offline recovery, and replica-aware reads.

    AnthropicSoftware EngineerSystem DesignTechnical Screen
  • Design a scalable social media platform supporting photo uploads, timeline feed generation, follow graphs, and friend recommendations. This problem tests distributed storage, feed fan-out strategies under skewed follower distributions, and graph-based recommendation systems.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a high-throughput, fault-tolerant distribution platform that transfers multi-hundred-gigabyte model weights to tens of thousands of GPU worker nodes with integrity validation, progressive rollouts, and fast rollback capabilities.

    AnthropicSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates expertise in designing scalable, real-time one-to-one messaging systems, testing knowledge of distributed systems principles, message persistence and retrieval, delivery semantics, session and WebSocket management, ordering, retries, deduplication, and trade-offs between streaming and in-memory technologies such as Kafka and Redis. It is commonly asked to assess architectural reasoning about latency, availability, ordering guarantees and reliability within the System Design domain, and requires a mix of conceptual architectural understanding and practical implementation-level considerations.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design an internal peer-to-peer artifact distribution system to deliver large model weights from a single seed machine to thousands of cluster workers subject to a shared aggregate upload-and-download network link limit.

    AnthropicSoftware EngineerSystem DesignTechnical Screen
  • Design a scalable telemetry ingestion pipeline that standardizes and reconciles metric naming inconsistencies and schema drift across disparate client libraries, historical stores, and real-time query engines.

    AnthropicSoftware EngineerSystem DesignTechnical Screen
  • A system design question on serving large language model inference by batching requests, given the interviewer's assumption that every batch finishes in 100 ms. It tests batching policy, capacity math, latency budgets, returning results to callers, failure handling, and whether a fixed batch time holds when prompt and response lengths vary.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a collaborative prompt playground with conflict-aware editing, immutable versions, asynchronous model runs, and reliable input and result provenance.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a resilient, distributed image-processing pipeline that safely scales from a single worker to hundreds of concurrent nodes while guaranteeing job lease safety, idempotent output writes, and clean cancellation.

    AnthropicSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's competency in designing a crash-resilient LRU cache, including which data and ordering must be persisted, durability and recovery concerns, and trade-offs between latency and persistence.

    AnthropicSoftware EngineerSystem DesignTechnical Screen
  • Tests the candidate's ability to design a low-latency, highly available distributed rate-limiting service that coordinates shared state across geographically distributed API gateways while gracefully handling network partitions and datastore failures.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a scalable, multi-tenant LLM inference serving platform that balances Time-to-First-Token (TTFT) and throughput using dynamic iteration-level batching, KV cache memory management, and strict admission control.

    AnthropicMachine Learning EngineerSystem DesignOnsite
  • A system design interview question that asks you to design an inference API for a trained model served on GPUs, covering the public API, streamed responses, request queueing, scheduling onto GPU workers, overload handling and failure recovery. Follow-up questions probe how to raise GPU throughput and memory efficiency without missing latency targets.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a highly available, low-latency one-on-one messaging system capable of delivering messages in real time, maintaining strict ordering, and handling offline synchronization.

    AnthropicSoftware EngineerSystem DesignTechnical Screen
  • Design a parallel model downloader with version-bound byte ranges, resumable verified pieces, bounded resource use, and atomic publication of complete artifacts.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a resilient, distributed 1:1 and group messaging system focusing on durability guarantees, strict message ordering, robust fan-out, and reliable offline catch-up under partial failures.

    AnthropicSoftware EngineerSystem DesignTechnical Screen
  • Design a game launcher's patch downloader that fetches a multi-gigabyte update in parallel byte-range chunks, survives crashes and connection drops without re-downloading verified bytes, and only ever exposes a complete, verified patch to the game client.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a node-side fetcher that downloads multi-terabyte dataset releases in parallel byte ranges, resumes from verified pieces after crashes, and atomically publishes only complete releases. Tests manifest design, range-request validation, durable progress tracking, and atomic filesystem publication.

    AnthropicSoftware EngineerSystem DesignOnsite
  • Design a team tool where engineers co-edit a shared collection of HTTP request templates, freeze them into immutable versions, and execute versions asynchronously against third-party APIs with full provenance of inputs, config, and results.

    AnthropicSoftware EngineerSystem DesignOnsite

More topics