Software Engineer applicants have rated the interview process at Stripe with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 45.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 21 days to get hired, when considering 242 user submitted interviews for this role. To compare, the hiring process at Stripe overall takes an average of 26 days.
Common stages of the interview process at Stripe as a Software Engineer according to 242 Glassdoor interviews include:
Phone interview: 42%
One on one interview: 23%
Skills test: 14%
Presentation: 9%
Group panel interview: 6%
Background check: 2%
Other: 2%
IQ intelligence test: 1%
Personality test: 1%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 4 weeks. I interviewed at Stripe in Dec 2021
Interview
A recruiter reached out in November 2021.
We scheduled an initial call, and the next step was a technical screening over a video call with an engineer that I scheduled for a month later in December.
The interview question itself wasn't too bad and not the standard LeetCode-type questions. However, the interviewer didn't introdce themself and didn't ask for my introduction either. We jumped straight into the problem. And when we got into the problem, it was mostly silent on their part unless I had specifically asked a question. It didn't feel very collaborative at all, and like someone else here described perfectly, it felt more like a proctored test.
Interview questions [1]
Question 1
The technical screening was a three part question, each part building on the previous question.
1. Given a store log which includes closing times and whether or not customers were present, calculate a penalty score (i.e. add to the penalty score if customers were present after the store was closed or if no customers were present while the store was open).
2. Find the best closing time.
3. Given an incomplete log with possibly invalid data , find the best closing time for all logs.
First an OA which is very hard, you have to be really fast. Then HR call and then phone round. Unfortunately I got unlucky and my interviewer was doing something else while doing the interview, he was muted and I had to ask for his attention twice. Of course in the end he said I did very well and one day later I was rejected. The phone round is not particularly difficult but you have to be fast and talking too much will cost you.
Interview questions [1]
Question 1
They have a bunch of questions about string parsing, more often than not you will need to read a CSV so know how to do that, and know how to use the split function.
1 round of team screen - go/no go with a multi step problem
Design - classic interview
Integration - work on integrating some new systems
Bug bash - find and solve a bug
Programming exercise - same as team screen maybe a bit harder
I applied through a recruiter. I interviewed at Stripe in Jul 2026
Interview
started with a quick recruiter chat (checking developer infrastructure know-how), followed by a 45-min live coding screen where they look for production ready code. onsite was 5 rounds: coding, bug bash, integration, system design, and behavioral. bug bash was the most interesting part. they just drop you into a random repo with failing tests and watch how you track down the root cause. integration is pure API work - reading docs and wiring things up, but they lean heavy on error handling. sys design felt very grounded. instead of drawing huge scalable architecture, we basically just talked through failure modes and backward compatibility.behavioral was standard. across the board, stripe cares way more about readable code and communication than tricky algorithms.for prep, practice reading other people's code and fixing bugs. i had a mock on prepfully with a stripe SWE to test my bug bash process, and it really highlighted some messy debugging habits i had. tough loop, but it actually feels like real engineering.
Interview questions [1]
Question 1
Given a stream of Stripe checkout session events, identify sessions abandoned at each step of the checkout flow and calculate conversion rates