Snowflake
Storage and concurrency internals, with a strong preference for candidates who can reason about cost.
- Active questions
- 26
- Rounds covered
- 2
- Last reviewed
- Aug 8, 2026
Reported questions
The full collection. Each entry shows how many independent reports it has and when it was last seen in a live loop.
- System designHardCorroborated · 3 reports
A single shard is taking 40% of writes
Your sharded datastore has one dominant key. Describe short-term mitigation you could ship today, then the re-sharding plan you would run over the next quarter without downtime.
Last seen Aug 14, 2026Study: System design → - CodingMediumCorroborated · 5 reports
Cache with expiry and bounded memory
Implement a cache with a maximum entry count and a per-entry TTL, with O(1) get and put. Then explain what changes if reads outnumber writes a thousand to one.
Last seen Aug 16, 2026Study: Core coding patterns → - CodingMediumCorroborated · 5 reports
Make a payment write idempotent
A client retries a charge request after a timeout. Design the request contract and storage schema so the charge happens exactly once, then explain what your code does when two retries arrive concurrently.
Last seen Aug 22, 2026Study: System design →
Interviewed at Snowflake recently?
Corroborating a question takes reports from people who did not interview together. Adding yours is what keeps this collection from drifting out of date.