practice a little every day, paws crossed ♡
Software Engineer 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 1081–1110 of 1189 results
- StubHubMediumSoftware EngineerDesign Event Email System
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 Event Email System states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
System DesignOnsite - StubHubMediumSoftware EngineerDesign Internal Chat and Re-engagement Emails
This question evaluates a candidate's competency in designing scalable, real-time messaging systems and re-engagement workflows, covering distributed systems concepts such as WebSocket-based bidirectional communication, presence, cross-server message routing, message persistence, APIs, storage trade-offs, inactivity detection, and email-triggering workflows. Commonly asked in the System Design category, it tests high-level architectural reasoning and practical application of scalability, reliability, and failure-handling trade-offs when integrating persistent WebSocket connections, cross-server routing, and background email jobs in a distributed platform.
System DesignOnsite - StubHubMediumSoftware EngineerDesign a Global Marketing Email Platform
This problem tests your ability to design a high-throughput, fault-tolerant email delivery system that handles scheduling across time zones, manages email templates, and provides basic analytics.
System DesignOnsiteScalabilityDistributed SystemsMessaging - 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 EngineerBalance Backend Availability, Maintainability, and Scalability
Design a high-throughput vehicle telemetry and diagnostics backend while evaluating explicit architectural trade-offs among availability, maintainability, and scalability.
System DesignHR ScreenDistributed SystemsIoTKafka - 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 Distributed Blob Storage System for Build Artifacts
Design a distributed storage system for build artifacts, similar to a distributed NoSQL database but storing opaque blobs with looser ACID requirements. It tests separating immutable data from consistent metadata, upload atomicity, replication and repair, handling download fan-out, and safe retention and garbage collection.
System DesignOnsite - 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 - TeslaMediumSoftware EngineerDesign a Video Sharing Platform
Design a resilient, large-scale video sharing and streaming platform that handles multi-gigabyte uploads, asynchronous transcoding, and low-latency global delivery. This question tests your ability to design chunked upload protocols, idempotent processing pipelines, and CDN-backed adaptive streaming architectures.
System DesignOnsiteDistributed SystemsVideo StreamingCDN - TeslaMediumSoftware EngineerDesign an Order Fulfillment System
Design an order-fulfillment system and explain its major components, data flow, and reliability trade-offs.
System DesignOnsite - 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 - TeslaMediumSoftware EngineerDesign synchronization for water molecule assembly
This question evaluates concurrency and synchronization skills, including thread coordination, use of locks/semaphores/condition variables, and reasoning about safety and liveness properties in concurrent systems.
System DesignHR Screen - TeslaHardSoftware EngineerFrom a Monorepo Commit to an Over-the-Air Vehicle Update, and Choosing What to Build
Trace everything that happens between an engineer pushing a commit to a monorepo and the resulting software being installed on customers' cars, then explain how the monorepo decides which targets to build and test and in what order. It tests CI and release gating, artifact provenance, staged over-the-air rollout, safe in-vehicle installation, and dependency-graph builds.
System DesignOnsite - 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 EngineerExplain Your System Architecture
Explain Your System Architecture 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 DesignOnsite - 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 - TruefoundryMediumSoftware EngineerDesign Interviewer Availability and Atomic Booking APIs
Design a relational data model and concurrent APIs for managing interviewer availability and atomic candidate interview booking.
System DesignOnsiteConcurrencyDatabase DesignAPI Design - 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 - TuroMediumSoftware EngineerRoute HTTP requests to pods in a cluster
This question evaluates understanding of request routing, service discovery, virtual service abstractions, load balancing algorithms, health checks, and fault-tolerance mechanisms within containerized cluster environments, testing competencies in distributed systems and networked service architecture.
System DesignTechnical Screen
StubHub
Tesla
TikTok
Together AI
Turo