J'ai postulé en ligne. J'ai passé un entretien chez Stripe (New York, NY) en janv. 2026
Entretien
Waste of time. Recruiter was nice, quickly scheduled phone screen. Had a positive experience with the engineer. Onsite was poorly organized and interviewers wanted you to fail. Onsite had 5 rounds: coding (similar to phone screen, implement a function, had a few parts), bug squash, behavioral, system design, integration. Last interviewers for integration did not even show up.
I can feel the "senior" engineers' vast ego from my monitor. At times they were not paying attention to what I was doing and I was talking to the void.
I ask a simple clarifying question on system design - sorry, could you repeat?
Asked me about a "missing" component in my design - I drew it 2 minutes ago.
Some deep dive questions were interesting and it showed the engineers had some depth, but it was domain specific and they did not have the breadth to do general deep dive.
Would not want to work on a team with other senior engineers like this. Just read the posts about politics and people stealing others credit. I came from a Faang with bad reputation, but even there nothing quite as bad happened.
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.
Questions d'entretien [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
J'ai postulé via un recruteur. J'ai passé un entretien chez Stripe en juil. 2026
Entretien
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.
Questions d'entretien [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