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 961–990 of 1311 results
Design the backend of a Google Docs-style editor in which many users edit the same document in real time and every copy converges to the same text. Tests concurrency control for simultaneous edits, routing of document sessions, operation storage and revision history, presence, and recovery from disconnects and server failures.
Otter.AiSoftware EngineerSystem DesignOnsiteDesign a versioned key-value store supporting staging, atomic commits, point-in-time snapshot reads, and automated rollover compaction.
Otter.AiSoftware EngineerSystem DesignTechnical ScreenDesign a system that ingests live telemetry from many drones sharing airspace and warns operators when two of them are predicted to come too close. It tests streaming ingestion, spatial partitioning, trajectory-based conflict prediction, alert delivery and reliability under the latency and safety demands of a real-time system.
PalantirSoftware EngineerSystem DesignOtherThis question evaluates knowledge of distributed system design, scheduling and orchestration, concurrency, fault tolerance, and observability in the context of large-scale metric collection.
PalantirSoftware EngineerSystem DesignOnsiteA senior system design question about the platform that lets LLM-driven agents discover and call backend tools. It probes tool registration and discovery, schema definition versus runtime validation of model-generated arguments, the interface between backend services and agents, and patterns for executing actions safely.
PalantirSoftware EngineerSystem DesignOtherThis question tests the ability to design a secure, scalable multi-tenant analytics platform that enforces strict data isolation and fine-grained access control while maintaining rigorous audit trails.
PalantirSoftware EngineerSystem DesignOnsiteDesign a scalable interview question bank 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.
PalantirSoftware EngineerSystem DesignTechnical ScreenThis question evaluates a candidate's ability to design cloud-native distributed systems, covering job scheduling, lifecycle management, observability, persistence, resource-aware placement, retry semantics, and multi-tenant security for containerized workloads.
Palo Alto NetworksSoftware EngineerSystem DesignOnsiteThis question evaluates system design and distributed systems competency, including API design, storage modeling, rollout workflows, operational behavior, and consistency trade-offs for device configuration management.
Palo Alto NetworksSoftware EngineerSystem DesignOnsiteA Palo Alto Networks system-design screen: design and implement a thread-safe, high-QPS rate limiter that enforces per-identity request quotas. The answer covers algorithm choice (token bucket vs. fixed/sliding window), atomic per-key state with locks or CAS, hot-path performance, bounded-memory eviction, distributed scaling (Redis+Lua, token leasing, consistent-hash partitioning), and rejection semantics.
Palo Alto NetworksSoftware EngineerSystem DesignTechnical ScreenDesign a loan application system 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.
ParafinSoftware EngineerSystem DesignOnsiteThis question evaluates architecture and systems engineering competencies related to building scalable, compliant financial platforms, including data modeling, API and event-driven workflow design, security, and regulatory integration.
ParafinSoftware EngineerSystem DesignOnsiteThis question evaluates object-oriented system design, API and data-structure modeling, state and concurrency management, persistence considerations, and algorithmic time/space complexity within a Go-based music player domain.
Paramount CommerceSoftware EngineerSystem DesignTechnical ScreenDesign a data processing system for JSON user records that contain names, addresses and payment methods, and explain how the design changes when the upstream source delivers data in batches versus as a continuous stream. It tests pipeline architecture, idempotent loading, ordering and late data, and the handling of sensitive fields.
PatreonData EngineerSystem DesignTechnical ScreenThis question evaluates proficiency in designing distributed, fault-tolerant payment systems with competencies in payments flows, exchange-rate management, compliance and regulatory constraints, transactional integrity, idempotency, scalability, reliability, and observability.
PayPalSoftware EngineerSystem DesignOnsiteThis system design question tests the ability to architect a real-time, low-latency fraud decisioning service that combines deterministic rule engines with machine learning model scores. It evaluates practical understanding of distributed systems trade-offs, feature store design, and safe model/rule deployment on a high-availability critical path.
PayPalSoftware EngineerSystem DesignOnsiteDesign elevator scheduling for small building 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.
PayPalData ScientistSystem DesignOnsiteThis question evaluates skills in large-scale system design including API and third-party integrations, data ingestion and normalization, transactional consistency and idempotency, security and privacy controls, data modeling for multi-currency financial records, and operational concerns like alerts and budgeting.
PerplexitySoftware EngineerSystem DesignTechnical ScreenThis question evaluates competency in diagnosing and mitigating production overloads in Kubernetes-based microservice architectures, emphasizing observability, autoscaling behavior, resource constraints, and incident-response reasoning.
PerplexitySoftware EngineerSystem DesignTechnical ScreenA system design question about letting customers update records individually and in bulk by uploading CSV files. It focuses on reliable asynchronous job processing, idempotent row application, partitioning large files and the underlying data, conflicts between the two write paths, and reporting row outcomes.
PinterestSoftware EngineerSystem DesignOnsiteTests end-to-end system design for large-scale, bursty notification pipelines, focusing on stream processing, aggregation under viral traffic spikes, and reliable third-party push delivery.
PinterestSoftware EngineerSystem DesignOnsiteThis problem tests the ability to design a distributed system capable of handling high-throughput asynchronous updates, atomic transactional integrity for partial batch failures, and robust image processing pipelines.
PinterestSoftware EngineerSystem DesignOnsiteDesign a distributed search autocomplete system capable of returning the top 10 popularity-ranked queries for any prefix with sub-30ms latency. The problem evaluates your ability to handle massive read throughput, partition heavily skewed prefix workloads, and merge streaming popularity signals with batch historical baselines.
PinterestSoftware EngineerSystem DesignOnsiteThis problem evaluates your ability to design a distributed rate-limiting service that maintains low latency while enforcing consistent request quotas across multiple global nodes.
PinterestSoftware EngineerSystem DesignTechnical ScreenDesign a highly available, ultra-low-latency distributed rate-limiting service supporting multi-tier rules (user, tenant, route, global) across globally distributed edge gateways.
PinterestSoftware EngineerSystem DesignOnline AssessmentThis question evaluates proficiency in designing large-scale distributed media systems, testing competencies in distributed storage and caching, ingest pipelines, CDN-backed delivery, indexing/search, sync/conflict resolution, access control/privacy compliance, and cost/operational planning.
PinterestSoftware EngineerSystem DesignOnsiteTests the ability to design an end-to-end media ingestion system supporting chunked resumable uploads, asynchronous analysis pipelines, idempotency, and real-time client notifications.
PinterestSoftware EngineerSystem DesignOnsiteThis problem tests the ability to design a high-throughput, low-latency search suggestion system that handles real-time updates and ranking at scale.
PinterestSoftware EngineerSystem DesignOnsiteTests the ability to architect a scalable, asynchronous catalog ingestion pipeline that balances high-throughput bulk feed processing with low-latency single-item edits while prioritizing price and inventory updates over compute-heavy image processing.
PinterestSoftware EngineerSystem DesignOnsiteDesign an extensible, resilient multi-channel notification engine (push, email, SMS, in-app) supporting high throughput, deduplication, quiet hours, rate limiting, and provider fallbacks.
PinterestSoftware EngineerSystem DesignOnline Assessment