Rate Limiter Implementation

CodingOpenAILast reported July 2026Medium Frequency

Reported: 4× across candidate reports
First seen: November 2025
Last reported: July 2026
Reported outcome: mixed

Problem Overview

You are given a buggy Python rate limiter implementation for a ChatGPT-like API service. The rate limiter is integrated into a web framework (Django or similar), spanning from the controller/route layer to the backend logic. It supports multiple rules, each expressed as a (max_requests, period) tuple, and enforces per-user request…

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 OpenAI catalog

Full problem statements, candidate-reported follow-ups, and walkthroughs — for every OpenAI 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.