Stripe interview notes, page 4 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 big open-ended budget question. No idea what round this was but it felt like a product strategy case, the kind where there's no clean answer and you just have to commit to a direction.

You've been hired by an airline consortium to improve public perception of air travel. You have a $10M budget and one year. What do you do?

“I spent way too long trying to diagnose the perception problem before actually proposing anything.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe software engineering interview with a CSV parsing and validation problem. The question was more about careful rule implementation than raw algorithmic cleverness, which I didn't fully appreciate until I was halfway through writing broken logic.

Given a CSV string with a header row and data rows, output VERIFIED or NOT_VERIFIED for each data row based on four rules: all 6 fields must be non-empty, the fifth column must be between 5 and 31 characters, the second column must not contain any blocklisted words, and the second column must share at least 50% of its words (case-insensitive) with either the fourth or fifth column.

“The word-overlap rule is where I fumbled.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe coding round for a software engineer role, one problem the whole session. The problem looked like a clean DP question on the surface but the skip mechanic made it messier than expected.

You have N factories in a sequence, each with multiple options described by a cost and a distance. You must pick exactly one option per factory you decide to build, and you must skip exactly one factory entirely. The goal is to minimize the total selected costs plus the sum of absolute differences between consecutive built factories' distances (the skipped factory is removed from the sequence, so its two neighbors become adjacent). How do you solve this, and what's the complexity?

“My first instinct was to just try every possible skip index, which is N candidates, and for each one run a DP over the remaining N-1 factories.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe coding screen for a software engineer role, pretty focused on data validation logic. Nothing flashy, just a clean implementation problem with some edge cases that could trip you up if you weren't paying attention.

Given a list of KYC records where each record is a list of field values, write a function to validate each record against two rules: no field can be empty after stripping whitespace, and the fifth column must be at most 50 characters. Return the records that pass both rules. Target time complexity is O(R * N).

“I got the basic structure pretty fast but fumbled on the edge cases.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe SWE screen, basically one coding question with some follow-up discussion on complexity and edge cases. Pretty straightforward but they pushed harder on the theory side than I expected.

Given a string containing letters mixed with '*' and '&' characters, replace every '*' with '0' and every '&' with '1' using the language's built-in string replace method. Then discuss the time complexity and how you'd handle edge cases like Unicode or repeated characters.

“The replacement part took me about two minutes, nothing hard there.”

View Post

Stripe·Software Engineer·Online Assessment (OA)

Apr 2026

Stripe SWE interview with a KYC verification coding problem. Pretty domain-specific, which I wasn't expecting for a standard engineering round.

Given a list of business account records, each containing 6 KYC fields including a statement descriptor field, and a blocklist of generic descriptor strings, write a function that outputs VERIFIED or NOT_VERIFIED for each record. A record fails if any field is missing or empty, if the statement descriptor is outside a specific character length range, or if the descriptor matches any blocklist entry case-insensitively.

“The multi-rule layering is what got me.”

View Post

Stripe·Product Manager·Onsite - System Design / Architecture

Apr 2026

Stripe PM interview, one question about designing the SMS API for Twilio. Pretty open-ended and I wasn't totally sure if they wanted a product take or a technical architecture take, so I kind of did both and hoped for the best.

Design the SMS API for Twilio. Walk through how you'd structure the API, what endpoints you'd expose, and what decisions you'd need to make.

“I started with the developer use case, like what does someone actually need to send a text programmatically, and worked outward from there.”

View Post

Stripe·Product Manager·Onsite - Product Sense / Strategy

Apr 2026

Stripe product interview, one question about consumer pain points in online purchasing. Pretty open-ended and I wasn't totally sure how deep they wanted me to go on the solution side.

What are the biggest challenges consumers run into when buying things online, and how would you address them?

“I started with checkout friction and payment failures, which felt obvious in hindsight for a Stripe interview.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe coding round for a software engineer role. The problem was a KYC data validation exercise where you read business records from stdin and apply a bunch of rules across fields and records. Felt more like a backend systems task than a typical leetcode grind, which I didn't fully expect.

Given a stream of business records from standard input (each with fields like business name, address, tax ID, owners, and attached documents), implement a validation pipeline that checks format rules, cross-field consistency, duplicate detection across records, and mandatory document presence. Output per-record pass/fail results with reasons.

“The stdin/stdout part tripped me up more than the logic itself.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Apr 2026

Stripe coding round, one meaty question about bitmap compression that took up the whole session. More systems-flavored than pure algo, which I wasn't expecting from a coding interview.

You have a bitmap lookup table mapping characters to 2D pixel grids. Implement compress(table) and decompress(compressed) for this table, then use the decompressed glyph to render a given character. Also discuss expected compression ratio and the tradeoff between encoding cost and rendering cost.

“I started with run-length encoding on each row of '#' and ' ' characters, which felt obvious, but then they pushed on packing bits into bytes and I fumbled around for a bit.”

View Post