Key-Value Store System Design (Distributed)

System DesignSnowflakeLast reported May 2026Medium Frequency

Reported: 5× across candidate reports
First seen: July 2025
Last reported: May 2026
Reported outcome: mixed

Problem Overview

Design a distributed key-value store. The problem has appeared in several variants: (1) Base variant: design a distributed KV store considering all non-functional requirements (consistency, availability, partition tolerance, latency, durability, scalability, etc.) and how design choices change depending on which trade-offs are prioritized. (2) Disk-backed, contention-heavy variant: values are large…

5 candidate-reported follow-ups — the exact probes interviewers asked, with the trigger for each
The rest of the problem statement — full requirements, constraints, and edge cases
Approach and trade-offs — what passing candidates did, and the mistakes that sink people

Unlock the full Snowflake catalog

Full problem statements, candidate-reported follow-ups, and walkthroughs — for every Snowflake question.

Unlock with Pro

Already a member? Sign in

Verified Source

Every question is reconstructed from multiple independent candidate reports. Verbatim follow-ups, not invented ones.

Codex Fact-Checked

Technical claims, formulas, and scale numbers are reviewed against primary sources.

Interviewer Follow-ups

The exact follow-ups reported by candidates, with the trigger that prompts each one — plus the mistakes that sink people.