Incident Monitor

OAStripeLast reported September 2026Medium Frequency

Reported: 4× across candidate reports
First seen: March 2026
Last reported: September 2026
Reported outcome: mixed

Problem Overview

Given a list of time-sorted transaction log entries, each containing a timestamp, merchant_id, status_code (error code), and count, design an incident monitoring system that maintains a 30-second sliding window over the logs. For each (merchant_id, error_status_code) pair, continuously aggregate error counts within the sliding window. The problem is divided into…

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