Failsafe Retry Library

Bug SquashStripeLast reported April 2026Low Frequency
Reported
1× across candidate reports
First seen
April 2026
Last reported
April 2026
Reported outcome
unknown

Problem Overview

Given a repository implementing a failsafe/retry policy library (candidates are told they can Google the open-source 'failsafe' library for context), identify and fix bugs in the implementation. The interviewer-provided codebase contains approximately 3 bugs. Candidates run failing test cases, diagnose root causes, and apply fixes. The first known…

  • 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?