I applied online. I interviewed at Stripe (Singapore) in May 2026
Interview
Applied for a Software Engineer role at Stripe Singapore. The process started reasonably. Received a HackerRank coding assessment, completed it, and was invited to a 30-minute recruiter call. On that call I was told I would be moved to a pair programming round and that the recruiter would send over the details to book a slot.
That was over 3 weeks ago. Despite multiple follow-up emails from my end, I never received any response or update. No rejection, no rescheduling, no acknowledgement. Complete silence.
What stood out during the recruiter call itself: there was no background discussion, no fit assessment, no questions about my experience or what I was looking for. For a company of Stripe's caliber I expected at least a basic screening conversation. It felt more like a box-ticking exercise than a genuine evaluation.
Ghosting candidates after explicitly committing to next steps is poor candidate experience regardless of the outcome. A simple update either way would have been professional. Would not recommend applying if you value your time and expect basic communication standards from a recruiter.
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
I applied online. I interviewed at Stripe (Dublin, Dublin)
Interview
The position was in Dublin, but I interviewed with someone on the West Coast, which was where I was located at the time. The tech question round was multi-leveled as in build X, then add Y, then adapt for Z. Essentially, based on whatever "system", add these functions and change them to handle the input/output/question of the system. The interviewer was nice and better than 1-2 other companies I'd interviewed with in regards to responsiveness, communication, friendliness, etc.
Interview questions [1]
Question 1
Given a "system", build one function, then add another, then adapt and build something else. From a design-build problem, it was actually rather pleasant; the issue is that you spend a lot of time expecting interview questions and get tripped up on solving the "real-world problem" they give you.