I applied through a recruiter. I interviewed at Stripe (Seattle, WA) in Apr 2021
Interview
Got contacted by the recruiter from LinkedIn, the interview process was pretty standard, one phone screen and then 5 rounds of virtual onsite (coding, system design, BQ, Integration, Bug Squash, etc.)
Interview questions [1]
Question 1
Their on-site interview was different than most other companies. I'd like to mention two rounds, one "Integration", one "Bug Squash", which both required you to download some code source from git repo and you would need a local environment setup to run.
Integration round need you to understand HTTP Rest calls, parsing some Json and sending requests to some API server, I managed to get the code completed with some googling of new libs/apis.
Bug Squash round need you to understand their code base and fix multiple bugs based on some test case failures.I was able to fix partial of those, what I could tell was that some bugs tend to be easy but some could be difficult, especially when code was compact, lack of comments, or it touched some advanced componments of a coding language which you probably never/rarely used.
There's no much need to prepare hard for their interview and I didn't expect to pass interview from the beginning, just try your luck.
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