Stripe Interview Questions — Page 32

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe coding screen for a software engineer role. One problem, pretty focused on transaction processing logic. Felt straightforward on the surface but there are a few edge cases that'll bite you if you're not careful.

You're processing a stream of bank transactions with account name, timestamp, currency, and amount fields. Positive amounts are credits, negative are debits. If a transaction would push an account's balance below zero, reject it and keep the balance unchanged. After processing everything, return all accounts with non-zero balances and the list of rejected transactions in the original order.

“The core structure is a hash map keyed by account name.”

View Post

Stripe·Software Engineer·Onsite - Multi Round

Jul 2026

Stripe interview with three distinct sections: an AI-assisted part, an integration section that went pretty smoothly, and a debugging round where I found two bugs but felt like I fumbled the communication side. Stayed on the call chatting with the interviewer for 20 minutes after, which was either a good sign or just awkward small talk.

Complete a coding task with AI assistance as part of the assessment.
Build out integrations across multiple scenarios in a hands-on coding section.
Find and fix bugs in existing code during a live debugging session.

“Two parts here.”

View Post

Stripe·Software Engineer·Onsite - Behavioral / Leadership

Jul 2026

Standard behavioral round at Stripe for a software engineer role. Six questions, all pretty much what you'd expect, nothing that should surprise you if you've done a few of these before.

Walk me through your background and a recent project you worked on.
What draws you to this team and company specifically?
Describe a situation where you had a disagreement with a coworker and how you handled it.
Tell me about a time you had to work through a problem that wasn't clearly defined. How did you break it down?
Can you share an example of when you received tough feedback and what you did with it?
What do you consider your biggest strengths, and what's one area you're actively trying to improve?

“I over-prepared the project part and under-prepared the 'about me' opener, which is backwards.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe technical phone screen for a software engineer role, focused entirely on a partially-implemented Mako template engine. Two-part problem: find and fix parser bugs, then do AST-level work. Pretty niche stuff, I hadn't touched Mako in years.

Given a partially-implemented Mako-style template engine, identify and fix bugs in the template parser and string-interpolation logic, covering things like `${...}` expression handling, comments, control directives, and escape sequences.
Work with the AST representation of Mako templates to support more advanced features: add a missing visitor method, fix a misnamed node attribute, or extend a `visit_*` method to handle a new node type.

“This is where I spent most of my time and honestly fumbled around more than I'd like to admit.”

View Post

Stripe·Software Engineer·Take-home Assignment

Jul 2026

Take-home assignment from Bikemap, three parts total, this being the last one. Basically an HTTP client exercise with some follow-up discussion baked in about concurrency and error handling.

Given an array of coordinate objects, assign each a color based on latitude (red if >= 0, blue otherwise), then POST each to an API endpoint with the coordinate and its color. How would you implement this sequentially, and how would you approach parallelizing it with bounded concurrency?
How would you handle transient failures when sending these POST requests, including retry logic and ensuring idempotency?

“The sequential part was fine, just a loop with awaits.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe data engineer interview that was basically a multi-part coding problem dressed up as a shipping calculator. Three progressively nastier versions of the same domain, each adding a new pricing wrinkle. Felt like a take-home but done live, which added its own kind of pressure.

Given a list of order lines and a flat per-unit rate table keyed by country and product, compute the total shipping cost across all order lines.
Extend the shipping calculator to use incremental tiered pricing, where each unit is charged at the rate of the tier covering that unit's index, taxi-meter style. Also explain how your code handles the case where all units fall within a single tier.
Now add a second tier type: a 'fixed' pricing mode where, if the total order quantity falls within a tier's range, the entire line item costs a flat price regardless of quantity. Fixed tiers take priority over incremental ones. Implement the combined logic and include meaningful test cases for all three parts.

“Straightforward enough.”

View Post

Stripe·Software Engineer·Online Assessment (OA)

Jul 2026

Stripe software engineer round that was basically a CSV parsing problem dressed up as a payments exercise. Sounds mundane but the edge case handling is where it gets you.

Given a CSV file of payment transactions with a status field and various amount/fee columns, parse the file and output a fee report grouped by payment status. The output format must be byte-exact, matching a provided example including column order, separators, header, alignment, decimal precision, and trailing newline.

“The actual math is nothing.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe coding screen for a software engineer role, basically one problem the whole time: parse a CSV of transactions, apply a fee ruleset, and output a clean result. Felt more like a real-world task than a leetcode grind, which was a nice change.

You are given a CSV describing payment transactions with fields like transaction ID, payment method, payment type, status, and amount. Apply a provided set of fee-calculation rules to each row and output the results as: id, transaction_type, payment_provider, fee.

“The parsing part felt fine at first, then the edge cases in the fee rules started stacking up and I realized I'd been skimming the spec instead of actually reading it.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe SWE interview with a billing simulation problem. The core challenge was modeling a two-plan pricing system with prorated splits when a user straddles both plans in the same month. More nuance than it looks on the surface.

Given a list of usage records (user_id, input_tokens, output_tokens, plan), compute the total monthly cost per user. There are two plans: a pay-as-you-go plan billed per token with different rates for input vs output, and a subscription plan with a flat monthly fee covering usage up to a threshold, with any overage billed at pay-as-you-go rates. If a user appears under both plans in the same month, split the billing proportionally by usage share.

“The base case felt manageable.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe technical screen for a software engineer role. The whole round was built around debugging a chain of five API calls where the first two pass and the last three break in various ways. Pretty unusual format but kind of makes sense for a payments company.

You are given a sequence of five API requests against a live HTTP service. The first two succeed with 200s, but the next three return non-2xx errors. Find what's wrong with each failing request, fix it, and get the full chain passing end to end.

“This was more involved than I expected.”

View Post