Stripe Software Developer interview questions

Insulting, scrambled, and unprofessional is perhaps the easiest way to describe what interviewing with Stripe is like. The technical question begin with the interviewer copy/pasting a long 4 paragraph problem statement for part 1a of the interview. The interviewer then acted impatient as I tried to read through this lengthy problem statement, of which at least 75% of it was unnecessary. Once this was completed, and I confirmed with the interviewer that we both understood the problem similarly, it was mentioned that I should "write production-level code". Totally acceptable, and that had me diving into a discussion of the areas that I would tackle there while building out the solution, such as dependency injection, splitting fundamental pieces of code into manageable modules, commenting out where I'd otherwise emit logging or telemetry data, etc. I was then informed that we didn't need to bother with any of that. So, with that in mind, I wrote out some non-production "production" code to solve the problem. Along with some unit tests. We then moved on to part 1b, which was another 4 paragraph monstrosity, requiring me to read through and parse it once again as the interviewer acted disinterested and impatient. Following this, we moved on to part 2, which was a 5 (!) paragraph description. This is where things somehow turned even worse. It turns out that there was a statement hidden deep within one of the paragraphs phrased as "...what would happen if...". Not having caught that single word "would" caused my interviewer to lambast me for modifying data based on the rest of the requirements when this was only supposed to return the possibility without actually modifying anything. I can understand looking for people who can parse through overly-lengthy requirements descriptions and extract the necessary bits, but to do that during a 45 minute interview session, in a very non-standard, high-stress environment, while at the same time expecting them to write not-production production code, is insulting, derogatory, and simply unprofessional. Having an interview unequipped to handle anyone who codes differently from themselves is another negative occurrence here that happened far too many times. I would start writing something out experimentally (and make it clear upfront that I wasn't sure if this was the right course, but we'd quickly figure that out), and they would immediately stop me and ask why I was doing something the way I was. Overall, this was the worst interviewing experience I have ever had in the industry thus far. Hopefully the worse I will ever have as I can't imagine they can get much more insulting than this.