System Design interview questions

Showing 481–510 of 1311 results

• Design a Security Monitoring FrameworkMedium

  Design a scalable, low-overhead security monitoring framework capable of capturing OS-level events via eBPF across a massive cloud fleet, streaming telemetry, and detecting malicious activity in near-real-time.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design a System to Distribute Large ML Model Files Across a Serving FleetMedium

  System design interview question from a senior software engineer loop at Google: design a system that distributes very large ML model files to a fleet of serving machines. It examines bandwidth reasoning, fan-out strategies, integrity verification, staged rollout and rollback, and recovery from failed or partial transfers.

  GoogleSoftware EngineerSystem DesignOther
• Design a Task Scheduler for Opaque Long-Running GPU Jobs ("Design Sora")Hard

  This question tests your ability to design a distributed job scheduler and execution engine for long-running, compute-intensive GPU workloads. It evaluates distributed system fundamentals including multi-tenant fairness, gang scheduling, node failure recovery, and resource utilization.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design a distributed rate limiterHard

  This question evaluates skills in distributed systems design, concurrency control, rate-limiting algorithms (token bucket and sliding window), distributed coordination and consistency, API design, and operational monitoring for scalability and fault tolerance.

  GoogleSoftware EngineerSystem DesignOnsite
• Design a global real-time notification systemMedium

  This question assesses the ability to design a distributed, global-scale notification platform that handles massive throughput, multi-channel delivery, and reliability requirements.

  GoogleSoftware EngineerSystem DesignOnsite
• Design a key-value storeHard

  This question tests the ability to design a distributed, scalable, and fault-tolerant key-value store while addressing challenges related to data distribution, consistency, and storage engine implementation.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design a large-scale distributed rate limiterMedium

  This question tests the ability to design a high-throughput, distributed rate-limiting service that handles multi-tenancy, ensures low latency, and manages consistency trade-offs.

  GoogleSoftware EngineerSystem DesignOnsite
• Design a prioritized log manager with evictionHard

  Design a prioritized log manager with eviction 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.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design an Embeddable Streaming Chat InterfaceHard

  Design an embeddable chat-agent widget with resumable streaming, virtualized history, safe caching, accessibility, and meaningful metrics.

  GoogleFrontend EngineerSystem DesignOnsite
• Design an Enterprise AI Adoption Agent for a Global CompanyMedium

  Prepare for a Google system design interview about design an enterprise ai adoption agent for a global company. This question focuses on requirements, architecture, trade-offs, reliability, and follow-up discussion areas.

  GoogleSoftware EngineerSystem DesignOnsite
• Design an Offline-First Client That Syncs Edits and Resolves Multi-Device ConflictsMedium

  Design the client side of an app where users keep editing data offline, store every edit locally, and sync with the server when the network returns. Covers the local data model and edit queue, a sync protocol that is safe to retry, and detecting and resolving version conflicts when several devices change the same data.

  GoogleSoftware EngineerSystem DesignOnsite
• Design an Online Coding Judge PlatformMedium

  This question tests the ability to design a high-throughput, secure, and fault-tolerant distributed system capable of executing untrusted user code in isolated environments.

  GoogleSoftware EngineerSystem DesignOnsite
• Design an elevator control systemHard

  This question evaluates system design skills including architectural modeling of components, scheduling and concurrency control, state-machine design, and fault-tolerance for real-time control systems, and falls under the System Design domain.

  GoogleSoftware EngineerSystem DesignOnsite
