Stripe Interview Questions — Page 11

Stripe·Software Engineer·Technical Phone Screen

May 2026

Stripe coding screen for a software engineering role, three-part Python problem centered on purchase line item cost computation. The problem kept expanding in scope with each part, which I wasn't fully prepared for.

Write a function that takes a list of line items (each with a product ID and quantity) and a price lookup dictionary, then returns the total cost and a per-item breakdown. What do you do when a product ID isn't in the price dictionary?
Extend the function with input validation: quantities and prices must be numeric and non-negative, NaN and infinity should be rejected, and invalid rows should produce clear error messages. Also handle empty input and duplicate product IDs.
Add an optional sort parameter so that when enabled, the breakdown is returned sorted by per-item cost in descending order using a lambda. Document your rounding rules and make sure the output matches expected results.

“The missing product ID edge case is where I spent way too long deliberating.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026

Stripe coding screen for a software engineer role. The problem looked like a parsing exercise at first glance but the fee computation logic with volume-based discounts is where things got interesting fast.

Given a CSV string of transactions, parse each row and compute the fee for that transaction based on the payment provider, the buyer's country, and any volume-based discount that kicks in once a buyer crosses a transaction count threshold. Return results in the original input order with id, transaction type, payment provider, and computed fee.

“The CSV parsing part I handled fine.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026

Stripe coding round, backend-flavored design question about extending a scheduler class. Pretty niche problem that felt more like a systems design warmup than a pure leetcode grind. Left feeling okay about it but not confident I nailed the data structure discussion.

You're given an AccountScheduler class with methods to check availability and lock accounts for a duration. Add an overload of the acquire method that auto-selects an available account using an LRU policy, and explain what data structures you'd use to make this efficient. Also, what should happen if no account is available at the requested time?

“The LRU part tripped me up more than I expected.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026

Stripe coding round for a software engineer role. One problem, payment processing logic in Java, which sounds straightforward until you actually sit down and work through all the edge cases around fees and balance tracking.

Given a map of currency balances and a list of payments (each with a currency, amount, and payment method that carries a fee), determine for each payment whether the balance covers the total cost (amount plus fee). Apply successful payments to the balance and return a per-payment success or failure result.

“The fee part is where I fumbled first.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026

Interviewed for a data analyst role at Stripe. One question but it was a meaty one, the kind that sounds conversational but actually requires you to think pretty carefully about your audience.

How would you explain a complex technical concept to a non-technical business stakeholder, and conversely, how would you explain a business concept to someone with a technical background?

“I went with analogies for the first part, talked about explaining a model's confidence interval like a weather forecast range rather than dumping stats on them.”

View Post

Stripe·Product Manager·Onsite - Product Sense / Strategy

May 2026

Stripe PM interview with a product design question that gave you three audience segments to pick from. Felt like a gift but also kind of a trap because you had to justify your choice before doing anything else.

Design a messaging app (like WhatsApp) tailored for one of three user segments: senior citizens, families, or businesses. You choose which segment.

“I picked businesses because it felt most natural for a Stripe interview context, payments infrastructure, B2B workflows, that kind of overlap.”

View Post

Stripe·Data Scientist·Take-home Assignment

May 2026

Stripe gave me a 6-hour take-home for a Data Scientist role and the core challenge was basically a scoping exercise disguised as a modeling problem. The real test wasn't the prediction itself, it was showing you could manage time, communicate trade-offs, and not quietly drown trying to do 24 hours of work in 6.

You have 6 hours to predict a product's target users, but a thorough solution would realistically take 24+ hours. Write a one-page plan you'd send to the hiring manager before starting: define the problem and success criteria, prioritize what you'll actually deliver in 6 hours vs. defer, list the minimum data and clarifying questions you need upfront, call out risks like label ambiguity or class imbalance with mitigations, lay out your presentation storyboard, and explain how you'd defend scope decisions in Q&A if someone pushes you on skipping something like causal inference.

“This one messed with my head a bit because my instinct was to just start building.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

May 2026

Stripe coding round where they hand you a broken codebase and tell you to fix it. The whole thing is built around a Python templating library called Mako, and you're working from failing tests rather than a blank slate.

You're given an existing codebase that uses the Mako Python templating library along with a set of failing tests. Find the bugs causing the failures and fix the code until all tests pass. Walk through your debugging process as you go.

“This format threw me a bit.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026

Stripe SWE interview with a focused API integration task. You're given pre-computed map data and need to upload it via a single POST request to a provided endpoint, no extra API calls allowed.

You're given pre-computed map data. Using only a specified POST endpoint, write code to upload and save that data to an external service in a single request.

“Constraint is the whole point here: one POST, no other calls.”

View Post

Stripe·Data Scientist·Technical Phone Screen

May 2026

Stripe DS interview that was basically a full experiment design gauntlet compressed into one session. Heavy on stats and causal inference, less on product intuition. Left feeling like I'd passed a grad school qualifying exam.

You're launching an email targeting model where users above a score threshold get the email and others don't. What's your primary success metric and which two guardrail metrics would you use, and why?
With a baseline 7-day purchase rate of 5% and an expected relative lift of 8%, calculate the minimum per-arm sample size for a two-sided test at alpha=0.05 and 80% power. Show your work.
Describe a ramp plan with sequential monitoring that keeps type-I error controlled. What interim looks would you schedule and what are your stopping rules?
What pre-experiment checks would you run before launching, and how would you handle potential interference between users and seasonality effects around weekends?
If a pure A/B test isn't possible due to legal or traffic constraints, what quasi-experimental design would you use instead, what assumptions does it rest on, and what would you show in your slides?

“I went with 7-day purchase rate as primary, which felt obvious.”

View Post