TTL Key-Value Store with Efficient Expiry Cleanup

CodingSnowflakeLast reported July 2025Low Frequency

Reported: 1× across candidate reports
First seen: July 2025
Last reported: July 2025
Reported outcome: unknown

Problem Overview

Implement a key-value store that supports get, set, update, and delete operations, each accepting a timestamp as an extra parameter. Each key-value pair may be stored with a TTL (time-to-live), represented as an expiry timestamp. When a key has expired (its expiry timestamp ≤ the current timestamp), it should be…

4 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.