Applied online, contacted by the recruiter to set up an initial recruiter screen. Soon I got invited for tech screen (45 mins for coding, 15 mins for discussion/questions). The tech question got 4 parts, I finished 3 parts, and the last part (4th part) didn't get enough time. The interviewer said, don't worry about the optimization/time/speed, just focusing on to get the code to work. I got a few closing brackets errors/bugs, but I was still able to fixed them myself. I finished first 3 parts within 30-35 mins (with proper testing and validation), the interviewer didn't want to go to the 4th questions, and he asked two questions around 3rd question - like what if there are spaces, what if users input bad values. I was able to quickly solve his new add-on questions. He had no choice but gave me the 4th question. He told me that I do not need to finish all the questions. I wasn't able to finish last question, as I was in the middle of doing the last question, the time hit the 45 mins, he stopped me, saying time was up, and he was like "That's okay, I rarely see people managed to finish the last question". A week after, I got rejected by the email. I followed up with the recruiter, he told me that the Tech Interviewer put the note as my code had many bugs - because I missed closing brackets a few times. The recruiter was a pretty nice guy. I thanked him for helping me find out the reason/feedback. However, I felt like "What??" During the last 15 mins of tech interview (for asking questions), we chatted, the tech interviewer told me I was doing pretty good, didn't mention anything about closing brackets issue. But he rejected me for having "many bugs", which it's closing brackets in the note, apparently. Even I had a few closing brackets issues, I was able to fix them myself, and finish the first 3 questions with proper testing within 35mins." Anyway, I heard from other people, they said this company is very strange when hiring people. Some people didn't even finish 3rd question, got invited to the onsite interview, while others who finished 3 or 4th questions got rejected sometimes.

The interview process is straightforward: 1. Phone screening with a recruiter 2. Technical screening (1h) 3. Onsite interview preparation with a recruiter 4. Onsite interview (5h) As others have pointed out, Stripe is trying to be refreshing by avoiding the dreadful algorithm questions, and instead focusing on hands-on exercises: bug squash, real-world functions/projects implementation, ... I was invited for an onsite interview but decided to withdraw my application after accepting an offer from another company in the meantime. I had a very poor experience because of the recruiter in charge of my application. The recruiter forgot to call me for our initial phone screening. I can understand this happens, but she never apologized for it, and instead, a few hours later, she rudely sent me an automatic email to reschedule. She called me late for that second screening, and rushed it: the call lasted less than 5 minutes and did not give me the opportunity to ask any question. That same recruiter was also in charge of giving me an onsite interview prep: she called me for exactly 3 minutes, and repeated very quickly some very high-level information I already had by email. Once again, no opportunity to ask any question. On the bright side, the engineer who interviewed me during my technical screening was very nice & communicative. The interview went very smoothly, and I had plenty of time to ask questions. The technical screening question was also refreshing by focusing on solving a simple problem while evaluating the code quality, communication, and testing. In the end, the technical screening gave me a positive feeling, but the recruiter experience was awful and gave me a negative overview of the company.