Stripe Software Engineer Interview Experience — Five Onsite Rounds Including a Superhero Dispatch System
Company: Stripe
Role: Software Engineer
Round: Onsite
Seniority: General
Outcome: Rejected
The Stripe recruiter reached out saying I could interview for L3, so I figured I'd give it a shot. It wasn't like I absolutely had to go, though, because I'd heard it's really cutthroat.
In the end I didn't pass, and it stings a bit — I still feel like I have something to prove. So I wanted to turn that frustration into an interview writeup to help everyone out.
Two of the rounds were pretty new questions.
**Round 1 AI programming:** A few days before the interview the recruiter told me this round had been changed to an AI round. Kind of unlucky timing. The question was to write a rule parser, split into several parts. My advice: write fast, because you really only get 30 minutes of actual coding time. Also, it's not very clear what exactly they're evaluating. I read through the AI-generated code and could explain all of it without any problems, and wrote test cases as needed too, but the feedback said I still didn't explain my thinking enough. Kind of speechless.
**Round 2 Debug:** Mako, an old question. But I have to complain about this one — even if you know the question ahead of time, debugging all of it within the time limit is still really tight. If someone saw this question for the first time and managed to debug everything within the time limit, that would honestly be impressive.
**Round 3 Integration:** Bike map, another old question. As long as you can get through more than 3 parts you should be fine.
**Round 4 BQ:** This manager also asked me a lot of project-related questions. Something a bit different was that he also asked a lot about communicating with customers.
**Round 5 Design:** A superhero dispatch system. I was completely unprepared for this one. A regular person gets into an accident, a dispatch goes out, and a superhero picks up the job to come save you. A bit of an abstract setup, but it was actually pretty fun to design, lol. Kind of like Uber, except the dispatch traffic wouldn't be nearly as crazy as Uber's, and this design didn't involve any API design at all, unlike the other questions. In the end the feedback said my justification for the technology choices wasn't strong enough.
A bit of a shame, but I prepared what I could prepare, so — move on.