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 1021–1050 of 1311 results

  • This question tests the ability to design a high-throughput, low-latency leaderboard service capable of handling frequent rank updates and read requests for millions of active users.

    RedditSoftware EngineerSystem DesignOnsite
  • Design an extensible remittance fee-comparison engine that aggregates quotes across multiple providers, normalizes explicit fees and FX spreads, and gracefully surfaces provenance, staleness, and provider failures.

    RemitlyStaff AI-Native EngineerSystem DesignTechnical Screen
  • This question evaluates competency in designing a scalable, reliable, and secure production URL shortening service, covering API design, link data modeling and analytics, ID/token generation, caching and read/write paths, partitioning/replication/consistency choices, rate limiting and abuse mitigation, TTL handling and cleanup, and HA/DR and monitoring. Commonly asked in system design interviews to probe architectural trade-offs for high-read consumer services, it belongs to the System Design domain and emphasizes practical application of distributed systems and operational concepts rather than only conceptual theory.

    RemitlySoftware EngineerSystem DesignOnsite
  • Design a low-latency service that allows or denies traffic using source or destination IP rules. Candidates must define conflict precedence, address normalization, versioned rollout, stale-state behavior, audit evidence, privacy-conscious logging, and safe rollback.

    RemitlySoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's end-to-end system design skills, including architecture decomposition, trade-off analysis, data consistency choices, scalability and resiliency patterns, and integration of operational practices for a user-facing distributed service.

    RemitlySoftware EngineerSystem DesignOnsite
  • Design API rate limiting with token buckets, layered identities, endpoint costs, distributed-state tradeoffs, and measurable protection of legitimate traffic.

    RenderSoftware EngineerSystem DesignTechnical Screen
  • Design a resilient, multi-channel notification service that routes notifications across in-app, email, SMS, and push channels while honoring user preferences, idempotency, rate limits, and provider status tracking.

    ReplitSoftware EngineerSystem DesignOnsite
  • This question tests your ability to design a distributed system that routes incoming log streams to multiple storage clusters based on specified weight configurations while ensuring high availability and fault tolerance.

    Resolve.AiSoftware EngineerSystem DesignOnline Assessment
  • This question evaluates a candidate's ability to design a distributed, asynchronous system under hard external rate and capacity constraints. It tests system design fundamentals such as queueing, backpressure, state-machine modeling, and multi-tenant fairness, commonly asked to assess architectural reasoning at a practical, applied level rather than pure theory.

    Retell AISoftware EngineerSystem DesignTechnical Screen
  • Design a distributed outbound call pacing service that enforces smooth per-tenant calls-per-second (CPS) rate limits while ensuring durable queueing, priority scheduling, and safe failover.

    Retell AISoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's ability to design and build a small SQL query engine, covering tokenization, parsing, and query execution over in-memory tables. It tests system design and compiler-style thinking, including how to scope a large problem into an extensible v1 and reason about extending it with sorting, aggregation, and joins. This is a system design and practical implementation question assessing both architectural judgment and coding ability.

    Retell AISoftware EngineerSystem DesignTechnical Screen
  • This question evaluates a candidate's ability to design real-time collaborative systems, focusing on distributed systems concepts, concurrency control, consistency models, synchronization, and scalable backend architecture.

    Retell AISoftware EngineerSystem DesignOnsite
  • This question evaluates data modeling, transactional integrity, concurrency control, REST API and workflow design, and system scalability within the car rental domain in the System Design category.

    RetoolSoftware EngineerSystem DesignTechnical Screen
  • A system design exercise for a banking app that automatically enrolls opted-in customers in travel insurance when location signals show they are abroad. It tests requirements scoping, an event-driven pipeline, idempotent enrollment with an insurer, data modeling, scaling reads and writes, and failure handling.

    RevolutSoftware EngineerSystem DesignOther
  • This question evaluates competency in distributed systems and data consistency for financial applications, emphasizing replication, transaction correctness, conflict resolution, idempotency, and operational resilience.

    RevolutSoftware EngineerSystem DesignTechnical Screen
  • A multi-part system-design interview covering tagged event aggregation, driver-pay accounting, employee offboarding, and an LLM-backed expense assistant. Candidates must distinguish approximate dashboards from exact billing and design reliable workflows across failing dependencies.

    RipplingSoftware EngineerSystem DesignOnsite
  • Design a scalable topic-based news aggregation system covering distributed feed scheduling, idempotent article ingestion, stable pagination, and a low-latency read path.

    RipplingSoftware EngineerSystem DesignTechnical Screen
  • Design a news aggregation and recommendation system that ingests multi-publisher articles, clusters coverage of identical real-world events, and serves a personalized, deduplicated feed with low latency.

    RipplingSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates system design skills for building a large-scale, multi-region news aggregation platform, assessing competencies in ingestion architecture, deduplication and clustering, indexing and retrieval, personalization and ranking, and operational concerns like monitoring, consistency, and compliance.

    RipplingSoftware EngineerSystem DesignOnsite
  • This question tests your ability to design a distributed system that manages transactional integrity, high concurrency during bookings, and efficient searching for room availability.

    RipplingSoftware EngineerSystem DesignOnsite
  • Design an end-to-end hotel search and booking platform balancing high-throughput search with strictly consistent, transactional room inventory management across continuous date ranges.

    RipplingSoftware EngineerSystem DesignOnsite
  • This question evaluates expertise in large-scale system design—specifically data ingestion, article clustering/deduplication, feed ranking and personalization, API and data-model design, scalability, reliability, and monitoring—within the System Design domain.

    RipplingSoftware EngineerSystem DesignTechnical Screen
  • Design a scalable news aggregation platform that ingests high-volume publisher feeds, clusters and deduplicates coverage into cohesive stories, and serves fresh, personalized feeds with sub-second latency.

    RipplingSoftware EngineerSystem DesignTechnical Screen
  • Design an end-to-end news aggregation platform that ingests articles at scale, deduplicates syndicated content, clusters articles into evolving story threads, and serves low-latency feeds.

    RipplingSoftware EngineerSystem DesignTechnical Screen
  • System design question on building a news aggregator that polls many publisher APIs, stores only article metadata, and serves each user a paginated feed from the publishers and categories they follow. It tests polling schedules and stop conditions, rate-limit and outage handling, feed merging with deduplication, stable cursors, and bounded storage.

    RipplingBackend EngineerSystem DesignOnsite
  • Design a personalized news-feed system that ingests articles from many sources and builds a home feed. Connect requirements and APIs to data modeling, consistency, scaling, failure recovery, observability, and the important design trade-offs.

    RipplingSoftware EngineerSystem DesignOnsite
  • This problem tests your ability to design a high-scale feed delivery system, specifically focusing on the trade-offs between 'push' (fan-out) and 'pull' (fan-in) models for delivering content to users.

    RipplingSoftware EngineerSystem DesignOnsite
  • Design a scalable clickstream analytics pipeline capable of ingesting high-throughput user interaction events, handling duplicate and out-of-order data, and supporting both real-time aggregated dashboards and raw behavioral query paths.

    RipplingSoftware EngineerSystem DesignTechnical Screen
  • A Rippling software-engineer system-design screen: build an object-oriented, in-memory delivery cost dashboard that registers drivers with hourly rates, records completed deliveries, and reports total cost, paid and unpaid amounts via an idempotent payUpTo cutoff, and the maximum number of drivers simultaneously delivering in the last 24 hours. It tests time-interval modeling, exact monetary arithmetic without floating-point drift, sweep-line concurrency counting, idempotency, time-zone handling, and thread-safe O(1) dashboard reads. The walkthrough covers both prorated and whole-delivery payment semantics, a full Python reference implementation, and the production hardening a real payroll service would need.

    RipplingSoftware EngineerSystem DesignTechnical Screen
  • This question evaluates system design and architecture skills for building a policy-driven, explainable expense reimbursement platform, specifically testing competencies in rule engines and DSL/config design, versioning and immutable evaluations, group-level aggregation and conflict resolution, data modeling and partitioning for scale, API and workflow design, observability/auditing, and access control. As a System Design interview prompt it is commonly asked because it forces candidates to articulate trade-offs between extensibility, explainability, consistency, and performance; the assessment targets practical application of architectural principles with strong conceptual reasoning.

    RipplingSoftware EngineerSystem DesignTechnical Screen

More topics