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%
Personality test: 1%
IQ intelligence test: 1%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Stripe (Dublin, Dublin) in Mar 2024
Interview
I've read a lot about how Stripe's process was "different" - but even the limited amount I've experienced is honestly just worse than most others I've gone through.
Starting with an initial HR screen, the recruiter is very nice and helpful.
The next part was a live coding round.
People keep saying it's "not leetcode style" but thats just not true.
Just because the interviewer asks you to focus on solving it quickly and not care about efficiency this doesnt make it not leetcode style.
This also hamstrings you if you want to think out loud and explain your train of thought since when you actually think about the problem you don't just want to "get it done" - you want to do it right.
This part was very frustrating since I had an interviewer who also kept interjecting and actually focusing on efficiency (for example asking why I initialized a variable where I did or why I was considering implementing a certain approach instead of another) even though he asked me to disregard it.
At the end of the day this part is basically a speed coding interview and in order to complete it you need to stop being an engineer and just write the fastest, and probably worst, code you can.
This could be a much better experience if just given to the candidate without such a rigid time limit - or if it were a more digestible problem solving which you can actually show your skills as an engineer and not just as someone who can write code.
This is honestly a red flag since as an engineer I never consider just finishing something as quickly as possible a positive approach - youre at a disadvantage if you're a seasoned developer and fresh off learning how to code.
Interview questions [1]
Question 1
Leetcode style question without caring about efficiency
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