← Back to Directory

Stripe interview notes, page 18 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·Take-home Assignment

May 2026
Take-home assignment from Bikemap, though listed under Stripe for some reason. First of three questions, pretty straightforward file parsing task.
  • Given a JSON file containing bike map data (a list of records each with a coordinate field), read and parse the file using a standard JSON library and print the coordinates from the first 10 records.

“Pretty basic file I/O and JSON parsing.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding round focused on HTTP and JSON library usage, basically a test of whether you can read docs and wire things together under pressure. Not algorithmically hard but the devil is in the details.
  • Given a JSON file describing a sequence of HTTP requests (method, URL, headers, body, and expected response), make each call, parse the response, and verify it matches the expected output. Report any mismatches.

“The core trick here isn't the logic, it's knowing your HTTP and JSON libraries well enough to not fumble around.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe technical phone screen for a software engineering role. One meaty algorithmic problem that looked like a simple matching exercise until the follow-up questions started piling on.
  • Given a list of payments, a list of invoices, and a numeric tolerance value, implement a matching algorithm that applies three layered rules: first match by invoice ID, then by exact amount (earliest date wins), then by amount within the tolerance range (again earliest date wins). Return matched pairs and any unmatched items. Also discuss data structures for efficient range lookups on amount and how processing order affects results.

“I got the first two layers down pretty quickly, the id lookup is just a hashmap and the exact-amount fallback is another map keyed by amount.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe SWE interview with a meaty simulation problem that kept growing in scope, part by part. Each part added a new constraint on top of the last, so if your data structures weren't flexible enough early on you'd be rewriting half your code by part 4.
  • Design and implement a load balancer simulator that routes long-lived WebSocket connections across m backend servers, supporting CONNECT, DISCONNECT, and SHUTDOWN request types with rules for least-loaded routing, object stickiness, per-server capacity limits, and connection eviction on shutdown.

“This was a single problem with five escalating parts.”

View Post

Stripe·Software Engineer·Recruiter / HR Screen

May 2026
Stripe recruiter screen for a software engineer role that turned out to be way more about personal career motivations and company intel than anything technical. A few questions genuinely threw me off because they felt more like HR interrogation than a typical screen.
  • The compensation for this role seems below industry benchmarks. Are you okay with that, and are you satisfied with what you currently make?
  • Have you thought about leaving your current employer, and what's driving that?
  • How do you figure out if a company's culture is toxic, and what signs would you actually look for?
  • What do you know about where Stripe stands on going public, and would that affect your decision to join?

“This one felt like a trap but I'm not supposed to say that word.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe AI round for a software engineer role, and it was a genuinely confusing experience. The task itself wasn't hard but the interviewer seemed to be testing something I couldn't quite pin down, and I kept second-guessing every move.
  • Build a rule parser using AI assistance.

“The problem itself was fine, not especially tricky.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding screen for a software engineer role. Pretty straightforward problem but they care a lot about how you define your inputs and handle edge cases, not just whether you get the right number.
  • Given a list of order items (each with a SKU, price, and quantity) and a flat shipping cost, write a function to compute the total order price. Define your input format and state any assumptions about tax or currency.

“I jumped straight to the math and forgot they wanted me to define the input schema first.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe coding screen, probably for a backend or data engineering role. The problem was a record linkage thing where you score pairs of user records using weighted field similarity and return which ones are linked to a target. Sounded manageable until I actually had to think through the similarity function design.
  • You're given a list of user records, each with an id, name, email, and company field. Each field has a weight (summing to 1). Two records are considered the same user if their weighted similarity score meets or exceeds a threshold. Write a function that returns all record ids directly linked to a given target record.

“The setup took me a minute to internalize.”

View Post

Stripe·Software Engineer·Technical Phone Screen

May 2026
Stripe SWE screen, one coding problem the whole time. The problem looked like a boring CSV parsing exercise but there was enough edge-case logic in the scoring rules that it took me longer than I expected to get clean.
  • You're given three lists of CSV strings: transactions, scoring rules, and merchants. Each merchant has a base score. For every rule, scan that merchant's transactions and add different point values depending on whether each transaction amount is below, equal to, or above the rule's threshold. Sum all rule contributions across all transactions and return the final score per merchant in the original order.

“Spent the first few minutes just parsing the CSV strings and almost forgot to handle the base score, which would've been embarrassing.”

View Post

Stripe·Software Engineer·Onsite - Multi Round

May 2026
Stripe SWE interview that combined behavioral questions with a deep project walkthrough in the same session. The behavioral side was pretty standard but the project deep-dive was where things got real.
  • Tell me about a time you demonstrated leadership on a project or team.
  • Describe a situation where you had a conflict with a teammate or stakeholder. How did you handle it?
  • Walk me through a failure or a project that didn't go as planned.
  • Give an example of a time you took strong ownership over something outside your direct responsibilities.
  • How do you operate when requirements are unclear or keep changing?
  • How do you decide what to work on when you have multiple competing priorities?
  • Pick a significant past project and walk me through it: the problem, your role, the design decisions you made, the trade-offs, and the outcomes.

“Structured it as situation-action-result and it landed fine.”

View Post