Katkat

Topic

System Design interview questions

1311 System Design questions from 230 companies, with hints, runnable code and solution walkthroughs.

Questions1311

60 easy819 medium432 hard

Your progress0/1311

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

Showing 931–960 of 1311 results

  • Design an edge-to-cloud device monitoring system that accurately tracks device health and liveness across flaky, high-latency networks without falsely reporting absolute state.

    OpenAISoftware EngineerSystem DesignOnsite
  • This System Design question evaluates understanding of idempotency, request deduplication, client- and server-side reliability mechanisms, and concurrency control in distributed systems.

    OpenAISoftware EngineerSystem DesignHR Screen
  • This problem tests the ability to design a geo-spatial search service capable of handling high-frequency map interactions, filtering, and data consistency at scale.

    OpendoorBackend EngineerSystem DesignTechnical Screen
  • Design a subscription push service 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.

    OptiverSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates system design skills for building a topic-based news subscription service, focusing on streaming ingestion, relevance filtering, sliding-window rate limiting, de-duplication, ordered delivery, and data structure choices for in-memory operation.

    OptiverSoftware EngineerSystem DesignOnline Assessment
  • Design an end-to-end low-latency market making and execution architecture split between an exchange-colocated environment and a remote operational office.

    OptiverSoftware EngineerSystem DesignOnsite
  • This problem tests the ability to design a scalable, low-latency distributed system for enforcing traffic quotas across multiple geographic regions with considerations for consistency and burst handling.

    OracleBackend EngineerSystem DesignOnsite
  • Design a fault-tolerant, high-throughput log aggregation service that identifies and ranks the top-K microservices with the highest error counts over a sliding five-minute window.

    OracleSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a resilient, high-throughput ETL pipeline for sensitive and messy healthcare data, focusing on fault isolation, data integrity, and architectural scalability.

    OracleBackend EngineerSystem DesignOnsite
  • Design a real-time event-time aggregation pipeline to compute the top 100 most active users over a trailing 60-minute sliding window at scale.

    OracleSoftware EngineerSystem DesignOnsite
  • This problem tests the ability to architect a scalable, fault-tolerant entry point for distributed systems, focusing on request routing, health monitoring, and concurrency management.

    OracleSoftware EngineerSystem DesignOnsite
  • Design an in-memory key-value storage system utilizing active-passive synchronous replication where writes must commit on both nodes or fail atomically.

    OracleSoftware EngineerSystem DesignOnsite
  • A system design question that asks for a URL shortening service that turns long links into short codes and redirects visitors quickly. It tests requirements and capacity estimates, collision-free short-code generation, redirect caching and status codes, data modeling and partitioning, expiry, analytics and abuse handling.

    OracleSoftware EngineerSystem DesignOnsite
  • A system design question about building a service that accepts video uploads of up to 100 GB. It covers moving very large files efficiently, splitting them into chunks, resuming interrupted uploads, choosing storage for bytes and metadata, and scaling to many concurrent uploads.

    OracleSoftware EngineerSystem DesignTechnical Screen
  • A system design question for the like feature of a large video platform. It probes one-like-per-user correctness, serving counts and viewer state at huge read volume, absorbing bursts of likes on viral videos, exact versus approximate counting trade-offs, counter reconciliation, and abuse protection.

    OracleSoftware EngineerSystem DesignOnsite
  • A system design question for a photo and video sharing social network with follows, media uploads and a home feed. It probes estimation, media storage and delivery, feed generation for ordinary and very popular accounts, data modeling, caching, and defending trade-offs under heavy cross-questioning.

    OracleSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's ability to design scalable, correct distributed rate limiting mechanisms, testing competencies in distributed systems, concurrency control, API gateway behavior, observability, and configurability within the System Design domain.

    OracleSoftware EngineerSystem DesignOnsite
  • This problem tests the ability to architect a low-latency, secure isolation platform that bridges the gap between untrusted web content and enterprise endpoints.

    OracleSoftware EngineerSystem DesignOnsite
  • Design a scalable internal metrics collection and storage platform capable of ingesting high-throughput time-series data from hundreds of thousands of hosts, decoupling ingestion from query workloads.

    OracleSoftware EngineerSystem DesignOnsite
  • This 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 Explain your project system design states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    OracleSoftware EngineerSystem DesignOnsite
  • Design a memory-bounded distributed analytics system to compute both global (all-time) and rolling 24-hour top-K accessed URLs from a high-throughput event stream.

    OracleSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a distributed telemetry collection and automated incident remediation system for a large-scale hardware fleet.

    OracleSite Reliability EngineerSystem DesignOnsite
  • This question evaluates system design competency (Category: System Design), emphasizing distributed systems, queueing and matching logic, data modeling, API design, concurrency control, and regulatory compliance for constrained resource allocation.

    OscarSoftware EngineerSystem DesignOnsite
  • This problem tests the ability to design a resilient, stateful task scheduler capable of handling asynchronous external triggers (responses) and idempotent state transitions.

    OscarSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's competency in large-scale system design, encompassing distributed systems, networking, storage, real-time processing, and scalability considerations specific to live video streaming.

    OtherSoftware EngineerSystem DesignOnsite
  • This question evaluates skills in designing real-time collaborative systems, including distributed-systems reasoning, conflict-resolution algorithms, real-time synchronization, presence and offline synchronization, and storage/versioning architecture.

    OtherSoftware EngineerSystem DesignOnsite
  • Design a durable task scheduler with due-time indexing, atomic claims, worker leases, retry states, recurring occurrences, and clear duplicate-delivery semantics.

    OtherSoftware EngineerSystem DesignOnsite
  • Design incremental per-context entry numbering with idempotent state, contiguous-gap backfills, and correct handling of interleaved late events.

    OtherAnalytics EngineerSystem DesignTechnical Screen
  • Prepare to defend a production data pipeline you genuinely built or changed. The prompt tests how you connect requirements to architecture, compare alternatives, explain replay and backfills, diagnose a hard failure, quantify outcomes, and reflect on ownership and trade-offs.

    Otter.AiData EngineerSystem DesignTechnical Screen
  • Design the infrastructure between a web UI and a bot pool. Connect requirements and APIs to data modeling, consistency, scaling, failure recovery, observability, and the important design trade-offs.

    Otter.AiSoftware EngineerSystem DesignOnsite

More topics