← Back to Directory

Stripe interview notes, page 23 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

Jun 2026
Stripe coding screen for a software engineer role, one problem but it had a sorting requirement buried in it that I completely missed the first time through.
  • Given two CSV files each with a header row, merge rows from both files where the values in a specified field column match exactly. Output each merged row as all columns from the first file followed by all columns from the second. The output must be sorted by an 'order' field present in the header.

“I got the join logic working fine, matched on the field name, combined columns, seemed good.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe technical phone screen for a software engineer role, heavy on implementation details and design reasoning. The whole session revolved around one meaty coding problem with a lot of follow-up layers baked in.
  • Design and implement a payment-to-invoice matcher. Given a list of invoices (id, amount in integer cents, date), a payment string (with or without an explicit invoice id), and an optional forgiveness threshold, write a function that matches the payment to the correct invoice and returns a canonical output message. Walk through your data structures, parsing approach, and matching priority rules.
  • Why should you represent monetary amounts as integer cents rather than floating point numbers?
  • Describe the test cases you would write for this payment matcher, covering explicit id matching, multiple candidates with the same amount, forgiveness boundary conditions, tie-breaking, and regression coverage.

“This looked manageable at first glance and then kept growing.”

View Post

Stripe·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Stripe PM interview with a product strategy question about why Stripe has made certain bets outside its core payments business. One question, no fluff, but it required actually knowing the company well.
  • Why did Stripe launch initiatives like Stripe Atlas and Stripe Press, and why did they acquire a platform like Indie Hackers?

“This one tripped me up more than I expected.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe debugging round for a Software Engineer role. Four steps total, and I made it through the first two okay but ran out of time on the third. The interviewer was nicer about it than I deserved.
  • Given a broken codebase in a sandboxed environment, set up the environment correctly so the test suite can run.
  • A test is failing due to multiple bugs. Find and fix all of them.
  • A second failing test is presented. Identify and fix the bug under time pressure.

“This part was fine.”

View Post

Stripe·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Interviewed for an EM role at Stripe and got a question that sounds philosophical but is actually pretty practical once you sit with it.
  • What kinds of engineering manager goals are fundamentally impossible to capture with KPIs?

“I fumbled this a bit because my first instinct was to list soft skills and call it a day.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe technical screen for a software engineer role. One question, but it had enough moving parts to keep me busy for a while. The debugging angle made it feel more practical than a lot of API questions I've seen.
  • You have a chain of 5 sequential API requests. The first two succeed but the next three fail because they rely on a hard-coded ID instead of one generated dynamically by the first request. How do you fix this so the whole chain succeeds?

“My first instinct was to just say 'parse the response and store it in a variable' and I think I undersold the answer for a minute there.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Stripe system design round for a software engineering role, focused entirely on a single merchant deduplication problem broken into three progressively harder parts. The question was well-structured but the fuzzy matching and clustering sections caught me more off guard than I expected.
  • Given a stream of merchant records with fields like merchant_id, name, address, and phone, how would you detect and remove exact duplicate merchants?
  • How would you extend that deduplication to handle fuzzy or near-duplicate merchants, where records might differ in casing, punctuation, whitespace, or phone number formatting?
  • How would you cluster merchant records using a similarity function like Jaccard on name and address n-grams, grouping records that exceed a similarity threshold? Also discuss the complexity and how you'd scale this.

“This part was fine.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe SWE interview that was basically a graph/similarity problem broken into three progressive parts. The problem itself was well-designed, I'll give them that, but getting ambushed by part 3 after thinking I was done with part 2 was a whole thing.
  • Given a list of user records with fields like name, email, and company, and a weight map assigning each field a numeric weight, write a function that returns all record IDs directly linked to a target user. Two records are directly linked if their weighted field-match score meets or exceeds a given threshold.
  • Extend the previous solution so that for a given target user, you return all records reachable within exactly two hops in the similarity graph, meaning direct matches plus records that are directly linked to any direct match.
  • Further extend the solution to return all record IDs in the same connected component as the target user, meaning any record reachable through any number of hops in the similarity graph.

“Pretty approachable as a standalone problem.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe technical screen for a software engineering role. The whole thing centered on a single debugging scenario inside a custom HTTP library, and it went deeper than I expected for what felt like a contained problem.
  • You have a custom HTTP library where two test cases involving 301 redirects are failing. One involves a file stream and one involves binary content. The binary case times out at the post step. The call stack is deep and the helpers are barely commented. Walk through how you'd isolate the bug, write a minimal reproduction, and propose a fix that doesn't break the non-redirect paths.

“I spent probably the first five minutes just staring at the setup trying to figure out what I was even supposed to touch.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe coding screen, pretty focused on low-level string/display logic rather than the usual algorithmic stuff. One question, not too long, but there are more moving pieces than you'd expect at first glance.
  • You're given a bitmap lookup table that maps each character to a 2D grid of pixels, where '#' is a lit pixel and ' ' is unlit. Write a function that takes a character, looks it up in the table, and prints its bitmap row by row. Cover how the table is structured, how you handle characters that aren't in the table, and how you emit each row.

“I went straight to the happy path and forgot about missing characters until the interviewer nudged me.”

View Post