Stripe Interview Questions — Page 20

Stripe·Software Engineer·Take-home Assignment

Jun 2026

Stripe gave me a take-home coding task split into four sub-tasks, all centered around working with a map API and some geometric/landmark data. Pretty hands-on, no live coding pressure, which I appreciated.

Parse a JSON file containing geometric point/coordinate data and work with it programmatically.
Make an API request to fetch a map image based on the parsed coordinates and save it to disk.
Use the API to annotate the coordinate points onto the downloaded map image and draw connecting lines between them.
Read a second JSON file of landmarks, annotate each one on the map via the API, and for each landmark find and annotate its nearest point from the first dataset.

“Straightforward file I/O stuff.”

View Post

Stripe·Data Scientist·Technical Phone Screen

Jun 2026

Stripe data science interview that went deep on expected value calculations and model calibration. Four questions, all quantitative, no fluff. The kind of round where you either know the delta method or you don't.

Given a base purchase rate of 4%, a $50 incremental profit per true positive, and a $1 cost per false positive, compute the expected profit for three candidate operating points (A: TPR=0.70, FPR=0.12; B: TPR=0.55, FPR=0.05; C: TPR=0.80, FPR=0.20) over a cohort of 100,000 users. Which threshold do you pick?
Construct a 95% confidence interval for the expected profit at your chosen operating threshold. Walk through either a delta method or a bootstrap approach and explain what you're resampling and why.
Your model outputs probabilities. Describe and compute two calibration diagnostics you would use in practice.
How would you design a monthly drift test to check whether the chosen operating threshold is still optimal as the underlying purchase rate shifts over time?

“The formula itself isn't hard once you see it: 100000 times (0.04 times TPR times 50 minus 0.96 times FPR times 1).”

View Post

Stripe·Product Manager·Hiring Manager Screen

Jun 2026

Hiring manager chat at Stripe, pretty conversational. They wanted to hear about what I'd actually owned in past roles and where I was trying to go next, not a lot of curveballs.

Walk me through your project experience and what you personally owned.
What have you learned from your most significant projects?
What are you looking for in your next role in terms of scope, problems, and type of work?

“I'd done this kind of walkthrough before so I wasn't nervous, but I realized partway through I was spending too much time on context and not enough on what I specifically did.”

View Post

Stripe·Software Engineer·Onsite - Multi Round

Jun 2026

Went through the full Stripe Android Engineer loop: a screening coding round, a programming exercise, an integration round, a bug squash round, and a hiring manager chat. Five rounds across two days, all collaborative in style, nothing like the typical leetcode-grind interview. The unconventional rounds (integration and bug squash) are where I felt the most underprepared.

String parsing coding challenge: implement a solution that processes a string input and returns a result in a specific format, with subsequent parts building on the previous solution.
Same multi-part coding problem as the screening, but this time you're also responsible for writing unit tests and identifying edge cases for each part before moving forward.
Given an existing Android app with partial functionality, integrate a new class or library so that the UI behaves correctly end-to-end.
Given an unfamiliar codebase and a failing test case in a git issue (with a passing test for reference), identify and fix the root cause of the bug.
Walk through a complex project from your resume in detail, focusing on the logistical and decision-making aspects rather than the technical implementation.
Behavioral questions centered on AI: how you've thought about or worked with AI tools, and how you approach decisions in that space.

“This was the screening round.”

View Post

Stripe·Software Engineer·Onsite - System Design / Architecture

Jun 2026

Stripe system design round for a software engineer role. One meaty scheduling problem that looked straightforward until the edge cases started piling up.

Given a list of users each with a subscription start time and a notification cadence (daily, weekly, or custom interval), design a system that produces a schedule of email notifications to send over a given time window. Return a chronologically ordered list of notification events and discuss how you'd scale this to millions of users.

“I spent the first few minutes just generating timestamps and almost forgot to ask anything.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Stripe coding round, graph traversal problem that builds on a merchant-linking concept with weighted field matching. The twist was bounding the search to 2 hops, which sounds simple but has some edge cases that'll bite you if you're not careful.

Given a graph of merchants linked by weighted field-match scores, find all merchants reachable from a target merchant within at most 2 hops (directly or indirectly linked). Return the full set.

“The weighted scoring part from the base problem was already established, so this was really about layering BFS on top of it and capping depth at 2.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Stripe bug smash round for a software engineer role, focused on the Colander Python validation library. Fairly narrow scope but you really do need to know what you're doing with error handling internals.

You're given a broken validation pipeline using the Colander library. The error aggregation step crashes when some validators return null or empty messages. Find and fix the bug.

“Took me a minute to even see where the crash was coming from.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Stripe coding screen for a software engineering role, focused entirely on building out a parsing and validation layer for an email subscription pipeline. Pretty implementation-heavy with a lot of edge cases to cover, which I wasn't fully expecting.

Read and parse JSON from both a local file and an HTTP endpoint, then merge the two into a single in-memory structure with basic deduplication of subscriptions.
How do you handle I/O errors for both the file read and the HTTP fetch, and what does your error reporting look like to the caller?
How would you detect and surface schema mismatches between the parsed JSON sources and the expected output format?
Compare the combined subscription data against an expected JSON output and report whether they match, including surfacing specific differences when they don't.

“I went straight for a naive merge and only thought about deduplication halfway through.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Phone screen for a software engineer role at Stripe. The one question I saw flagged everywhere on forums beforehand showed up, so at least I wasn't totally blindsided. Speed mattered a lot here, both writing clean code and covering edge cases fast.

Implement a payment reconciliation system that matches transactions across two data sources and identifies discrepancies.

“This one circulates a lot so I'd seen it before, but knowing it's coming and actually executing under time pressure are two different things.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jun 2026

Stripe coding interview that revolves around a graph/union-find problem disguised as a data deduplication task. The problem sounds like a simple similarity check but the transitive linking requirement is what actually makes it interesting.

Given a list of user records with fields like id, name, email, and company, along with per-field similarity weights and a threshold, find all records transitively linked to a target user. Two records are linked if their weighted similarity score meets the threshold, and you need to return the entire connected component containing the target with no hop limit.

“I started with BFS which felt natural, but the interviewer kept pushing on what happens when n gets large.”

View Post