← Back to Directory

Stripe interview notes, page 1 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·Data Scientist·Technical Phone Screen

Sep 2025
Stripe DS interview that was basically one long SQL gauntlet. The question was dense enough that I'm still thinking about edge cases a week later. Solid experience if you like data engineering adjacent problems, rough if you were expecting something lighter.
  • Write a single SQL query to build a training dataset anchored at a specific snapshot timestamp, including feature columns like days since signup, event counts over a 7-day window, distinct session counts, and a binary 30-day order label. The schema includes users, events, and orders tables, and the data has late-arriving events, duplicates, and users with no events at all.

“This was the whole interview basically.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Stripe API design round focused entirely on a single problem called 'bikemap'. It was one of those rounds where the scope sounds narrow but the surface area keeps expanding the more you dig into it.
  • Design a public API for a service that integrates with the Bikemap dataset. The dataset includes coordinates and a color or state value per location. Your API needs to support batch updates, a clear resource model, pagination, idempotency, and proper error handling.
  • What latitude and longitude conventions are you assuming, and how would you communicate those to API consumers in your documentation?

“I started by trying to nail down the resource model before touching endpoints, which I think was the right call.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding round for a software engineer role, one problem the whole time. The algorithm wasn't the hard part, the I/O parsing was.
  • Implement a subscription email notification system: given users, their subscription data, and a stream of events (new content, billing, etc.), determine which users should receive email notifications and output the results in the required format.

“The logic for figuring out who gets emailed wasn't that bad once I mapped it out.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Stripe coding round, software engineer role. The problem was a factory selection optimization with transport costs layered in, and it escalated across multiple parts. Decent problem if you like thinking about prefix arrays and DP, but the setup took a while to internalize.
  • You have three lists of factories, one per type. Each factory has a distance from origin and a production cost. Pick exactly one factory from each type to minimize total cost, where total cost includes each factory's production cost plus the transport cost between consecutive factories (transport cost = absolute difference in distances). How do you solve this efficiently?
  • How would you generalize the factory selection problem to an arbitrary number of factory types instead of just three?

“The naive triple-nested loop is obviously too slow and I think they were watching to see if I'd go there first.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Stripe system design round for a software engineer role. The core problem was building a transaction fee calculator from scratch, which sounds straightforward until you actually have to model the rule schedule in a way that's both flexible and not a complete mess to maintain.
  • Design a transaction fee calculator that accepts a transaction (amount, type, currency, and other attributes you define) and a configurable fee rule schedule supporting flat fees, percentage fees, tiered fees, capped or minimum fees, and per-type or per-currency overrides. How do you model the rule schedule, handle rule precedence, and keep it extensible to new fee types?

“I started with the data model and that turned out to be the right call.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding screen for a software engineer role, built around a contact filtering problem that kept getting harder as the interview went on. Multi-part structure meant you couldn't just solve the easy version and coast.
  • Given a list of contacts with fields like name, email, and phone, filter down to only those whose information matches a given target domain. The problem starts simple but adds layers: fuzzy domain matching, subdomain handling, alias resolution, and eventually writing unit tests for edge cases.

“The first part felt easy enough, just check if the email host equals the domain string.”

View Post

Stripe·Machine Learning Engineer·Onsite - System Design / Architecture

Apr 2026
Stripe ML engineer interview with a system design question centered on fraud detection. Pretty standard for the domain but still a lot of ground to cover.
  • Design a machine learning system for fraud detection.

“This is basically the canonical ML system design question for fintech, so I'd prepped for it, but there's still a lot of surface area to cover.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Phone screen for a Stripe SWE role, focused on a payment invoice parsing and matching problem. Interviewer was chill, and I got the callback for onsite the same day.
  • Given a set of payment invoices, parse the relevant fields and match them according to specified criteria. The problem has multiple parts that build on each other.

“This one has apparently made the rounds on forums quite a bit, so I'd seen some version of it before.”

View Post

Stripe·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Stripe software engineer interview with a debugging round that nearly broke me. The time pressure was real and I did not finish, which stings in retrospect.
  • Given a buggy codebase, identify and fix the bugs within a strict time limit using a debugger.

“Spent way too long on print statements before realizing that wasn't going to cut it.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe debugging round where you're handed a broken fork of the Mako Python template engine and told to find the bug. The final stretch goes into the compiler internals, which I was not expecting at all.
  • You're given a buggy fork of the Mako Python template engine. Investigate the failures, narrow down the root cause, and produce a fix.
  • In the template compiler path, a tag is missing or not being recognized, causing compilation to fail. Trace the lexer and parser flow, identify where the tag should be registered or emitted, and patch it.
  • How would you write a regression test for the fix you just made, and how could this bug have been caught earlier?

“The setup sounds reasonable until you're actually in it.”

View Post