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 181–210 of 1311 results

  • This problem tests the ability to design a distributed, high-concurrency counter system that maintains strict consistency while ensuring low-latency updates for collaborative task management.

    AsanaSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates system design competencies including scalable architecture, data and API modeling, feed generation trade-offs, storage and caching strategies, consistency expectations, and operational concerns such as rate limiting, abuse mitigation, and observability.

    AsanaSoftware EngineerSystem DesignTechnical Screen
  • Design a conversational flight service that turns vague travel intent into grounded multi-leg search, safe booking, and useful price alerts. Cover clarification, authoritative supplier data, repricing, idempotent payment flows, shared price watches, quotas, privacy, and graceful degradation at large scale.

    Assorted HealthSoftware EngineerSystem DesignOnsite
  • This question evaluates skills in designing scalable, low-latency analytics and aggregation systems, covering event tracking, time-windowed ranking, stream processing, storage trade-offs (OLTP vs OLAP), caching, API design, and handling late or duplicate events.

    AtlassianSoftware EngineerSystem DesignOnsite
  • Design a comprehensive observability and reliability framework to guarantee 99.99% availability for a multi-tenant cloud collaboration platform. The design must cover Service Level Indicators (SLIs), Service Level Objectives (SLOs), automated burn-rate alerting, dependency fault isolation, and chaos recovery testing.

    AtlassianSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a high-throughput, distributed task management system, focusing on data modeling, concurrency control, and scalability for collaborative features.

    AtlassianSoftware EngineerSystem DesignOnsite
  • This question tests your ability to design a scalable, reliable stream processing pipeline capable of ingesting, filtering, and persisting real-time events while managing system state.

    AtlassianSoftware EngineerSystem DesignTechnical Screen
  • A front-end system design question about a product search page with a search input above a grid of results drawn from a catalog of unbounded size. It probes the component tree, where search state should live, and how the candidate keeps typing responsive and results fast when the result set can never be loaded all at once.

    AtlassianFrontend EngineerSystem DesignTechnical Screen
  • A three-part system design question about a rate limiter service: the components a simple limiter needs, how to scale it as users grow and what breaks, and how to make limits more precise. It tests shared counters, atomic updates, hot callers, failure policy and the accuracy trade-offs between rate limiting algorithms.

    AtlassianSoftware EngineerSystem DesignTechnical Screen
  • Design social comments with APIs, indexed pagination, durable notifications, retry deduplication, and measured read/write scaling for hot posts.

    AtlassianSoftware EngineerSystem DesignOnsite
  • This question tests the ability to design a scalable, low-latency distributed rate-limiting service that handles high-concurrency requests across multiple microservices.

    AtlassianSoftware EngineerSystem DesignTechnical Screen
  • This problem tests your ability to architect a scalable, stateful chatbot system that integrates RAG (Retrieval-Augmented Generation) with low-latency conversational requirements.

    AtlassianMachine Learning EngineerSystem DesignOnsite
  • This question tests a candidate's ability to design scalable data models and distributed indexing strategies for a multi-tenant tagging system. It evaluates system design competency across storage, caching, sharding, and consistency trade-offs — core skills assessed in senior software engineering interviews.

    AtlassianSoftware EngineerSystem DesignTechnical Screen
  • This question assesses the ability to design a scalable, functional MVP for a greeting-card service, focusing on user-generated content storage and retrieval.

    AtlassianSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's ability in RESTful API design, data modeling, concurrency control, idempotency, pagination, and indexing/search strategies for a multi-tenant tagging system. It is commonly asked in the system design category to assess architectural decision-making and both conceptual understanding and practical application of endpoints, schema, and edge-case handling.

    AtlassianSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's ability to design a scalable authorization system incorporating RBAC and resource-based ACLs, testing competencies in access-control models, data schema design, policy evaluation, API design, caching strategies, and audit logging.

    AtlassianSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's ability to design scalable, fault-tolerant distributed systems for web crawling, covering competencies in concurrency, queueing and scheduling, deduplication, storage architecture, and observability.

    AtlassianSoftware EngineerSystem DesignOnsite
  • Tests systematic incident triage, observability strategies, and root-cause analysis across distributed tiers (caching, connection pools, databases, compute) when a scaled service suffers severe latency degradation.

    AtlassianSoftware EngineerSystem DesignTechnical Screen
  • Ensure thread-safe updates to org hierarchy 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.

    AtlassianSoftware EngineerSystem DesignTechnical Screen
  • A candidate-driven front-end system design discussion about an emoji picker with a search field. It tests how a candidate scopes the component, models and loads the emoji catalog, ranks search results, keeps a grid of thousands of emoji fast, and supports keyboard and screen-reader users.

    AtlassianFrontend EngineerSystem DesignTechnical Screen
  • This question evaluates understanding of hierarchical data modeling, REST API design, database schema choices (e.g., adjacency list vs alternatives), and systems-level concerns like scalability, pagination for large subtrees, and cycle prevention.

    AtlassianSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate’s ability to design scalable, reliable broadcast and scheduling systems, covering API design, data modeling, distributed scheduling, delivery semantics, idempotency, retries, and operational fault-tolerance.

    AttentiveSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates debugging and root-cause analysis, memory management, streaming/chunked data processing (including correctness across chunk boundaries), and system reliability aspects such as observability, testing, and recovery for large-input backends.

    AttentiveSoftware EngineerSystem DesignTechnical Screen
  • This problem tests the ability to design a time-series storage system by balancing read/write throughput, data retention policies, and query performance at scale.

    AttentiveSoftware EngineerSystem DesignTechnical Screen
  • Design a service that pulls and syncs data from a third-party API that enforces a hard limit of 3 requests per second. It tests global rate limiting across distributed workers, retry and backoff behavior, incremental sync with checkpoints, and prioritizing work when demand exceeds the request budget.

    AttentiveSoftware EngineerSystem DesignTechnical Screen
  • A system design exercise to build an event analytics system that ingests very high-volume, concurrent event streams from Kafka and stores them for long-term analysis. It tests Kafka topics, partitions, consumers and consumer groups, delivery guarantees, and durable, queryable storage design.

    AttentiveSoftware EngineerSystem DesignOnsite
  • A system design question about a product catalog built from full retailer snapshot files, with 50,000 retailers, 11,000 read queries per second and a 400 ms latency target. It tests snapshot diffing, recovery from a mistaken upload, admin overrides that survive retailer updates, scaling ingestion, and observability.

    AttentiveSoftware EngineerSystem DesignOnsite
  • Design a real-time ad serving system that picks an eligible ad for each ad request, returns it within a tight latency budget, and records impressions and clicks for billing. Tests candidate retrieval and ranking, campaign data freshness, budget enforcement across many servers, and a deduplicated event pipeline.

    AttentiveSoftware EngineerSystem DesignOnsite
  • Design an extensible, resilient data ingestion service capable of extracting data from heterogeneous third-party APIs while managing rate limits, pagination state, schema drift, and fault recovery.

    AttentiveSoftware EngineerSystem DesignOnsite
  • Design a high-throughput, read-heavy catalog service supporting draft/publish lifecycles, item versioning, search projections, and resilient rollback mechanisms.

    AttentiveSoftware EngineerSystem DesignOnsite

More topics