Applied online and recruiter reached out for a quick phone screen to talk about the job and next steps. The next step was a technical coding interview where it was less like Leetcode style and more interactive and was advise to make it conversational. The technical question they asked was easy but only after you can get through the wall of text you need to read to understand the problem. The interviewer I feel was not very interactive at all as I was talking through the problem and stating my assumptions, there was no reaction from the interviewer. At some point during the interview it was clear they were looking at their phones as well. The question was done in 3 parts, each building on top of the other and I had passed the first 2 parts pretty accurately and ran out of time on the 3rd part but was able to give a quick overview of how I would approach it. In the end they decided to not move me forward. For an interactive interview where the goal is to work together with the interviewer, they were not very helpful or attentive during the process.
Interview questions [1]
Question 1
Write some API and build on top of it with further criteria
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