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 541–570 of 1311 results
This question evaluates a candidate's ability to design scalable, reliable data ingestion and delivery systems, covering competencies such as scheduling and crawling, data normalization, storage schema design, idempotent ingestion, rate limiting, retries, and monitoring.
HubSpotSoftware EngineerSystem DesignOnsiteThis 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 Schedule and execute future payments states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
HubSpotSoftware EngineerSystem DesignOnline AssessmentAn IBM software-engineer take-home that asks you to design and implement a multithreaded CPU version of valid 1D convolution across three regimes: a tiny kernel (K=3), a kernel as long as the input (K=N, a single dot product), and a 100-thread cap. It evaluates parallel decomposition, scheduling, cache locality, false-sharing avoidance, SIMD vectorization, and reduction/synchronization choices.
IBMSoftware EngineerSystem DesignOnline AssessmentThis question tests the ability to design a distributed system that reliably replicates data from a primary database to multiple cloud providers while exposing a unified, secure API gateway for external consumers.
IllumioSoftware EngineerSystem DesignOnsiteThis problem tests the ability to architect a high-throughput, horizontally scalable system for time-series data, balancing ingest performance with efficient range-query capability.
IllumioSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's ability to design in-memory data models, concurrency control mechanisms, and temporal reservation logic for booking systems.
ImcSoftware EngineerSystem DesignTechnical ScreenDesign idempotent library notifications for upcoming and current due dates plus FIFO hold availability. Use stable business-event identities, transactional scheduling, atomic recipient claims, state rechecks, retries, reconciliation, and clear frontend distinctions among holds, offers, and checkouts.
InstacartBackend EngineerSystem DesignOnline AssessmentDesign asynchronous in-app availability alerts and due-date reminders with Celery, Redis, durable idempotency, versioned schedules, and crash recovery.
InstacartSoftware EngineerSystem DesignOnline AssessmentA system design question about an inventory management service that reserves stock while customers check out. It tests how a candidate prevents overselling under concurrent updates, handles hot SKUs, manages reservation expiry and idempotency, and supports partial fulfillment of multi-item orders.
InstacartSoftware EngineerSystem DesignOnsiteA system design discussion of an inventory service that reserves stock for orders, centered on reservations, concurrent updates and preventing overselling. It probes how stock and holds are modeled, how a reservation stays atomic under contention, how abandoned holds are released and how hot items scale.
InstacartSoftware EngineerSystem DesignTechnical ScreenThis question evaluates competency in system design, data modeling, distributed consistency, concurrency control, API design, idempotency, and scalability for backend inventory and reservation workflows.
InstacartSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's competency in designing inventory and distributed systems, covering stock tracking models, reservation and commit semantics, concurrency control, data modeling, API design, and real-time integrations.
InstacartSoftware EngineerSystem DesignHR ScreenDesign a strongly consistent micro-fulfillment (dark-store) inventory system that handles reservations, stock reconciliation, and idempotent retries, alongside a zero-downtime deployment strategy.
InstacartSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's ability to design a multi-tenant cloud storage system, testing competencies in API design, quota accounting, compression strategies, distributed storage architecture (partitioning, replication/erasure coding), consistency models, security, versioning, and observability.
InstacartSoftware EngineerSystem DesignOnline AssessmentThis 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 product catalog service states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
InstacartSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's ability to design scalable, highly available distributed systems with robust concurrency control and consistency reasoning, covering architecture, data modeling, caching, message-based integration, and operational concerns like observability and disaster recovery.
InstacartSoftware EngineerSystem DesignOnsiteDesign a high-throughput inventory reservation system that locks stock when items are added to a cart, prevents overselling during flash promotions, handles automatic reservation expiration, and scales seamlessly under a 10x traffic spike.
InstacartSoftware EngineerSystem DesignOnsiteTroubleshoot a production incident end-to-end 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.
InstacartSoftware EngineerSystem DesignOnsiteSystem design deep dive on scaling a service built earlier in the same interview loop. Compare schema options, extend the data model for reviews, ratings, and keyword search, and reason about query performance, indexing, pagination, and when a dedicated search engine is worth adding.
IntuitSoftware EngineerSystem DesignOnsiteDesign a secure, enterprise-grade file transfer service that supports resumable multi-gigabyte uploads/downloads alongside fine-grained, token-based authorization and key management.
J.P. MorganSoftware Engineer IISystem DesignOnsiteA high-level design question on a rate limiter that compares common limiting algorithms and then scales the chosen one across many servers while staying available. It tests trade-off reasoning about accuracy, memory, burst handling, shared state, and what happens when the limiter's own dependencies fail.
J.P. MorganSoftware EngineerSystem DesignOnsiteDesign a reliable bank payment system that remains correct across retries, crashes, duplicate requests, and ambiguous external-rail timeouts. Define idempotent APIs, a durable state machine and ledger, transactional handoff, safe reconciliation, invariant monitoring, auditability, and operator remediation.
J.P. MorganSoftware EngineerSystem DesignOnsiteThis question assesses the ability to design a distributed, asynchronous notification system capable of handling high-throughput multi-channel messaging while maintaining strict delivery guarantees and rate-limiting policies.
J.P. MorganSoftware EngineerSystem DesignOnsite- Design a URL shortenerMedium
This question assesses the ability to design a distributed URL shortening service, focusing on database schema design, collision resolution, and caching strategies for high-read throughput.
J.P. MorganSoftware EngineerSystem DesignTechnical Screen Design an enterprise RAG-based AI assistant that enforces role-based document access control, bounds conversation history, mitigates prompt injection, and maintains an immutable, compliance-grade audit trail.
J.P. MorganSoftware EngineerSystem DesignTechnical ScreenThis problem tests your ability to design a scalable, consistent backend architecture for an e-commerce platform, focusing on inventory management, order processing, and high-read traffic handling.
J.P. MorganSoftware EngineerSystem DesignTechnical ScreenThis problem tests the ability to architect an LLM-based agentic system that balances autonomous task execution with strict role-based access control (RBAC) and auditability.
J.P. MorganMachine Learning EngineerSystem DesignTechnical ScreenTests your ability to present a production system architecture end-to-end, detailing data flow, ownership boundaries, database indexing and partitioning strategies, resilience patterns, and concrete architectural trade-offs.
J.P. MorganSoftware Engineer IISystem DesignOnsiteThis question evaluates a candidate's ability to design scalable, low-latency e-commerce architectures and real-time notification mechanisms while reasoning about data consistency, concurrency control, and correctness under high traffic (including concerns like avoiding oversells).
J.P. MorganSoftware EngineerSystem DesignOnline AssessmentEvaluate and design database access patterns, indexing strategies, and scaling techniques (partitioning, sharding, replication) for a financial user-profile system with high regional skew and frequent lookups.
J.P. MorganSoftware Engineer IISystem DesignOnsite