• Design at-least-once notification deliveryMedium

  This question evaluates expertise in reliable distributed systems design, including at-least-once delivery semantics, idempotency and deduplication strategies, retry and dead-letter handling, API and message-schema design, ordering and out-of-order handling, and scalability for high-throughput multi-tenant notification platforms.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design deduplicated file storage on filesystemHard

  This question evaluates system design and storage engineering competencies, including multi-tenant isolation, authentication and authorization models, content-addressable storage and deduplication, reference counting and garbage collection, concurrency control, API surface design, and scaling across nodes using only filesystem primitives.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design distributed log storage serviceHard

  This question evaluates a candidate's expertise in designing distributed storage systems, covering partitioned append-only logs, high-throughput writes and reads, replication, retention, indexing, compaction, leader/follower roles, and recovery mechanisms.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design distributed transactions protocolHard

  This question evaluates a candidate's understanding of distributed transactions, coordination protocols, fault tolerance, consistency, and reliability across microservices and databases.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design executable notebook service APIsHard

  This question evaluates a candidate's competence in designing secure, scalable systems for executing user-supplied code, covering API design, sandboxing and isolation, dependency management, resource limits, scheduling, and streaming proxies for logs/results.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design high-throughput event subscription systemHard

  This question evaluates a candidate's ability to design scalable, fault-tolerant event ingestion and subscription architectures, covering distributed systems, high-throughput messaging, content-based filtering, multi-tenant isolation, API/webhook design, delivery semantics, backpressure, sharding, security, and operational observability.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design key management serviceHard

  This question evaluates system design and security competencies—specifically cryptographic key lifecycle management, HSM integration, access control, auditing, multi-tenant isolation, and scalability—within the System Design domain.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design large-scale near-duplicate video detectionHard

  This question tests the ability to design an end-to-end pipeline for detecting near-duplicate videos at a massive scale, focusing on embedding generation, vector indexing, and trade-offs between precision and recall.

  GoogleMachine Learning EngineerSystem DesignOnsite
• Design nearest-available-taxi lookup with updatesMedium

  This question assesses the ability to design a high-concurrency geospatial system that maintains real-time state for moving entities and supports low-latency queries.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design quota enforcement for high concurrencyHard

  This question evaluates a candidate's understanding of distributed system design and engineering competencies related to quota enforcement, high-throughput rate limiting, consistency models, sharding, and concurrency control under very high QPS.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design relational-to-NoSQL migration pipelineHard

  This question evaluates a candidate's competency in designing a relational-to-NoSQL migration pipeline, covering distributed systems and data engineering concepts such as consistent snapshotting, change-data-capture, per-key ordering, idempotency, exactly-once behavior, schema evolution, partitioning, and operational reliability.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design street-view image ingestion and storage systemHard

  This question tests the ability to design a high-throughput, fault-tolerant ingestion pipeline for massive geospatial media, focusing on distributed storage strategies, data integrity, and efficient retrieval at scale.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Design viewing history and resume serviceHard

  This question evaluates a candidate's ability in large-scale system design, covering distributed state management, API design, data modeling for per-user progress, idempotent update semantics, cross-device synchronization, and privacy/compliance considerations.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Enforce a Country's IP Ban List on Incoming Connections Using Its Lookup APIMedium

  A system design exercise where a country provides an API reporting whether an IP address is banned and the service must refuse connections from banned addresses. It tests scoping questions such as IPv6 and address ranges, fast local enforcement at the edge, keeping ban data fresh, and fail-safe compliance behavior.

  GoogleSoftware EngineerSystem DesignOnsite
• Grounding Misinformation Moderation Decisions with a Retrieval-Augmented LLM PipelineMedium

  A product manager system design prompt about using retrieval-augmented generation to help moderate misinformation on a platform at large scale. It tests pipeline design from claim detection through evidence retrieval to human review, evidence freshness, precision and recall trade-offs, success metrics, and risks such as prompt injection.

  GoogleProduct ManagerSystem DesignOther
• How to host many domains on one IP?Medium

  Evaluates knowledge of DNS, HTTP/HTTPS request routing, TLS certificate management, and operational/security trade-offs when hosting multiple domains on a single public IP. Commonly asked to probe architectural reasoning and practical deployment trade-offs in the System Design domain at an architectural/operational level of abstraction.

  GoogleSoftware EngineerSystem DesignTechnical Screen
• Match Tagged Problems to Skilled Programmers at ScaleMedium

  Design a distributed matching platform that pairs incoming tagged tasks with skilled programmers using graph algorithms at scale.

  GoogleSoftware EngineerSystem DesignOnsite