Stripe Interview Questions — Page 5

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe SWE interview with a debugging-round format where instead of writing code from scratch, you're handed broken or inefficient code and have to talk through what's wrong and how to fix it. Less about raw implementation and more about whether you can reason out loud under pressure.

You're given a piece of buggy or poorly optimized code. Walk through what's wrong with it, propose a fix, and explain whether your fix is actually optimal.

“The format threw me a bit.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

Apr 2026

Stripe's code craft round for a software engineer role was a weird setup: download a repo, fix a GitHub issue locally, and do it all in under 30 minutes. The environment setup ate into that time and the interviewer wouldn't budge on extending the coding window, which felt pretty unfair. Finished three problems but skipped test cases, which apparently got flagged in feedback.

Fix a real GitHub issue from a downloaded codebase (Bit Font Renderer) within a strict 30-minute coding window, including local environment setup.

“The setup itself took a chunk of time and the interviewer made it clear that finishing early didn't roll over into extra coding time.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

Apr 2026

Stripe coding round where they hand you a broken codebase and ask you to find and fix bugs. The real pressure isn't the bugs themselves, it's explaining every single fix in detail afterward.

Given a buggy codebase involving a template rendering and data-processing module, identify and fix as many bugs as you can.
For each bug fix you made, what is the downstream effect of that change, and are there edge cases where your fix could break something else?
How would you write regression tests to make sure the bugs you fixed don't reappear?

“I went in thinking it was a speed contest, find the most bugs fastest.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe debugging interview for a software engineer role. They handed me a small Python program using the Mako template engine with three planted bugs and told me to find them using a debugger. Two needed actual code fixes, the third just a verbal explanation. Felt more like a practical lab than a traditional coding round.

You are given a small Python program built on the Mako template engine containing three bugs. Use a debugger to reproduce each bug, trace the root cause, fix the first two in code, and verbally describe the fix for the third.

“This was not what I expected from a Stripe screen.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe coding round for a software engineering role. One meaty optimization problem that looked like a graph traversal at first but turned out to be a DP problem once I sat with it for a minute.

You have multiple groups of factories, each group representing a different type. Every factory has a distance from origin and a production cost. Pick exactly one factory per type. The total cost is the sum of production costs plus pairwise transport costs between consecutive types (transport cost depends on the distances of the two chosen factories). Find the minimum total cost.

“My first instinct was to try something greedy, which was wrong.”

View Post

Stripe·Data Analyst·Technical Phone Screen

Apr 2026

Stripe data analyst interview focused entirely on a working-capital loan product case. Four connected questions that built on each other, which was a nice change from the usual disconnected problem set. Pretty intense if you're not already thinking in terms of fintech revenue decomposition.

What metrics would you define to monitor whether a merchant working-capital loan product is performing well?
Total revenue from the loan product dropped over the last quarter. Walk me through how you'd investigate the root cause.
How would you use segmentation, data validation, and causal analysis to separate out product issues, risk problems, pricing changes, merchant mix shifts, and macroeconomic effects as possible explanations for the revenue decline?
Based on what the root cause turns out to be, what recommendations would you make to the business?

“I jumped straight to repayment rate and total revenue, which felt thin in retrospect.”

View Post

Stripe·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026

Standard behavioral loop at Stripe, nothing too surprising. Five questions, all pretty much what you'd expect from a big fintech company trying to assess how you work with people.

How do you handle conflicts with teammates or stakeholders?
Can you describe how you've worked effectively across different teams?
What's the most impactful project you've worked on, and why?
Have you mentored someone? How did you approach it?
How would your current manager describe you, and what feedback have they given you recently?

“I had a decent story ready for this but I rambled a bit getting to the point.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe coding round for a software engineer role, one question about implementing a join across two CSV-like datasets. Pretty algorithmic for what felt like a practical data problem.

Implement a join over two CSV-like datasets where one customer row can match multiple processor rows on a shared column. Walk through the algorithm, handle the one-to-many matching case, and discuss time and space complexity.

“The merge-style two-pointer approach clicked pretty quickly but I fumbled the tie-handling part for longer than I'd like to admit.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Apr 2026

Stripe system design round, one question the whole time. Pretty focused session, no warmup, they just went straight into it.

Design a feature flag system from scratch.

“This is one of those questions that feels approachable until you realize how many directions it can go.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

Apr 2026

Stripe gave me a pretty intense coding round centered entirely on payment card validation. Four parts, escalating complexity, and they wanted complexity analysis and edge case handling throughout. Not a vibe-check interview at all.

Implement the Luhn checksum algorithm and use it to validate a 16-digit VISA card number, returning either 'VISA' or 'INVALID_CHECKSUM'.
Extend the validator to support multiple card networks (VISA, Mastercard, AMEX) with different prefix ranges and lengths, returning the network name, 'INVALID_CHECKSUM', or 'UNKNOWN_NETWORK'.
Given a card number string with 1 to 5 asterisks replacing digits, count how many valid completions exist per network and output them sorted alphabetically.
Given a card number ending in '?' that indicates exactly one error was introduced (either a single digit change or a swap of two adjacent digits), enumerate all original valid cards consistent with that model, output as '<number>,<NETWORK>' sorted numerically.

“The Luhn part itself is fine once you remember the direction matters: start from the rightmost non-check digit and double every second one going left.”

View Post