Katkat

practice a little every day, paws crossed ♡

System Design Interview Questions

Practice 9403 coding, system design and machine learning questions from 546 companies, sorted by role, topic and interview round. Every question has step-by-step hints, a code runner that supports 8 languages and an AI mentor; members also get the full solution walkthrough.

9403
Questions
546
Companies
11
Topics
8
Languages

Showing 31–60 of 517 results

  • AmazonHardSoftware Engineer
    Design a memory usage switcher with thresholds

    This question evaluates system design and operational engineering skills in process memory management, runtime configurability, observability, and reliability, and belongs to the System Design domain; it primarily tests practical application with system-level conceptual reasoning.

    System DesignTechnical Screen
  • AmazonMediumSoftware Engineer
    Design a package installer with dependencies

    This question tests your ability to design a system that manages complex dependency graphs, ensuring package integrity, version compatibility, and atomic installation operations.

    System DesignTechnical ScreenGraphsDependency ResolutionTransactions
  • AmazonHardSoftware Engineer
    Design a scalable parking lot system

    Design a scalable parking lot 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.

    System DesignTechnical Screen
  • AmazonMediumSoftware Engineer
    Design an AI Fraud-Triage Agent Over a 1 TB/Day Payments Event Stream

    Design a service where an AI agent investigates flagged payment events inside a stream running at roughly 1 TB of events per day, covering capacity math, where the agent sits relative to deterministic detection, and the cost and adversarial-input guardrails that keep it from becoming a liability.

    System DesignTechnical Screensystem-designstreamingfraud
  • AmazonEasySoftware Engineer
    Design an Amazon Locker Service

    Tests object-oriented design and state-machine modeling for a self-service package locker station, focusing on parcel allocation, code expiration, and physical-vs-logical state consistency.

    System DesignTechnical ScreenObject-Oriented DesignState MachineIoT
  • AmazonHardSoftware Engineer
    Design an extensible ticketing system

    This question evaluates software architecture and system-design competencies, covering extensibility patterns, concurrency control for high-throughput ticketing, transactional and idempotency guarantees, persistence/schema modeling, API design, and pluggable pricing strategies.

    System DesignTechnical Screen
  • AmazonHardSoftware Engineer
    Design an intersection traffic-light system

    This question evaluates system design competency across real-time control and safety-critical logic, API and data modeling, sensor/actuator integration, and operational scalability for traffic-signal controllers.

    System DesignTechnical Screen
  • AmazonHardSoftware Engineer
    Design in-memory threshold switcher

    This question evaluates a candidate's ability to design memory-aware control systems, covering skills such as hysteresis-based thresholding, dynamic runtime reconfiguration, thread-safe concurrency, low-overhead metric sampling, event-driven state notifications, and handling multi-process and failure edge cases.

    System DesignTechnical Screen
  • AmazonHardSoftware Engineer
    Design locker allocation service

    This question evaluates a candidate's understanding of stateful system design, resource allocation strategies, concurrency control, API and data modeling, and fault tolerance in the context of real-time locker assignment.

    System DesignTechnical Screen
  • AmazonMediumSoftware Engineer
    Design pickup point planning for ride-hailing

    Design a ride-hailing pickup-point planning system. Covers map snapping, candidate generation, driver and passenger routing, safety filtering, scoring objectives, app presentation, architecture, historical learning, and A/B metrics.

    System DesignTechnical Screen
  • AmazonHardSoftware Engineer
    Design real-time top-K products service

    An Amazon software-engineer system-design screen: design a real-time service that ingests a stream of purchase events (customer_id, item_id, timestamp) and continuously serves the top-K most purchased items over multiple rolling windows (e.g. last 5 minutes, last 1 hour, 24 hours, and daily totals). The answer covers ingestion and partitioning, event-time windowing with watermarks, exact min-heap vs. approximate Count-Min-Sketch / Space-Saving top-K, late/duplicate/out-of-order handling, state and TTL, exactly-once fault tolerance, horizontal scaling, serving APIs, and latency-vs-accuracy trade-offs.

    System DesignTechnical Screen
  • AmazonHardSoftware Engineer
    Design secure multi-tier cloud infrastructure

    This question evaluates cloud systems design competencies including multi-tier network architecture, IP addressing and capacity planning, security controls, centralized server management, shared storage trade-offs, and identity and access integration within a production-scale virtual private cloud.

    System DesignTechnical Screen
  • AmperityMediumSoftware Engineer
    Design a Metrics Collection System

    Design an end-to-end distributed metrics collection and monitoring pipeline capable of ingesting millions of data points per second, handling label cardinality risks, and supporting low-latency time-series queries.

    System DesignTechnical Screensystem-designtime-seriesdistributed-systems
  • AnrokHardSoftware Engineer
    Design async batched key-value fetcher

    This question evaluates understanding of designing asynchronous, batched request handling in a single-threaded event-loop, covering batching windows, key deduplication, response-to-callback correlation, consistency boundaries, error handling, timeouts/retries, cancellation, and backpressure.

    System DesignTechnical Screen
  • AnthropicHardSoftware Engineer
    Design Durable One-to-One Web Messaging at Large Scale

    Design Web-only one-to-one messaging at 100 million DAU with durable deduplication, chat sharding, membership indexes, offline recovery, and replica-aware reads.

    System DesignTechnical Screen
  • AnthropicHardSoftware Engineer
    Design Large Model-Weight Distribution to GPU Workers

    Design a high-throughput, fault-tolerant distribution platform that transfers multi-hundred-gigabyte model weights to tens of thousands of GPU worker nodes with integrity validation, progressive rollouts, and fast rollback capabilities.

    System DesignTechnical Screensystem-designml-infrastructuredistributed-systems
  • AnthropicMediumSoftware Engineer
    Design Peer-to-Peer Model Distribution Under a Shared Link Cap

    Design an internal peer-to-peer artifact distribution system to deliver large model weights from a single seed machine to thousands of cluster workers subject to a shared aggregate upload-and-download network link limit.

    System DesignTechnical Screensystem-designdistributed-systemsnetworking
  • AnthropicMediumSoftware Engineer
    Design Telemetry Ingestion and Reconcile Metric Names

    Design a scalable telemetry ingestion pipeline that standardizes and reconciles metric naming inconsistencies and schema drift across disparate client libraries, historical stores, and real-time query engines.

    System DesignTechnical ScreenData InfrastructureTelemetryStream Processing
  • AnthropicHardSoftware Engineer
    Design a Crash-Resilient LRU Cache

    This question evaluates a candidate's competency in designing a crash-resilient LRU cache, including which data and ordering must be persisted, durability and recovery concerns, and trade-offs between latency and persistence.

    System DesignTechnical Screen
  • AnthropicMediumSoftware Engineer
    Design a One-on-One Chat Service

    Design a highly available, low-latency one-on-one messaging system capable of delivering messages in real time, maintaining strict ordering, and handling offline synchronization.

    System DesignTechnical Screensystem-designdistributed-systemsreal-time
  • AnthropicMediumSoftware Engineer
    Design a Resilient Chat System

    Design a resilient, distributed 1:1 and group messaging system focusing on durability guarantees, strict message ordering, robust fan-out, and reliable offline catch-up under partial failures.

    System DesignTechnical Screensystem-designdistributed-systemschat-architecture
  • AnthropicHardSoftware Engineer
    Design a concurrent web crawler

    An Anthropic system design question: design and implement a concurrent web crawler, from a single-threaded baseline to manual threads, a thread pool and asyncio. It covers the URL frontier, deduplication across workers and redirects, robots.txt and per-host politeness, Retry-After backoff, completion detection, memory sizing, testing and monitoring.

    System DesignTechnical Screen
  • AnthropicMediumSoftware Engineer
    Design a distributed web crawler

    This question tests the ability to design a scalable, fault-tolerant distributed web crawler that handles URL management, distributed coordination, and domain politeness.

    System DesignTechnical ScreenDistributed SystemsScalabilityCaching
  • AnthropicMediumSoftware Engineer
    Design a one-to-one chat system

    This problem tests your ability to design a scalable, real-time one-to-one messaging system by addressing requirements for message ordering, delivery guarantees, and user presence.

    System DesignTechnical ScreenWebSocketsMessagingScalability
  • AnthropicMediumSoftware Engineer
    Design a prompt-sharing platform

    This question assesses the ability to design a scalable content-sharing platform, focusing on data modeling, efficient retrieval of user-generated prompts, and the handling of concurrent access and permissions.

    System DesignTechnical ScreenAPI DesignData ModelingScalability
  • AnthropicHardMachine Learning Engineer
    Design a scalable MapReduce pipeline

    Design a scalable MapReduce pipeline 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.

    System DesignTechnical Screen
  • AnthropicHardSoftware Engineer
    Design a scalable network I/O service

    This question evaluates a candidate's ability to design a scalable, highly available network I/O backend, testing competencies in distributed systems, storage architecture, CDN and caching integration, API and data model design, capacity planning, failure handling, observability, and security.

    System DesignTechnical Screen
  • AnthropicHardSoftware Engineer
    Design a scalable, reliable system

    The prompt evaluates competence in large-scale distributed system design, covering storage architecture, consistency and replication strategies, caching, APIs and data models, operational reliability, security, and cost/capacity planning.

    System DesignTechnical Screen
  • AnthropicHardSoftware Engineer
    Design production-ready dedup service

    This question evaluates system design and distributed storage competencies, focusing on scalable file deduplication, content-defined chunking, metadata and index design, multi-tenant architectures, and operational reliability across regions.

    System DesignTechnical Screen
  • AnthropicMediumSoftware Engineer
    How would you scale batch image pipelines?

    This problem evaluates your ability to design a distributed, fault-tolerant batch processing system for high-throughput image transformation tasks.

    System DesignTechnical ScreenDistributed SystemsScalabilityBatch Processing