Stripe Software Engineer interview questions

228 Software Engineers have shared notes from their Stripe interviews, with the questions they were asked in each round. That is 99% of the 231 Stripe interview notes on Screna AI.

228 Software Engineer interview notes

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe coding screen for a software engineering role. One question, pretty focused on math and edge case handling. Not the most glamorous problem but it had more gotchas than I expected.
  • Implement a DISTANCE command that computes the great-circle distance in kilometers between two latitude/longitude coordinates using the Haversine formula. Validate that latitudes are in [-90, 90] and longitudes are in [-180, 180], returning ERROR for invalid inputs. Round to the nearest integer.

“I knew the Haversine formula existed but had never actually coded it from scratch.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Stripe system design screen for a software engineer role, focused entirely on a role-based access control problem with a twist around hierarchical account inheritance. The question had a lot of moving parts and the discussion went pretty deep into indexing tradeoffs and complexity analysis.
  • You have a list of (userId, accountId, role) assignments and an account hierarchy where roles inherit downward from ancestors. Given an accountId and a set of required roles, return all users who hold every required role on that account, either directly or through inheritance. Walk through your indexing strategy, how you'd traverse ancestors, and the time complexity.

“This one took me a minute to fully parse.”

View Post

Stripe·Software Engineer·Take-home Assignment

Jun 2026
Take-home assignment from Bikemap, three parts total. This is the third question, focused on sending POST requests for a list of coordinates with some color logic thrown in. Pretty self-contained once you've done the first two parts.
  • Given an array of 10 coordinate objects (each with lat and lon), assign each a color based on whether the latitude is positive or negative, then send a POST request per coordinate to a given API endpoint. How would you process these sequentially, and how would you approach parallelizing with bounded concurrency or handling transient failures?

“The color assignment part is trivial, lat >= 0 gets red, negative gets blue, fine.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe technical screen that went deep on a debt settlement graph problem. Started with the classic LeetCode formulation and then kept pushing on scale, pruning, approximations. Not a comfortable interview if you only know the textbook answer.
  • You have a list of debt records between people (lender, borrower, amount). What is the worst-case complexity of the backtracking approach to minimize the number of transactions needed to settle all debts, and where does it break down at scale?
  • What pruning strategies can reduce the search space in the backtracking solution for debt settlement?
  • How would you partition the debt graph into independent sub-problems to make the solution more tractable?
  • When hundreds of people are involved, exact optimization may not be feasible. What approximation strategies would you consider, and what are the trade-offs?

“I knew the net balance reduction step and could explain O(n!) in the worst case for backtracking, but I fumbled when they pushed on exactly *why* it degrades so fast.”

View Post

Stripe·Software Engineer·Online Assessment (OA)

Jun 2026
Stripe SWE interview with a KYC verification coding problem. The question was more rules-heavy than algorithmically complex, which honestly threw me off a bit because I kept second-guessing the edge cases instead of just implementing the logic cleanly.
  • Given a list of business account records (each containing 6 KYC fields like business_name, business_full_name, and full_statement_descriptor) and a blocklist of generic descriptors, write a function that outputs VERIFIED or NOT_VERIFIED for each record. The rules are: all 6 fields must be present and non-empty, the full_statement_descriptor must be between 5 and 31 characters inclusive, it must not match any blocklist entry (case-insensitive), and at least 50% of the words in either business_name or business_full_name must appear in the full_statement_descriptor.

“The word overlap rule is where I lost time.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe coding round for a software engineer role. One problem, but it had enough layers to keep you busy for the whole session.
  • Write a function `compute_total(items, shipping_cost, method)` that calculates the total price of an order. Each item has a price and quantity. Support two pricing modes: one where the unit price decreases linearly as quantity increases (with an optional floor), and another where the total cost for a quantity range is a fixed flat amount regardless of how many units fall in that tier. Add a flat shipping cost at the end.

“The incremental pricing part was fine, just a loop with a floor check.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe technical screen focused entirely on a data validation problem, three parts back to back with no warmup. It was more of a systems thinking exercise than a pure coding test, which I didn't expect.
  • Build a routine that parses a key-value record set, validates each record against a schema with required keys, types, and value constraints, and reports all validation errors with the offending key and reason. The solution must handle nested keys and both missing and extra fields.

“Three parts but they flow into each other, so you kind of have to design the whole thing before writing any of it.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe coding interview, looks like a follow-up to an earlier scheduling/email problem. This extension added plan-switching logic and honestly the state management got messier than I expected.
  • You have a list of users with billing plans and a separate list of plan changes, each with a timestamp. On the day a user switches plans, send an 'Updated' email. For all emails after that point, the new plan name should be used. How do you extend your existing email scheduling logic to handle this?

“The 'Updated' email on the change day tripped me up more than I expected.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe technical screen for a software engineer role. One coding problem, pretty focused on API chaining and runtime data handling. Left feeling okay about it but not confident I nailed the substitution piece.
  • You have a chain of 5 sequential API calls where the first two succeed but the next three fail because they use a hard-coded ID instead of the one generated at runtime by the first request. You've already extracted that ID from the first response. Write the substitution logic to replace the hard-coded ID in both request URLs and request bodies before each downstream call is sent. Also discuss safe templating approaches, handling nested JSON, and how you'd verify the substitution actually happened before dispatch.

“This is where I spent most of my time and still walked away unsure I got it right.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026
Stripe SWE interview with a meaty coding problem around payment matching logic. The problem looked like a straightforward lookup at first but the follow-up discussion on data structures and edge cases is where things got interesting.
  • Given a list of payments and a list of invoices, implement a matching algorithm with three priority levels: first match by invoice ID, then by exact amount (earliest date wins), then by amount within a tolerance range (again earliest date wins). Return matched pairs and any leftovers on both sides.
  • What data structure would you use to efficiently find invoices whose amount falls within a given range, and how does it handle deletions as invoices get matched?
  • If two invoices are eligible under the forgiveness rule and have the same date, how do you break the tie, and does the order in which you process payments matter for the final result?

“The id-based match felt easy and I got through it quickly, but I tripped on the forgiveness range part.”

View Post