Stripe

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·Onsite - Multi Round

Sep 2026

Did a virtual onsite for a Stripe SWE intern role, two parts: coding and an integration section. Finished most of it but left the last coding problem a little rough around the edges, and now I'm sitting here refreshing my email wondering if messy code kills an otherwise decent performance.

Coding problem where you needed to implement a solution, refactor it for cleanliness, and handle edge cases with your own test cases.
Integration section questions covering API behavior and how components interact.

“Got through 3 of 4 coding problems.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Aug 2026

A friend with 4 years of experience went through Stripe's API integration round and finished 2 out of 3 parts, explaining the approach for the last one but not actually coding it up before time ran out. Posting here to get a read on whether that's a normal outcome or a red flag.

In Stripe's API integration round, candidates are given a multi-part coding problem. Can partial completion (finishing 2 of 3 parts and verbally explaining the third) be enough to pass, or is full completion expected?

“Asking for a friend who ran out of time on part 3.”

View Post

Stripe·Software Engineer·Online Assessment (OA)

Jul 2026

Got an OA invite from Stripe for a Software Engineer role focused on Money Movement in London. Still in early stages, mostly trying to figure out logistics before diving into prep.

Is Python acceptable to use throughout the Stripe hiring process, or do they prefer statically typed languages?
How fast do interview rounds get scheduled after clearing the OA? Is it purely based on candidate availability?
What resources or prep materials are most useful for preparing for Stripe's interview process?

“Genuinely unsure about this.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe frontend coding round, one big component question that looked manageable but had enough wrinkles to keep you honest for the full session.

Build a UI component that accepts an array of name/amount pairs, renders the list with a text search filter and a minimum-amount filter, and highlights the item(s) with the highest amount in the currently filtered results in real time. Also explain your state management approach, how you compute the max efficiently, the time/space complexity, and describe edge-case test scenarios including empty lists, ties, non-ASCII names, and rapid typing.

“The base rendering was fine.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe coding round, one question about bitmap fonts and rendering characters as grids. Niche problem but the core logic isn't too bad once you break it down.

You're given an array or string of 0s and 1s representing a bitmap font. Write code to render each character as a grid where 0 becomes '.' and 1 becomes '#', and support concatenating multiple characters to print whole words.

“The rendering part clicked pretty fast for me, map bits to characters, chunk by row width, done.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe coding screen for a software engineer role. One problem, the whole time, and it was deceptively tricky to get right. The sliding window part was straightforward enough but the event deduplication logic is where things get messy if you're not careful.

Given transaction logs sorted by timestamp, each with a merchant ID, status code, error code, and count field: monitor each (merchant_id, status_code) pair using a rolling window. For each log entry at time t, the rolling count is the sum of all counts for that pair within [t - window_size + 1, t]. Emit a TRIGGER event when the rolling count crosses from below threshold to at or above it, and a RESOLVE event when it drops back below. No duplicate consecutive events per pair. Return all events in chronological order.

“The sliding window itself wasn't the hard part.”

View Post

Stripe·Data Scientist·Technical Phone Screen

Jul 2026

Stripe DS interview with a meaty marketing attribution case. Five sub-parts, all SQL-heavy, and they really wanted you to think about metric design before touching any code. Felt more like a take-home squeezed into a live session.

Define a primary success metric for the marketing campaign that is attributable, time-bounded, and robust to activity spikes. Include two guardrail metrics and write out the precise formulas.
Write SQL to compute, for each contact week and country, the 14-day post-contact purchase conversion rate and average revenue per contacted user. Use only the first contact per user and exclude purchases that happened before the contact time.
Write SQL to build a matched baseline: pair each contacted user to one non-contacted user in the same signup week and country, breaking ties by smallest user_id, then compute the 14-day purchase rate for the matched group.
On a specific date, contacted-user conversion in the US drops 20% versus the prior 7-day average. Write SQL to break this down by device and product_id, showing count contacted, 14-day conversion, and delta versus the prior period for each slice. Return the top 3 slices by approximate contribution to the drop.
What check would you add to make sure your metrics aren't biased by users who unsubscribed immediately after being contacted?

“I went with 14-day post-contact purchase conversion using only first contacts, which felt right.”

View Post

Stripe·Data Scientist·Technical Phone Screen

Jul 2026

Stripe DS interview with a meaty experiment design question built around a merchant subscription model. The whole thing was one big multi-part case and it went deep fast.

You built a ranked list of merchants likely to adopt Subscription. Design a randomized experiment to test whether targeting the top 50,000 with a sales or email nudge actually drives conversions. Walk through the RCT setup including control/treatment split, stratification by score decile and country, guardrails, and a staged ramp.
Compute the required per-arm sample size to achieve 80% power at a two-sided alpha of 0.05, given a baseline conversion of 2% and a minimum detectable uplift of 50% relative. Show the formula and the actual number.
Given a $5 outreach cost per merchant and an expected $120 gross margin over 90 days from a converted merchant, what precision threshold does the model need to break even on targeting?
What contamination risks exist when some customers transact across multiple merchants in the experiment? How do you handle merchants already piloting Subscription, and how do you attribute conversions when a merchant gets multiple outreach touches?

“I started with the split and stratification, which felt solid, but I fumbled a bit on the guardrails.”

View Post

Stripe·Software Engineer·Technical Phone Screen

Jul 2026

Stripe SWE interview with a payments-flavored coding problem. Pretty domain-specific which was a nice change from generic leetcode, but the complexity discussion at the end caught me slightly off guard.

You're building a payment processor. Given a fee table that maps (payment_type, payment_status) pairs to rates in basis points, and a list of transactions each with an id, type, status, and amount in cents, compute the processing fee for each transaction using floor(amount * rate / 10000), return 0 for unmatched rules, and return both the per-transaction fees in input order and the total. Discuss time and space complexity.

“The core logic clicked pretty fast, just build a dict from the fee table and do a lookup per transaction.”

View Post

Stripe·Software Engineer·Hiring Manager Screen

Jul 2026

Hiring manager behavioral round at Stripe for a software engineer role. Pretty standard stuff but a few questions had follow-ups I wasn't fully ready for. No technical coding involved, just a lot of talking about yourself and your work.

Tell me about the most interesting project you've worked on and what made it interesting to you.
Describe a time you ran into a problem you couldn't solve on your own. What did you do?
Can you walk me through a situation where you had to make a quick decision under time pressure? What was your reasoning?
What are your career plans going forward, and what do you look for most in a job?
How would you define success for yourself in your first six months on the team?
What are the top three qualities or traits you'd bring to this team?

“They dug into this one more than I expected.”

View Post

Stripe interview FAQ

What rounds are in the Stripe interview?

Candidates most often report a technical phone screen (206 write-ups), a system design round (39), a behavioral / leadership round (22) and a product sense round (20).

What does the Stripe technical phone screen cover?

Across 206 technical phone screen write-ups, the most tagged question topics are Technical Trade-offs (210 questions), Algorithms & Data Structures (202) and System Design (107).

What is asked in the Stripe system design round?

Across 39 system design write-ups, the most tagged question topics are System Design (73 questions), Technical Trade-offs (62) and Data Modeling (29).