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 241–270 of 1311 results
Identify and fix deadlock in locked code 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.
BoxSoftware EngineerSystem DesignOnsiteThis question evaluates full‑stack engineering competencies including API design, data persistence, input validation, transactional integrity for monetary data, frontend-backend integration, automated testing, and developer documentation.
BrexSoftware EngineerSystem DesignTechnical ScreenThis question evaluates system design and distributed-systems competency, focusing on transaction processing, idempotency and deduplication, monetary precision and rounding, consistency models, data modeling, and operational controls like observability and fraud prevention.
BrexSoftware EngineerSystem DesignTechnical ScreenDesign a peer-to-peer money transfer product with accurate balances and history despite retries, crashes, and concurrent spending. Define APIs, transfer states, durable accounting, atomic movement, recovery, reconciliation, authorization, and the boundary between an in-memory prototype and production.
BrexSoftware EngineerSystem DesignOnsiteThis question evaluates understanding of authentication system design, secure password storage practices, API endpoint and request/response modeling, database schema design, and session or token-based login state management.
BridgeSoftware EngineerSystem DesignTechnical ScreenThis question tests your ability to design a distributed asynchronous processing pipeline that manages entity relationships, handles API retries, and maintains state consistency across multiple dependent components.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenThis question tests your ability to design a distributed streaming data pipeline that balances high-throughput ingestion with low-latency analytical queries for country-specific rankings.
ByteDanceSoftware EngineerSystem DesignOnsiteDesign a centralized, governed data serving platform that provides downstream consumers with stable query APIs, schema evolution safety, cursor-based exports, and data freshness metadata.
ByteDanceData EngineerSystem DesignHR ScreenThis question tests the ability to design a scalable, low-latency rate limiting service that functions across multiple distributed application servers.
ByteDanceSoftware EngineerSystem DesignOnsiteThis question tests your ability to design a distributed, high-frequency job scheduling system that handles millions of tasks with varying priorities while ensuring reliability and strict execution guarantees.
ByteDanceSoftware EngineerSystem DesignOnsiteDesign a monitoring dashboard that separates data freshness from query latency, with ingestion, rollups, browser updates, and stale-data handling.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenA time-boxed system design question asking for a high-level payment system that charges users through an external payment provider. It tests the end-to-end checkout flow, idempotent retries, a payment state machine and ledger, asynchronous provider notifications, reconciliation and failure handling.
ByteDanceSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's ability to design a real-time, high-throughput distributed system focusing on API design, concurrency control, ordering guarantees, idempotency, persistence of bid history and state transitions, and real-time push/update mechanisms.
ByteDanceSoftware EngineerSystem DesignOnsiteDesign a live comment overlay that stays synchronized with a video during live viewing, replay, seeking, and reconnects. Explore timeline semantics, stable ordering, scalable fanout, replay queries, moderation, backpressure, and graceful degradation during traffic bursts.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenA system design question about a ticket booking system for high-demand on-sales. It probes how to absorb the traffic spike when sales open with load balancing, waiting rooms and rate limiting, and how to manage inventory with holds, payment-timeout release and consistent cache and database updates so that no ticket is ever sold twice.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenSystem design question: design a payment system that places real-time holds on funds and settles them in batches, then explain how retries avoid double charges. It probes idempotency at every hop, payment state machines, double-entry ledgers, consistency across an external processor, reconciliation, and recovery from specific failures.
ByteDanceSoftware EngineerSystem DesignOnsiteDesign an e-commerce platform with searchable catalogs, carts, atomic inventory reservations, idempotent checkout, payment recovery, and reliable order state.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenThis problem tests your ability to design a normalized relational database schema that implements Role-Based Access Control (RBAC) to support hierarchical users, roles, and resource-level permissions.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenEvaluate whether a MySQL-backed service should migrate to MongoDB using its actual workload and correctness needs. Compare relational and document models, joins and transactions, then outline a dual-run migration, rollback plan, and measurements that would prove an improvement.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenModel a demand-side ad platform with advertisers, campaigns, ad groups, ads, and creatives, including audience rules, edit history, and versioned publishing.
ByteDanceSoftware EngineerSystem DesignOnsiteThis question tests the ability to design robust cache-aside mechanisms to prevent database overload during cache expiration events for high-traffic keys.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenDesign a distributed observability and tracing system to monitor, debug, and diagnose multi-step agent tool-call failures across retries and execution stages without leaking sensitive data.
ByteDanceSoftware EngineerSystem DesignTechnical ScreenThis question evaluates skills in system architecture and engineering, including data modeling, API design, concurrency control to prevent double-booking, availability and scheduling logic, scalability under traffic spikes, and operational concerns like auditability and low-latency queries.
C3 AISoftware EngineerSystem DesignOnsiteDesign the issuer-side platform that approves or declines card purchases in tens of milliseconds, settles them later, and stores cardholder identity data so a breach of any one service exposes as little as possible.
Capital OneSoftware EngineerSystem DesignTechnical ScreenDesign the backend of a buy-now-pay-later checkout financing service that approves or declines a purchase in real time against a shopper's revolving credit line, then go deep on latency budgeting for the decision and on securely storing borrowers' personal data.
Capital OneSoftware EngineerSystem DesignTechnical ScreenA system design question that asks for the backend of a credit card system, then goes deep on what payment authorization latency is reasonable and how to achieve it, and on how to store cardholders' sensitive personal information. It tests transaction flow design, available-credit concurrency, latency budgeting, and data protection.
Capital OneSoftware EngineerSystem DesignTechnical ScreenA system design question for a credit card platform covering customer login, real-time payment authorization with fraud checks, monthly credit bureau reporting, a spending overview, and instant credit limit increase decisions. It tests laying out entities, services and read and write paths before choosing deep dives.
Capital OneSoftware EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's ability to architect a highly reliable transactional account-balance service, testing competencies in data modeling and storage choice, API design for idempotency, concurrency and consistency mechanisms, replication/failover, partitioning for scale, and auditability.
Capital OneSoftware EngineerSystem DesignOnsiteThis question evaluates system design skills focused on distributed systems architecture, transactional integrity, strong consistency models, security and authentication, external payment and ATM integrations, data modeling, API design, concurrency control, and operational monitoring for financial platforms.
Capital OneSoftware EngineerSystem DesignOnsiteDesign an enterprise agent platform with durable execution, deliberate workflow-versus-agent choices, enforceable tool guardrails, and a dependency-aware latency plan.
Capital OneSoftware EngineerSystem DesignOnsite