← Back to Directory

Stripe interview notes, page 3 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·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Stripe PM interview with a product design question focused on Google Maps and small business engagement. Pretty open-ended, which I wasn't fully prepared for coming from a more structured background.
  • How would you redesign Google Maps to drive more engagement with small businesses?

“I went straight to features, which was probably the wrong move.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe tech screen for a new grad software engineer role in Canada. Three-part coding question, got tripped up in the middle section but recovered, and the whole thing felt like a coin flip by the end.
  • Three-part coding problem: solve each section progressively, with increasing complexity.

“Part one went clean, dry run and everything.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding screen for a software engineer role, one question the whole time, pretty focused on payment matching logic. Not a trick question but the ordering piece tripped me up more than I expected.
  • Given a payment and a list of candidate transactions, along with a set of matching rules and an ordering criterion, implement a function that returns the single best matching transaction (or null if none qualify).

“The rules part felt obvious once I started coding but the ordering piece is where I fumbled a bit.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding interview, looks like a follow-up to a classic multi-currency balance problem. The twist here is adding a constraint that no balance can go negative, which sounds minor until you're mid-implementation.
  • You have a system tracking per-account, per-currency balances. Given a list of transactions, process them in order but reject any transaction that would cause a balance to drop below zero. Return the final state of all balances.

“The base version of this problem is pretty standard, but the rejection logic tripped me up a bit.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe integration round for a software engineer role, Python-based, focused on a reconciliation problem across five questions. Managed to get through three of them.
  • Given a set of transactions and expected balances, implement a reconciliation system that identifies discrepancies between the two.

“Got through the core logic fine but the last two problems ran out of time.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Stripe for a software engineer role, focused entirely on building a ledger service for a payments platform. Pretty deep dive, way more nuance than I expected going in.
  • Design a ledger service for a payments platform with at least two APIs: one to record a financial transaction between parties, and one to return the current or historical balance for a merchant.
  • How would you represent monetary amounts in your API and database to avoid precision errors, and what are your rounding rules?
  • How do you make the record_transaction endpoint idempotent so that client retries don't result in double-counted transactions?
  • How do you ensure atomicity when recording a transaction that involves both a debit and a credit?
  • How would you design the storage layer to support fast balance lookups at scale, given a potentially huge append-only ledger?
  • How would your ledger handle edge cases like refunds, chargebacks, voids, and multi-leg transfers?

“I started with the APIs and felt okay about the surface area, but the money representation question is where I stumbled.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe technical screen focused on a parsing and aggregation problem. Pretty straightforward on the surface but the edge cases around normalization tripped me up more than I expected.
  • You're given a large input where each line is a series of key-value pairs separated by semicolons. Parse every line, normalize the values, and return the top 3 most frequent values per key, sorted by count descending and then alphabetically.

“I jumped straight to the nested hashmap structure which was fine, but fumbled the tie-breaking sort for a bit.”

View Post

Stripe·Software Engineer·Hiring Manager Screen

Apr 2026
Behavioral round at Stripe for a software engineering role, hiring manager style. Pretty standard stuff but the 'why Stripe specifically' question tripped me up more than I expected.
  • Walk me through your resume, focusing on the decisions you made and the impact you had.
  • Why do you want to join Stripe specifically? What draws you to the mission, product, or team?
  • Where do you see your career in two years, and how does this role fit into that?

“I'd done this a hundred times but still rambled in spots.”

View Post

Stripe·Software Engineer·Take-home Assignment

Apr 2026
Take-home assignment from Bikemap, filed under Stripe for some reason. Three questions total, this is the second one. Pretty practical stuff, no tricks.
  • You're given a working curl command that makes a POST request to an API endpoint (with URL, headers, JSON body, and auth). Rewrite it in a programming language of your choice, keeping everything identical, and confirm the response matches.

“Pretty much a sanity check on whether you can read an HTTP request and translate it into actual code.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026
Stripe coding round for a software engineer role. The problem looked like a calendar/scheduling utility but the edge cases around boundary validation made it way harder than it sounded. You also had to write your own tests, which I wasn't fully prepared for.
  • Given a date range and a weekly recurring schedule configuration, generate all valid 30-minute time slots within that range. The first and last days must be strictly validated so no slot starts before the range's start time or ends after the range's end time.

“The core logic wasn't too bad once I got the weekly schedule iteration working.”

View Post