← Back to Directory

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

Apr 2026
Stripe coding interview with a multi-part data validation problem. The problem scaled in complexity across parts, and the spec was genuinely long, so if you go in expecting a clean leetcode-style prompt you're going to have a bad time.
  • Given a stream of records and a set of validation rules, implement a system that verifies each record. The problem expands across multiple parts: starting with basic field presence and type checks, then adding cross-field constraints, then further rule extensions.

“The spec was way longer than I expected.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding screen for a software engineer role. One question, but it had a follow-up that caught me mid-thought and I had to basically re-architect my solution on the fly.
  • You're given a function that joins two CSV-like datasets on a shared key field, producing one output row per customer row with the matching processor columns appended. Extend it to handle cases where a single customer row's key matches multiple processor rows, emitting one combined row per match while preserving the processor file's original row order.

“Started fine with the base case in my head, then they asked about one-to-many and I had to stop and rethink the whole thing.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding screen for a software engineer role. The main problem was about reconciling payments and invoices, which sounds straightforward until you actually think through all the edge cases.
  • Given a list of payments and a list of invoices, match each payment to an invoice using the invoice_id field. Return three things: matched pairs, payments that couldn't be matched (missing or unrecognized invoice_id), and invoices that received no payment. Also discuss your choice of data structure and how you'd handle duplicate invoice_ids.

“I went straight for a hashmap keyed on invoice_id, which felt right.”

View Post

Stripe·Data Scientist·Technical Phone Screen

Apr 2026
Stripe DS interview that went deep fast. The coding portion was basically a mini distributed systems problem dressed up as a stats question, and I was not fully prepared for how much they wanted on the complexity proofs and the concurrency angle.
  • Design and implement in Python a streaming algorithm that ingests an unbounded sequence of (user_id, event_time, event_type) tuples and keeps, per user, a uniform random sample of at most M events using reservoir sampling. Prove that each event has equal inclusion probability.
  • What are the time and space complexity guarantees for your reservoir sampling implementation, and how do you achieve amortized O(1) update per event with O(U*M) total memory?
  • How would you support multiple concurrent processing shards with deterministic merging of their reservoirs, given a fixed random seed?
  • Write unit tests that verify marginal inclusion probabilities are correct and that increasing M reduces variance in feature estimates derived from the reservoir.
  • As an extension: maintain a real-time top-K users by event count using a min-heap of size K, where the heap also supports decrementing counts when late events are revoked. What are the time and space complexities?

“This is the kind of question where you think you remember reservoir sampling from a textbook and then realize mid-explanation that you're fuzzy on the proof.”

View Post

Stripe·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round for a software engineer role at Stripe. Pretty standard stuff, three questions and done.
  • Why do you want to work at Stripe specifically?
  • Tell me about a significant technical challenge you faced and how you handled it.
  • Describe a project you worked on that had meaningful impact.

“I had an answer ready but it felt a bit rehearsed coming out.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding screen, some kind of company-matching problem with weighted fields. Pretty niche variation on a fuzzy-matching theme, not what I was expecting.
  • Given a list of candidate companies and a target company, where each company has fields like phone, email, and name each carrying a different weight, return all candidates whose total weight of matching fields meets or exceeds a given threshold.

“The base problem wasn't too bad but the threshold-as-parameter part tripped me up a little.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding round for a software engineer role, and it was not what I expected. No LeetCode grind, just a practical parsing problem that felt more like real work than an interview. Deceptively tricky once you get into the edge cases.
  • Write a parser that reads lines from a file or stdin, where each line has five whitespace- or comma-separated tokens (timestamp, user ID, action, resource ID, status). Handle malformed lines, normalize datetime fields, and aggregate message counts by status. Be prepared to swap in other grouping strategies.

“I thought the aggregation part would be the hard bit but it was the parsing that ate my time.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding round with a graph/similarity problem that looked like a straightforward matching exercise until the indirect-hop requirement showed up. Not a typical LeetCode grind, more of a domain-modeling problem with some BFS flavor to it.
  • Given a list of user records where each field has an associated weight, a target user ID, and a similarity threshold, find all users similar to the target either directly (match score exceeds threshold) or indirectly through exactly one intermediate user where each consecutive pair is directly similar. Return the combined set.

“The weighted field matching part was fine, just iterate and sum.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding screen focused on a graph traversal problem dressed up as a user deduplication/entity linking task. The problem itself was interesting but the weighted similarity piece added enough complexity that I spent way too long on setup before getting to the actual BFS.
  • Given a list of user records with fields like name, email, and company, plus per-field similarity weights and a score threshold, find all records reachable from a target user within two hops in the resulting link graph.

“I got tripped up building the pairwise similarity matrix first, which burned a good chunk of time.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding screen for a software engineer role. One problem, math-heavy, not as straightforward as it looks on the surface.
  • Given a list of order items where each item has a base price, a quantity, a per-unit price decrement, and an optional price floor, plus a flat shipping cost, compute the total cost of the order using the incremental pricing rule.

“I knew the arithmetic series formula but blanked on whether to apply it directly or just loop.”

View Post