Stripe hands you a broken repo and a clock

If Stripe is on your calendar, do not file debugging under “normal coding.”
It is live, watched, and timed — not a take-home (Exponent, 4dayweek.io).

You clone a cold repo, read a failing test, fix bugs in your IDE. External resources are usually allowed. Perfect resolution is not the bar — your process is.

What the loop looks like

The coding round is often a multi-part incremental build that gets harder by adding requirements, not by swapping algorithm tiers (Prepfully, Exponent).
An integration-style round may hand you a real repo and docs and ask for a small feature with internet access (candidate report).

The debugging round is the incident. The rest of the loop is a workday.

Why narration matters here

Stripe is writing-first. Pre-meeting memos are normal; more people consume the writing than produce it (Pragmatic Engineer).
A company that runs on legible thinking grades legible thinking. The interviewer watches the diff and listens to the reasoning.

Candidate reports often hear: readable and maintainable beats clever and opaque (Medium report).

Stripe-shaped bugs

Think money-movement correctness, not algorithm flex:

• missing or misplaced idempotency keys on retries
• broken webhook signature / header parsing
• unsafe status transitions
• partial error handling around external calls

Check those seams first when the failing test smells like “retry wrote twice” or “webhook accepted garbage.”

What they are scoring

Candidate writeups stress orientation: burn the clock lost in the tree and you look weak even with skill (4dayweek.io). Treat that as qualitative, not a scorecard.

The 60-minute loop

0–5 — say what the repo does

Do not edit. Run the failing test. Read the error. Name the user-visible behavior. Find the narrow entry point.

“Before I touch anything: this repo processes X. The failing test exercises Y. The error is at Z. I’ll read Z before I form a theory.”

5–15 — one spoken hypothesis

Trace input → state change → validation → unchecked assumptions.
Instrument the one seam that can kill your theory fastest.

“Hypothesis: duplicate side-effect on retry — write before the idempotency key. I’ll check the retry path first.”

15–40 — smallest safe change

Fix the condition, the middleware order, or the missing key. Do not redesign the handler.

TS

Copy

async function createPayment(data: Params, key: string) { return stripe.paymentIntents.create(data, { idempotencyKey: key, }); }

“Key at the operation boundary, not the transport layer. Smallest change that restores the contract.”

40–60 — verify out loud

Run the targeted test. Say root cause, evidence, fix, and what you would add with more time (regression on the retry path). One sharp cleanup if time remains — not a bonus refactor.

The silent thrasher

Six files open, three half-edits, zero sentences. Even if they are right, the grader has no signal.
Order beats volume: behavior → theory → change → verification.

Operating Principles are in the room

The behavioral side scores against Stripe’s Operating Principles — users first, craft, urgency and focus, egoless collaboration, talent, curiosity (Stripe Jobs — culture / principles).
Demonstrate them in how you debug. Do not name-drop the list.

Five-day reset if the loop is close

1. Day 1 — read idempotency + webhook signatures. Write one broken-retry example and fix it.
2. Day 2 — clone a small unfamiliar open-source repo; find a failing test; narrate 15 minutes without fixing.
3. Day 3 — full 60-minute mock with a friend watching; record yourself.
4. Day 4 — kill silent stretches; practice the four sentences.
5. Day 5 — light rest; re-read Operating Principles; skim Stripe company page.

Short version

Orient fast. Say one hypothesis. Make the smallest safe fix. Verify in words.
That is the round.

Sources

• Stripe Operating Principles
• Idempotent requests, Webhook signatures
• Exponent — Stripe SWE guide
• Prepfully — Stripe SWE guide
• 4dayweek.io — Stripe process
• Pragmatic Engineer — Stripe culture (part 2)
• Candidate report (Medium, 2025–2026)