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 121–150 of 1311 results
Design a multi-user SQL workbench where analysts co-edit drafts, freeze immutable snapshots, and launch long-running warehouse queries whose results stay traceable to their exact inputs. Tests concurrency control, immutability boundaries, and reliable async execution.
AnthropicSoftware EngineerSystem DesignOnsiteDesign a telemetry pipeline that ingests metrics from a large fleet of deployed clients, then handle legacy clients that cannot be updated and report the same metric under inconsistent names. It tests durable ingestion, stream processing and storage design, canonical metric catalogs, version-scoped name mapping and schema evolution.
AnthropicSoftware EngineerSystem DesignOnsiteDesign a hosted translation API where a GPU worker runs one batch of pending requests every fixed round, and the candidate must derive throughput, batch-closing policy, and failure handling from that one constraint.
AnthropicSoftware EngineerSystem DesignOnsiteAn Anthropic system design question: design and implement a concurrent web crawler, from a single-threaded baseline to manual threads, a thread pool and asyncio. It covers the URL frontier, deduplication across workers and redirects, robots.txt and per-host politeness, Retry-After backoff, completion detection, memory sizing, testing and monitoring.
AnthropicSoftware EngineerSystem DesignTechnical ScreenThis question tests the ability to design a scalable, fault-tolerant distributed web crawler that handles URL management, distributed coordination, and domain politeness.
AnthropicSoftware EngineerSystem DesignTechnical ScreenThis problem tests your ability to design a scalable, real-time one-to-one messaging system by addressing requirements for message ordering, delivery guarantees, and user presence.
AnthropicSoftware EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's competency in large-scale system design, real-time streaming and prompt execution, multi-tenant data modeling, versioning and collaboration workflows, security and privacy controls, observability and cost tracking, and abuse prevention.
AnthropicSoftware EngineerSystem DesignOnsiteThis question assesses the ability to design a scalable content-sharing platform, focusing on data modeling, efficient retrieval of user-generated prompts, and the handling of concurrent access and permissions.
AnthropicSoftware EngineerSystem DesignTechnical ScreenDesign a scalable MapReduce pipeline 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.
AnthropicMachine Learning EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's ability to design a scalable, highly available network I/O backend, testing competencies in distributed systems, storage architecture, CDN and caching integration, API and data model design, capacity planning, failure handling, observability, and security.
AnthropicSoftware EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's ability in large-scale distributed system design, performance modeling, capacity planning, and operational reliability for latency-sensitive, multi-region key-value services.
AnthropicMachine Learning EngineerSystem DesignOnsiteThe prompt evaluates competence in large-scale distributed system design, covering storage architecture, consistency and replication strategies, caching, APIs and data models, operational reliability, security, and cost/capacity planning.
AnthropicSoftware EngineerSystem DesignTechnical ScreenA system design interview to build an LLM prompt playground where users write, run, save and share prompts, starting from the database schema. Follow-ups probe storing very large prompts, designing sharing, and handling frequent one- or two-character edits to a large prompt without wasting storage.
AnthropicSoftware EngineerSystem DesignOnsiteDesign the serving path for a code-completion model whose accelerators run requests in batches. The interviewer says one batch always takes a fixed 250 ms. Tests batching policy, capacity math, latency budgets, routing results back to callers, failure handling, and questioning the fixed-latency assumption.
AnthropicSoftware EngineerSystem DesignOnsiteThis question evaluates skills in distributed systems and large-scale analytics, covering data partitioning, streaming and sliding-window processing, quantile and heavy-hitter summarization, fault tolerance, and trade-off analysis for time, space, and network I/O.
AnthropicSoftware EngineerSystem DesignOnsiteDesign an end-to-end safety and reliability middleware layer for a production LLM service, focusing on low-latency input/output guardrails, early streaming interception, multi-tier fallback strategies, and observability.
AnthropicSoftware EngineerSystem DesignOnsiteThis question evaluates system design and distributed storage competencies, focusing on scalable file deduplication, content-defined chunking, metadata and index design, multi-tenant architectures, and operational reliability across regions.
AnthropicSoftware EngineerSystem DesignTechnical ScreenCopy 500 GB of model weights to 100 to 1,000 GPU workers whose 10 Gbps links are shared between upload and download. Derive the lower bound on distribution time, evolve a naive fan-out into a chunked peer-to-peer design, and handle stragglers, failures and cutover. It tests bandwidth reasoning and large-scale distribution design.
AnthropicSoftware EngineerSystem DesignOnsiteDesign an exact distributed mode-finding algorithm across partitioned workers that minimizes network I/O, prevents hotspotting, handles deterministic tie-breaking, and contrasts with approximate streaming sketches.
AnthropicSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's competency in low-level performance engineering and compiler optimization techniques—covering pragmas, intrinsics, manual code transformations, profiling and correctness verification—within the System Design and compiler-aware optimization domain.
AnthropicSoftware EngineerSystem DesignOnsiteDesign a high-throughput distribution system to broadcast a large file (e.g., 100 GB model checkpoint) to 1,000 cluster hosts in minimum time, analyzing network bottlenecks and replication topologies.
AnthropicSoftware EngineerSystem DesignOnsiteThis problem evaluates your ability to design a distributed, fault-tolerant batch processing system for high-throughput image transformation tasks.
AnthropicSoftware EngineerSystem DesignTechnical ScreenThis question evaluates understanding of system design and practical engineering competencies required for building resilient file deduplication tools, covering filesystem semantics, error handling, hashing and collision considerations, concurrency, performance bottlenecks, cross-platform interoperability, and safety trade-offs.
AnthropicSoftware EngineerSystem DesignTechnical ScreenThis question evaluates understanding of the MapReduce programming model and distributed batch processing at scale. It tests practical knowledge of parallel efficiency, network bottleneck analysis, and optimization techniques like combiners, partitioning, and speculative execution — core competencies assessed in machine learning and data engineering roles.
AnthropicMachine Learning EngineerSystem DesignTechnical ScreenThis question evaluates performance engineering and low-level kernel optimization competencies, including profiling, data-layout and instruction-level techniques, correctness verification, and benchmark-driven measurement within the System Design domain.
AnthropicSoftware EngineerSystem DesignOnsiteReview a design document for a batched GPU inference API and find its flaws in load balancing, batching, caching, retries and admission control. Then compare theoretical and achievable throughput at 100 ms per batch and 10,000 QPS, and schedule a large and a small model on one 8-GPU pool.
AnthropicSoftware EngineerSystem DesignOnsiteThis question evaluates system design and concurrent programming competencies, focusing on bounded thread-pool architecture, thread-safe frontier and deduplication structures, per-host politeness and in-flight limits, reliability mechanisms (timeouts, retries, backoff), and graceful shutdown and termination semantics.
AnthropicSoftware EngineerSystem DesignTechnical ScreenThis question evaluates proficiency in VLIW instruction scheduling, pipeline hazard analysis (RAW/WAR/WAW), register-pressure management, and software-pipelining for loop kernels within the System Design domain of computer architecture and compiler backends.
AnthropicSoftware EngineerSystem DesignOnsiteFigure out the theoretical floor on how fast a large search-index snapshot can reach every node in a fleet given each machine's shared upload/download bandwidth, then design a chunked, peer-assisted distribution scheme that approaches that floor and copes with stragglers and failures. Tests bandwidth reasoning and evolving a design from a naive baseline.
AnthropicSoftware EngineerSystem DesignOnsiteDesign a service that accepts JSON requests containing a target URL, a UTC timestamp and a payload, stores them durably, and sends each payload to its URL at the scheduled time. It tests finding due work at scale, delivery guarantees and retries, isolation from slow endpoints, outbound-request security and failure recovery.
AnyscaleSoftware EngineerSystem DesignOnsite