Stripe interview, decoded.

Published accounts and 2026 candidate reports agree on the shape: two screens, then five onsite rounds of 45 to 60 minutes each, then team matching. Whether the API design and system design rounds are separate or one depends on level; the hiring manager round is more common at senior.

Stripe publishes six operating principles and the behavioural round is scored against them; accounts say the screen and the behavioural round both punish an answer that could be about any company.

• Users first
• Create with craft and beauty: the reason the coding round grades naming and tests
• Move with urgency and focus
• Collaborate without ego: the behavioural round's disagreement question
• Obsess over talent
• Stay curious: the Integration round is a test of learning an API in an hour

The reported questions are practical and financial: parse, validate, reconcile, and never charge twice.

Stripe has no online assessment; its filter is a live coding screen, and its distinctive rounds are two onsite hours spent in code you did not write. Both are open book. Neither is about algorithms. Candidates who prepared LeetCode for them report being surprised, so here is what each round asks and the method that clears it, from the accounts.

• Bug Squash: find the failing test, then the bug: Run the test suite first and read the failure before opening any source. Trace from the failing assertion up the call stack to the last place the data was right. Say what you are doing as you do it; the interviewer grades the search, not the moment of the fix. Reported bugs are small and structural: a check that is missing, a visitor a walker never calls, a read-modify-write with nothing serialising it.
• Bug Squash: prove the fix with the existing tests: Re-run the suite, then add the test that would have caught it. A fix without a test reads as a guess. If the repo's language is not your first, say so early and pick from the languages offered; the round is about reading code, and reading in a strange language is fine, writing under a clock is not.
• Bug Squash: the race condition: The recurring one. A value read, modified and written back with no lock or transaction, so two callers lose an update. Name the interleaving out loud, then fix it with the mechanism the codebase already uses (a lock, a transaction, an atomic operation) rather than one you import.
• Integration: read the docs before writing: Spend the first ten minutes on the documentation and the existing code: how the API authenticates, what it returns, what errors look like, and where the codebase already calls something similar. Candidates who start typing first report running out of time on the second half of the task.
• Integration: build the smallest thing that works, then harden it: Get one call through and one field surfaced, commit that, then handle the failure modes: a non-200, malformed JSON from the external service, a retry that must not double-apply. Idempotency is the word interviewers wait for; an idempotency key on any write is the answer.
• Integration: no AI assistant, internet allowed: The round permits searching and forbids coding assistants, and one 2026 account says it felt more like design than coding: what to call, in what order, what to store. Narrate the design before the code and the round grades well even when the second half is unfinished.

Practise both rounds on real repositories. Pick an open-source project in your language, break a test, and fix it against the clock; then take an API you have never used and build one feature against its docs in an hour without an assistant. Two evenings of that is worth more than a month of puzzles for these two rounds.

Levels.fyi medians for Stripe software engineers in the United States from 1,523 submissions, read 22 September 2026. Base plus equity plus bonus; the equity is private stock made liquid by tender offers, most recently February 2026 at $159 billion, with refreshes reported about nine months in. Dublin, London, Singapore and Bengaluru are location-adjusted with a different cash and equity mix; ask for the hub's band rather than converting the US one.

1. 01Break a test in an open-source repo you have never read and fix it in an hour, thinking aloud. Do it three times in three languages. That is the Bug Squash.
2. 02Build one feature against an unfamiliar API from its documentation in an hour, no assistant, then add the failure handling. That is the Integration round.
3. 03Write the coding round's code as if it ships: names, tests, the malformed-input case handled before the happy path is polished.
4. 04Have the idempotent payment design ready: keys at the API layer, a unique index underneath, and what a retry after a timeout does.
5. 05Prepare one story each for a production mistake, hard feedback and a disagreement, with the reasoning rather than the outcome as the point.
6. 06Have a real answer to why Stripe. Accounts say the generic one loses in the first five minutes.

This guide covers Stripe's software engineering loop, which is reported as the same shape in San Francisco, Dublin, Singapore, Bengaluru and remote. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

• 01Aced (Exponent), Stripe software engineer interview guidethe five onsite rounds, the Bug Squash as an unfamiliar repository with a failing test or open issue in a language of your choice with the internet open, the reported bugs (missing file-path check, missing AST visitor, race condition), the Integration round's provided API and SDK with no AI assistant, the coding examples (numeronyms, transaction logs, LRU cache, the multi-part CSV), the six operating principles, and the four-to-eight-week timeline; updated August 2026.
• 02ClavePrep, Stripe interview process 2026 (18 July 2026)the six stages with durations, the API design round's prompts (subscription billing, payout scheduling, webhook delivery) and criteria, the system design invariants, team matching with two to four managers, the behavioural round's mistakes-and-feedback shape, and that the loop is consistent across hubs.
• 03LinkJob, a Stripe software engineer interview in 2026 (12 February 2026)first-hand: the 60-minute team screen with follow-ups on edge cases and failures, the CSV processing, currency conversion and recurring payment scheduler problems, the idempotent payment design with a unique index on (user, order), the Bug Squash race in a read-modify-write, and the behavioural questions.
• 04TechPrep, Stripe's interview process 2026the Integration round as documentation or a private repo with Googling encouraged, the practical coding (a rate limiter, parsing), financial-grade system design (idempotency, exactly-once delivery), and the optional hiring manager round.
• 05Levels.fyi, Stripe software engineerthe L1 to L4 medians from 1,523 US submissions, read 22 September 2026.
• 06CNBC, Stripe valued at $159 billion after tender offerthe February 2026 tender offer, the backers, and the rise from $91.5 billion a year earlier.
• 07Stripe, 2025 annual letter and tender offerthe $1.9 trillion in 2025 volume, about 1.6 per cent of global GDP, Bridge and Privy, and Tempo with Paradigm.
• 08Wikipedia, Stripe, Inc.headcount of about 8,200, the hubs, and the Bridge acquisition at $1.1 billion.

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.