Rate Limiter

CodingStripeLast reported October 2025Low Frequency
Reported
1× across candidate reports
First seen
October 2025
Last reported
October 2025
Reported outcome
unknown

Problem Overview

Design a rate limiter that supports two operations: 1. hit(key, timestamp) — Record one access by a given key (e.g., an API client ID or user ID) at the specified timestamp. 2. allowed(key, timestamp) — Return whether the given key is still within the rate limit at the given timestamp…

  • 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 Stripe catalog
Full problem statements, candidate-reported follow-ups, and walkthroughs — for every Stripe 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.
Is this helpful?