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 451–480 of 1311 results
This question evaluates a candidate's competency in designing and operating a monolithic application on Kubernetes, covering platform engineering topics such as deployment topology, networking and traffic management, CI/CD and rollout strategies, resource management and autoscaling, stateful dependencies, observability, incident response, and disaster recovery. Commonly asked in System Design interviews to assess practical application of distributed systems and SRE principles—specifically the ability to reason about operational trade-offs, reliability, and incremental migration paths—this prompt sits in the System Design domain and emphasizes practical application with architectural reasoning rather than purely conceptual understanding.
FigmaSoftware EngineerSystem DesignHR ScreenThis question tests the ability to design an end-to-end data pipeline architecture that ensures high-fidelity telemetry collection, automated quality validation, and safe release orchestration for embedded firmware devices.
FigureaiData EngineerSystem DesignTechnical ScreenThis question tests your ability to design a high-throughput, fault-tolerant telemetry ingestion pipeline capable of handling high-velocity data streams from distributed robotic systems.
FigureaiData EngineerSystem DesignTechnical ScreenDesign a simplified WhatsApp focused on sending and receiving messages: the online and offline delivery flow, client APIs, the database schema, and scaling. It tests connection routing, delivery guarantees and ordering, and a choice between relational and NoSQL storage justified by access patterns.
FivetranSoftware EngineerSystem DesignTechnical ScreenDesign a shipment-planning and container-packing service that assigns cargo items to ocean containers subject to physical dimensions, weight limits, and hazardous/incompatibility rules while supporting async workflows and plan approvals.
FlexportSoftware EngineerSystem DesignOnsiteThe question evaluates distributed-systems and scalability competencies for globally unique 64-bit ID generation (including sharding, time-ordering, fault tolerance and clock issues) as well as object-oriented design, concurrency control, API design, and data modeling for a parking lot backend.
FlipsterSoftware EngineerSystem DesignTechnical ScreenA system design question asking you to design a distributed job scheduler that runs jobs immediately, at a set time or on a recurring cron schedule across a pool of workers. It tests how you find due jobs at scale, prevent duplicate runs, recover from worker failures, and handle retries, bursts and missed runs.
FluidstackSoftware EngineerSystem DesignTechnical ScreenDesign a centralized scheduling and execution platform for one-off ML training jobs across a shared, heterogeneous GPU cluster, balancing fair resource sharing, multi-GPU network topology, and fault tolerance.
FluidstackSoftware EngineerSystem DesignOnsiteDesign a high-throughput caching and inventory architecture for a hotel booking platform that accelerates read-heavy search traffic while strictly preventing overselling through temporary holds and authoritative consistency.
Fora TravelSoftware EngineerSystem DesignOnsiteThis question evaluates system design and engineering competencies related to large-scale, real-time notification systems, including distributed systems architecture, messaging and delivery mechanisms, data modeling, API design, scalability, reliability, security, and monitoring.
Fora TravelSoftware EngineerSystem DesignOnsiteTests the ability to design an end-to-end location ingestion and geo-fenced notification system, focusing on spatial indexing, staleness filtering, scalable fan-out, and hotspot mitigation.
Fora TravelSoftware EngineerSystem DesignTechnical ScreenDesign a relational schema and REST API for a three-tiered learning curriculum (Tracks, Modules, Lessons) supporting drag-and-drop reordering, transactional updates, and versioned caching.
Fora TravelSoftware EngineerSystem DesignOnsiteThis question evaluates skills in designing real-time telemetry systems, including vehicle data collection and transmission, backend ingestion and validation, API and frontend design, operational controls for per-vehicle data flow, and the incorporation of AI-assisted development into the engineering process.
FordSoftware EngineerSystem DesignTechnical ScreenPrepare for a Fuse Energy system design interview about design a fitness activity tracking app with followers and leaderboards. This question focuses on requirements, architecture, trade-offs, reliability, and follow-up discussion areas.
Fuse EnergySoftware EngineerSystem DesignOnsiteDesign a concurrent healthcare appointment scheduling system that prevents double booking, supports fast availability searches, and ensures reliable notifications and state auditability.
Garner HealthSoftware EngineerSystem DesignTechnical ScreenDesign a doctor appointment system with searchable availability, atomic booking, cancellation, and protection against double booking. The follow-up examines a vaccine-demand spike through waiting-room admission, fairness, throttling, hot-slot partitioning, caching, autoscaling, load shedding, and reconciliation.
Garner HealthSoftware EngineerSystem DesignTechnical ScreenCompare monolithic and service-based architectures and plan incremental extraction or consolidation around domain boundaries, data ownership, and measured goals.
GeneralmotorsSoftware EngineerSystem DesignTechnical ScreenAn open-ended design discussion about an application that calls three to five dependent services and must keep latency under 10 seconds and availability at 99% or better. It tests objective definitions, availability and tail-latency math, timeouts, retries, fallbacks, and adapting as requirements change.
GeneralmotorsSoftware EngineerSystem DesignOnsiteDesign real-time typeahead for an enterprise search product that suggests past searches, people, documents, apps and filters as the user types. Tests client request policy and stale-response handling, accessible combobox UI, permission-aware backend fan-out, blending across sources and latency budgets.
GleanFrontend EngineerSystem DesignOnsiteDesign a scalable text sharing (Pastebin) service that generates unique short URLs for submitted text snippets. This question assesses API design, data modeling, storage decoupling, key generation strategies, and caching mechanisms under high read concurrency.
Goldman SachsSoftware EngineerSystem DesignOnsiteDesign the backend of a dashboard that shows metrics computed from a continuous event stream and lets users query any time range. The discussion focuses on answering range queries from pre-aggregated data and on how watermarks decide when event-time windows are complete despite late or out-of-order events.
Goldman SachsSoftware EngineerSystem DesignOnsiteDesign a high-throughput, low-latency in-memory deduplication service that identifies and suppresses duplicate notifications within a 10-minute sliding window.
Goldman SachsSoftware EngineerSystem DesignOnsiteA system design exercise for ingesting recorded Zoom meetings into a business product and processing them into transcripts and conversation analysis. It tests reliable ingestion despite missed notifications, rate-limited fetching, staged idempotent processing on costly compute, fairness between customers, reprocessing, and data deletion.
GongSoftware EngineerSystem DesignOtherA system design exercise for a service that finds times when a group of people is free, using calendars synced from external providers. It tests computing common free time correctly across time zones, keeping availability fresh within rate limits, preventing double bookings, and scaling queries and public booking pages.
GongSoftware EngineerSystem DesignOtherDesign a distributed storage quota accounting and enforcement service for a cloud drive platform that handles concurrent multi-part uploads, deletions, retries, and usage drift reconciliation.
GoogleSoftware EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's competence in designing scalable calendar event and conflict-handling systems, focusing on data modeling, time semantics (time zones and recurrence), concurrency control, and distributed-system trade-offs, and falls under the System Design domain.
GoogleSoftware EngineerSystem DesignOnsiteA system design question about an e-commerce platform that ingests customer reviews and uses an LLM to summarize them for an internal dashboard. It probes the ingestion and summarization pipeline, trust and safety filtering, data sanitization and PII redaction, and defenses against prompt injection hidden in review text.
GoogleSoftware EngineerSystem DesignOnsiteDesign a distributed rate limiter and quota enforcement service tailored for AI agent workloads where consumption is measured in variable billing tokens rather than fixed request counts.
GoogleSoftware EngineerSystem DesignOnsiteDesign a continuous integration system that builds a change and runs about one million tests within a ten-minute budget. Tests capacity estimation, sharding and scheduling by test duration, artifact distribution, caching and test selection, flaky tests, failure handling, and cost versus latency trade-offs.
GoogleSoftware EngineerSystem DesignOnsiteDesign a collaborative notes backend with CRUD, WebSocket editing, operation logs, snapshots, CRDT or Operational Transformation conflict handling, offline sync, note-based scaling, permissions, and recovery.
GoogleSoftware EngineerSystem DesignOnsite