Circuit Breaker Implementation

CodingDatabricksLast reported August 2026Medium Frequency
Reported
6× across candidate reports
First seen
April 2025
Last reported
August 2026
Reported outcome
mixed

Problem Overview

Implement a Circuit Breaker pattern in code. The circuit breaker wraps calls to an external service (simulated via a lambda/Supplier that returns success or failure) and manages state transitions among three states: CLOSED (normal operation), OPEN (failing fast / rejecting requests), and HALF_OPEN (testing recovery). Key behaviors: (1) In CLOSED…

  • 5 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 Databricks catalog
Full problem statements, candidate-reported follow-ups, and walkthroughs — for every Databricks 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?