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 421–450 of 517 results
- RobinhoodEasySoftware EngineerDesign a distributed job scheduler service
This question evaluates understanding of distributed systems and microservice architecture, scheduling and timeout semantics, fault tolerance, scalability, and data modeling for job metadata, run history, and logs.
System DesignTechnical Screen - RobinhoodMediumSoftware EngineerDesign a job scheduler with SLA and logs
This question tests the ability to design a distributed, fault-tolerant job scheduling system capable of meeting strict SLAs and providing audit-ready logging.
System DesignTechnical ScreenDistributed SystemsTask QueuesScalability - RobinhoodMediumSoftware EngineerDesign a secure trading app on AWS
This System Design question evaluates secure cloud-based architecture on AWS, covering competencies in authentication and authorization, PII handling and auditability, API and data model design, and scalable low-latency market-data retrieval.
System DesignTechnical Screen - RobinhoodMediumBackend EngineerScale Word-Frequency Processing Beyond One Machine
This question tests the ability to design a distributed data processing pipeline that handles large-scale text files by balancing memory constraints, horizontal scalability, and data integrity.
System DesignTechnical ScreenDistributed SystemsMapReduceScalability - RobloxEasySoftware EngineerDesign Multi-Dimensional Request Rate Limiting
Design a distributed, low-latency rate limiting service capable of enforcing multi-dimensional limits (e.g., by user ID, IP address, and endpoint) across a large-scale gaming platform.
System DesignTechnical ScreenDistributed SystemsRate LimitingCaching - RobloxHardSoftware EngineerDesign a Played-By Summary System
Design a scalable social-proof service that tracks unique player counts per experience and computes real-time friend-intersection summaries under high write throughput and low read latency.
System DesignTechnical Screensystem-designdistributed-systemscaching - RobloxMediumSoftware EngineerDesign a Real-Time Shared To-Do List
Design a real-time collaborative to-do list supporting concurrent edits, task reordering, fast write confirmations, and seamless reconnect recovery.
System DesignTechnical ScreenReal-TimeWebSocketsDistributed Systems - RobloxMediumSoftware EngineerDesign a Scalable Likes System
This question tests your ability to design a high-throughput, distributed service for tracking user engagement, focusing on write-heavy loads and read-consistency trade-offs.
System DesignTechnical ScreenScalabilityDistributed SystemsCaching - RobloxMediumSoftware EngineerDesign a rate limiter
This problem tests your ability to design a distributed rate-limiting service that maintains request counts across multiple application nodes while balancing system performance and accuracy.
System DesignTechnical ScreenScalabilityDistributed SystemsCaching - RobloxMediumSoftware EngineerDesign in-game payment wallet system
Design in-game payment wallet 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 - SalesforceHardSoftware EngineerArchitect serving and storage for recommender
Architect serving and storage for recommender 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 - SalesforceMediumSoftware EngineerDesign a coffee ordering system
This question evaluates system design competency, focusing on order lifecycle modeling and state-machine enforcement, idempotency and data consistency, event-driven integration, real-time status propagation, and scaling across stores.
System DesignTechnical Screen - SalesforceHardSoftware EngineerDesign an async job system and cache layer
This question tests the ability to architect a distributed job processing system and integrate a high-performance caching layer to handle scheduling, execution, and state management at scale.
System DesignTechnical ScreenDistributed SystemsCachingAsync Processing - SalesforceHardSoftware EngineerDesign cloud & k8s architecture
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 cloud & k8s architecture states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
System DesignTechnical Screen - SalesforceHardSoftware EngineerDesign secure Kubernetes with CI/CD
This question evaluates expertise in Kubernetes architecture, cluster operations and troubleshooting, security hardening, and CI/CD pipeline design for managed Kubernetes clusters, covering control plane and node responsibilities, incident diagnosis, access and network policies, secret management, image integrity, and progressive delivery mechanisms. It is commonly asked to assess operational and security judgment and design thinking, testing both conceptual understanding of distributed control and security models and practical application in real-world CI/CD and incident-response scenarios within the System Design domain.
System DesignTechnical Screen - Scale AIEasySoftware EngineerDesign a Streaming Job Scheduler
This question evaluates task scheduling, deadline-based prioritization, dependency management, and distributed coordination competencies, encompassing algorithmic/data-structure reasoning as well as correctness under concurrency and failure conditions.
System DesignTechnical Screen - Scale AIMediumSoftware EngineerDesign a large-scale ticketing system
This question evaluates skills in large-scale system design, including distributed systems, concurrency control, transactional correctness, data modeling, API design, and integration with external payment providers.
System DesignTechnical Screen - Sentry.IoMediumSoftware EngineerDesign a Book Purchase Broker
This problem tests the ability to design a resilient distributed system that orchestrates third-party API calls, handles partial failures, and ensures transactional integrity across asynchronous boundaries.
System DesignTechnical ScreenDistributed SystemsAPIsAsync Processing - ShopifyMediumData EngineerChoose Between Batch and Streaming for a Data Pipeline
Work through a data-platform design that must support fast operational metrics and reproducible daily reporting. Compare batch, streaming, and hybrid choices while addressing late events, deduplication, replay, backfills, governance, and recovery.
System DesignTechnical Screen - ShopifyMediumSoftware EngineerScaling a Collision-Free Rover Fleet to a Million Robots
This question tests the ability to design a distributed system that manages real-time state consistency across a massive, sharded spatial grid while handling concurrency and robot movement.
System DesignTechnical ScreenDistributed SystemsConcurrencySharding - SnapchatHardSoftware EngineerDesign short URL service with click counting
This question tests the ability to design a distributed URL shortening service, focusing on system architecture, database partitioning, and strategies for high-frequency write operations like click tracking.
System DesignTechnical ScreenScalabilityDatabaseCaching - SnapchatHardSoftware EngineerParallelize the lock BFS safely
Parallelize the lock BFS safely 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 - SnowflakeMediumSoftware EngineerDesign a Cron Job Scheduler
This question evaluates skills in designing reliable distributed schedulers, including durable state modeling, concurrency and race-condition reasoning, idempotency, and fault-tolerant handoff semantics, and is commonly asked to assess a candidate's ability to guarantee correctness and coordination when multiple replicas must manage recurring job triggers. Categorized under system design and distributed systems with overlap into data modeling and consistency, it emphasizes practical application of architectural and operational trade-offs rather than purely theoretical concepts.
System DesignTechnical Screen - SnowflakeMediumSoftware EngineerDesign a Distributed Job Scheduler with Cron, Pause and Resume
Design a job scheduler service that runs one-time and cron jobs, supports pausing and resuming, and dispatches work to an unlimited pool of workers. It tests due-job indexing, claim and lease protocols, pause semantics, at-least-once execution with idempotency, and handling top-of-the-hour spikes.
System DesignTechnical Screen - SnowflakeMediumSoftware EngineerDesign a Geolocation Search Service
This question tests your ability to design a scalable spatial indexing system capable of performing range-based queries (e.g., 'find all points of interest within 5km') while maintaining high availability and low latency.
System DesignTechnical ScreenGeolocationIndexingScalability - SnowflakeHardSoftware EngineerDesign a REST API Abstraction Layer
This question evaluates system design and API design competencies, focusing on creating a REST API abstraction layer and internal SDK that address cross-cutting concerns like reliability, observability, security, versioning, and contract/interface modeling.
System DesignTechnical Screen - SnowflakeMediumSoftware EngineerDesign a Shared User Quota Service That Never Overdraws
Design a quota service that several services draw from for each user, where the balance must never be overdrawn under highly concurrent requests and must stay strongly consistent. It tests atomic conditional updates, reserve-and-commit APIs with idempotency, replication choices, and scaling a single hot user's quota.
System DesignTechnical Screen - SnowflakeHardSoftware EngineerDesign a distributed system end-to-end
This question evaluates a candidate's ability to design scalable, multi-tenant distributed analytics platforms, testing competencies in distributed systems architecture, data layout and storage, query planning and execution, metadata management, consistency and replication strategies, fault tolerance, observability, and capacity planning.
System DesignTechnical Screen - SnowflakeMediumSoftware EngineerDesign a distributed tree node counter
Design a distributed tree node counter 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 - SnowflakeHardSoftware EngineerDesign a multi-tenant quota system
This question evaluates a candidate's ability to design a global multi-tenant quota service, testing competencies in distributed systems, data consistency, concurrency control, API and storage modeling, and scalability within the System Design domain.
System DesignTechnical Screen
Robinhood
Roblox
Salesforce
Scale AI
Shopify
Snapchat
Snowflake