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 451–480 of 517 results
- SnowflakeMediumSoftware EngineerDesign an Audit Logs Service
Tests the ability to design an immutable, highly available, multi-tenant audit logging service that supports high-throughput ingestion and tamper-evident storage while providing fast, tenant-scoped querying.
System DesignTechnical ScreenDistributed SystemsSecurityMulti-Tenancy - SnowflakeMediumSoftware EngineerDesign an Interactive Query Execution Notebook
Tests your ability to design an asynchronous, scalable system for executing interactive SQL queries and streaming execution state and tabular results back to web clients.
System DesignTechnical Screensystem-designdistributed-systemsapi-design - SnowflakeMediumSoftware EngineerDesign an object store with deduplication
This question evaluates a candidate's ability to design scalable, durable object storage systems with deduplication, touching on storage architecture, data modeling, metadata management, consistency, and garbage collection.
System DesignTechnical Screen - SnowflakeHardSoftware EngineerDesign under vague distributed requirements
This question evaluates expertise in distributed system architecture, metadata and schema management, transactional DDL semantics, consistency and replication strategies, API and data-model design, multi-tenant isolation, observability, security, and capacity planning.
System DesignTechnical Screen - SoFiHardSoftware EngineerScale a key-value store with consistent hashing
Scale a key-value store with consistent hashing 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 - SonatusHardSoftware EngineerDesign a RAG system for vehicle documents
This question evaluates a candidate's ability to design a Retrieval-Augmented Generation system, testing competencies in information retrieval, vector search, document ingestion and chunking, metadata modeling, citation handling, security, observability, and scalability within the system design and NLP/information-retrieval domain.
System DesignTechnical Screen - Sprinter HealthMediumSoftware EngineerDesign a Game Store with Purchases, Downloads, and Reviews
Design connected game-store pages for category browsing, purchases, authorized downloads, and reviews with consistent data and retry behavior.
System DesignTechnical Screen - StripeHardSoftware EngineerDesign a Feature Flag Service with Percentage Rollouts and Allow/Block Lists
System design question: design a feature flag service, similar in spirit to Amazon's Weblab, that lets teams turn features on or off, roll them out to a percentage of users, and force them on or off with allow and block lists. It probes where flag checks run, how users are assigned consistently, and how changes reach every service safely.
System DesignTechnical Screen - StripeMediumSoftware EngineerDesign a Scalable Idempotent Ledger Service
Design a high-throughput, fault-tolerant double-entry ledger service featuring immutable postings, strict write idempotency, and tunable balance freshness.
System DesignTechnical ScreenDistributed SystemsDatabase DesignFinancial Systems - StripeHardSoftware EngineerDesign a local activity counter service
This question evaluates a candidate's skills in designing large-scale distributed systems, focusing on near-real-time ingestion and aggregation, idempotency/deduplication, time-windowed (tumbling and sliding) analytics, hot-key sharding, storage and backfill strategies, and operational concerns including monitoring and privacy.
System DesignTechnical Screen - StripeMediumSoftware EngineerDesign an Idempotent Double-Entry Ledger
Design a highly reliable, idempotent double-entry ledger system that guarantees strict consistency, append-only immutability, and supports high-concurrency writes on hot accounts.
System DesignTechnical Screensystem-designfintechdistributed-systems - StubHubHardSoftware EngineerReview getEvents endpoint for readability, performance, scalability, security
A StubHub software-engineer technical-screen system-design exercise: review and fix a GET /events HTTP handler that loads related data (venue, performers, tickets, transactions) per event. Candidates must find and fix the N+1 query, then harden the endpoint across readability/architecture, performance (pagination, indexing, caching), scalability (timeouts, retries, rate limiting), and security (authN/authZ, injection, PII), with trade-offs, SLOs, and a test plan.
System DesignTechnical Screen - TemporalMediumSoftware EngineerDesign a One-to-One Chat System
This problem tests your ability to design a distributed, low-latency, real-time messaging system, focusing on message delivery guarantees, state management, and scalability.
System DesignTechnical ScreenWebSocketsDistributed SystemsScalability - TeslaMediumSoftware EngineerDescribe how you use Kubernetes
Describe how you use Kubernetes 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 - TeslaHardSoftware EngineerDesign a Supercharger Backend: Billing, Stall Telemetry and Nearest Available Charger
System design question on the backend for an electric-vehicle fast-charging network: billing each session by the energy delivered, storing stall health telemetry long term, and showing drivers the nearest available charger with its price. Probes secure device communication, DNS and routing, local buffering and sync versus async choices.
System DesignTechnical Screen - TeslaHardSoftware EngineerDesign concurrency-safe shared payment account API
Design concurrency-safe shared payment account API 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 - TikTokHardData EngineerDesign a Warehouse for Key Metrics
This question evaluates a data engineer's skills in dimensional modeling, data warehousing, and analytics infrastructure, covering facts and dimensions, grain definition, surrogate keys, partitioning and clustering strategies, and operational concerns like deduplication, late-arriving events, null/anonymous users, and slowly changing dimensions.
System DesignTechnical Screen - TikTokMediumSoftware EngineerDesign a distributed key-value store
This problem tests your ability to design a scalable, fault-tolerant distributed key-value store, focusing on partitioning strategies, replication, and handling node failures.
System DesignTechnical ScreenDistributed SystemsScalabilityHashing - TikTokHardSoftware EngineerDesign a high-concurrency ticketing system
TikTok software-engineer system-design interview question: design a high-concurrency ticketing / flash-sale system that survives millions of concurrent purchase attempts with zero oversell. It tests admission control and fairness (virtual waiting room, FIFO vs lottery), atomic inventory allocation with TTL reservations, anti-bot defenses, idempotent order creation, hot-key sharding, the data model and APIs, caching, message queues and delivery semantics, consistency and reconciliation, failure handling, capacity planning, SLOs, load testing, and monitoring.
System DesignTechnical Screen - TikTokHardSoftware EngineerDesign and explain your project architecture
A TikTok software-engineer system-design screen that asks you to walk through one of your recent projects end-to-end: architecture diagram, components and data stores, sync vs. async data flows and protocols, scaling and capacity planning, fault tolerance, backpressure, idempotency, observability, and security. It also probes the design trade-offs you made, the real failure modes you hit, the measurable impact, and what you would redesign. Includes a fully worked reference answer plus the scoring rubric.
System DesignTechnical Screen - TikTokMediumSoftware EngineerDesign low-latency large-scale hotel booking system
This question evaluates understanding of large-scale backend and distributed system design, including scalability, high availability, consistency models, concurrency control to prevent double-booking, hotspot mitigation, and protocol trade-offs for low-latency booking and availability flows.
System DesignTechnical Screen - TikTokHardSoftware EngineerDesign overload protection with load shedding
Design overload protection with load shedding 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 - TikTokHardSoftware EngineerDesign tables from metrics
This question evaluates analytics data modeling and event-driven warehousing skills, including schema design, metric derivation, partitioning/clustering strategies, and data-quality concerns such as deduplication, late arrivals, and idempotency.
System DesignTechnical Screen - TikTokHardSoftware EngineerExplain SRE architecture and troubleshooting scenarios
This question evaluates a candidate's competency in SRE architecture and reliability engineering, covering Kubernetes fundamentals, pod failure troubleshooting, SLO/SLA/SLI reasoning, multi-layer latency diagnosis, and SQL versus NoSQL trade-offs within the System Design domain.
System DesignTechnical Screen - TikTokHardSoftware EngineerImprove and measure service performance
This question evaluates performance engineering and observability skills—specifically SLIs/SLOs definition, instrumentation and profiling, load-testing, bottleneck identification, and optimization trade-offs for stateless HTTP microservices.
System DesignTechnical Screen - ToastHardSoftware EngineerDesign a Restaurant Seat and Table Reservation System
A system design question asking for a restaurant seat reservation system in which diners search availability by party size and time, then book, change or cancel. It tests the table-and-time inventory model, preventing double booking under concurrent requests, holds, availability caching and partitioning by restaurant.
System DesignTechnical Screen - Together AIHardSoftware EngineerDesign a GPU-aware pod scheduler
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 Design a GPU-aware pod scheduler states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
System DesignTechnical Screen - TripStackHardSoftware EngineerExplain Go concurrency and database choices
This question evaluates a candidate's understanding of Go concurrency primitives and scheduler behavior, cross-language concurrency comparisons, database model trade-offs (relational, document, columnar, key–value), and end-to-end storage design for high-concurrency systems.
System DesignTechnical Screen - TuroMediumSoftware EngineerDesign trip booking REST API and schema
This question evaluates RESTful API design, temporal data modeling, inventory management strategies, request/response/status-code design, data schema and indexing, and handling booking lifecycle changes such as extensions.
System DesignTechnical Screen - TuroMediumSoftware EngineerPlan a major database version upgrade
This question evaluates competency in database upgrade planning, including data migration strategies, cutover coordination, compatibility considerations, change-data-capture versus dual-write trade-offs, and rollback and risk management.
System DesignTechnical Screen
Snowflake
SoFi
Stripe
StubHub
Tesla
TikTok
Together AI
Turo