← Back to Directory

Stripe interview notes, page 33 of 35

Large Enterprises

Most of these Stripe write-ups come from Software Engineers (295), then Product Managers (22) and Data Scientists (20). The most reported rounds are the technical phone screen (206), the system design round (39), the behavioral / leadership round (22) and the product sense round (20).

342 interview notes · updated Oct 2026

Stripe·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Stripe system design round, one question about building a metrics service. Pretty open-ended, not a lot of hand-holding.
  • Design a metrics service.

“Way more open than I expected.”

View Post

Stripe·Software Engineer·Onsite - Behavioral / Leadership

Jul 2026
Behavioral round at Stripe for a software engineering role. Pretty standard stuff for most of it, but they tacked on some AI-related questions at the end which I wasn't fully expecting.
  • What project are you most proud of and why?
  • Why do you want to work at Stripe specifically?
  • How do you incorporate AI tools into your day-to-day work as an engineer?

“Prepared for this one but still fumbled the delivery a bit.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe SWE interview with a KYC validation problem. Pretty focused on rule-based logic over raw algorithmic complexity, which I didn't expect going in.
  • Given a list of business account records each containing 6 KYC fields, write a function that outputs VERIFIED or NOT_VERIFIED for each record. A record is only verified if all 6 fields are present and non-empty, and the full_statement_descriptor field is between 5 and 31 characters inclusive.

“Simpler than it sounds on paper but I still managed to fumble the inclusive boundary check the first time.”

View Post

Stripe·Data Scientist·Technical Phone Screen

Jul 2026
Stripe DS interview that went deep into dispute rate diagnostics. The whole session was basically one extended case study on a payments metric gone wrong, with real numbers to crunch and no hand-holding on methodology.
  • Given a weekly dispute rate time series that spikes then partially reverts, how would you determine whether the change is a real signal or just noise?
  • Using the provided counts (Week 34: 800 disputes out of 100,000 payments; Week 35: 1,400 out of 110,000), compute a two-sided test for the difference in proportions and a 99% confidence interval.
  • Given per-country breakdowns showing US dispute rate rose while EU dispute rate actually improved, compute the mix-adjusted overall change and explain why the aggregate rate still went up (Simpson's paradox).
  • You need to monitor 200 country-by-industry segment pairs weekly for dispute rate changes. How do you handle multiple testing, and how do you combine statistical significance with practical effect size?
  • For segments with fewer than 5,000 succeeded payments, how would you handle dispute rate estimation, and how would you report the uncertainty?

“I started with the obvious stuff, variance in small counts, week-over-week volatility, but they pushed me to be more precise about what 'real' even means here.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Stripe system design round for a software engineer role. The problem was an invoice processing system that needed to be extended with refunds, adjustments, and an audit trail. Pretty dense for a single session.
  • You have an existing invoice processing system with line items and payment status tracking. Extend it to support full and partial refunds, line-item adjustments, discounts, and credits, while keeping totals always reconciled and all operations idempotent.
  • How would you design the schema for an append-only audit trail that captures every state change across creation, payment, refund, and adjustment events, including timestamp and actor?
  • How do you recompute the current invoice state, including subtotal, tax, total, and balance, purely from the audit trail?
  • How should refunds interact with the 'paid' status? Walk through the status transitions when a partial refund is applied to a fully paid invoice.

“This is a lot to hold in your head at once.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe coding screen for a software engineer role. One problem, pretty focused on payment matching logic. Not flashy but you have to get the edge cases right.
  • Given a payment record and a list of candidate transactions (each with merchant id, amount, currency, and timestamp), implement a function that returns the matching transaction with the earliest timestamp, or null if none match. Two records match if their merchant id, amount, and currency are all equal.

“Went with a single pass through the list, keeping track of the best match so far and swapping it out whenever I found an earlier timestamp.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe SWE interview that went sideways on a debugging question. The problem itself wasn't crazy but I couldn't get it across the finish line.
  • You're given a validator that works on nested structures. There's a bug where errors from inner validations aren't being surfaced correctly, specifically when a list contains a None value nested inside. Fix it so errors propagate and combine properly across the whole recursive structure.

“This is the one that got me.”

View Post

Stripe·Product Manager·Recruiter / HR Screen

Jul 2026
Brief Stripe screen, just one question about product preferences.
  • What is your favorite Stripe product?

View Post

Stripe·Data Scientist·Onsite - Behavioral / Leadership

Jul 2026
Behavioral round at Stripe for a Data Scientist role, basically one meaty question about disagreeing with your manager. Not a lot of fluff, they wanted a real story with stakes.
  • Tell me about a time you disagreed with your manager's decision on a project. How did you handle it, and what happened after?

“The part I underestimated was the 'what happened after' piece.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026
Stripe software engineer screen that opens with a structured intro segment before any coding. More administrative than I expected but they clearly use it to filter fast, so worth preparing.
  • Give a brief self-introduction focusing on two or three achievements most relevant to this role.
  • Why Stripe specifically, and how does your background connect to what Stripe is building?
  • Where are you located, what are your remote or relocation preferences, and how many hours can you overlap with the team's main time zone?
  • What are your compensation expectations across base, equity, and benefits, and how did you arrive at those numbers?
  • What questions do you have for the team about current projects or how stable the org has been lately?

“I rambled for probably two full minutes and hit like five different projects.”

View Post