Technical phone screen. The interview started out like most, getting to know each other, what our backgrounds are, stuff like that. The prompt for the interview was incredibly wordy though. About 8 paragraphs to say something that could be said in 1. Took about 5minutes out of the interview just to read the whole thing, then another 5 minutes to just clarify what exactly was actually being asked. It was an algorithm question with multiple parts, where once one part was completed, another part was added on. The interviewer stated (repeatedly) that performance was not critical, they were looking for clean, well tested code that works rather than whether the algorithm performs in O(n) time or something similar. So working through the problem I repeatedly said that given more time I would refactor it to run faster, and identified the time the current algorithm runs in and the time I think I could optimize it to (and what I would do to optimize it), and that I am doing it that way because of time crunch. Interviewer seemed satisfied with that. Upon completing part 1a, 1b, and 2a of the challenge, we ran out of time. Spend about 1/3 of my coding-time (time not spent clarifying the prompt) writing tests. Despite the interviewer saying testing the code is important, he would often say something like "dont worry about writing more tests lets move on" The last 10 minutes of the interview I asked some pretty basic questions about his experience at Stripe. Things like "do you feel like your work has an impact" and "whats the company culture like". These questions were deflected, no straight answer. He went off on some tangent about the ethics of the company and how Stripe is not the most ethical, but that they try to make up for it by doing some carbon-offsetting program which they also offer to their customers. Way outta left field with that stuff, kinda confusing why he'd bring it up. Got an email the next morning saying I was declined. Not really sure what their standards are, or how far they expect people to get in their prompt, but the interviewer had me feeling like I did well in the interview and that the code I wrote was clean and well-tested. He even hinted that they would probably bring me in for a virtual on-site.