Very pleasant people to speak with, but the process is a little wonky. One red flag is that, as others have mentioned, they have a bizarrely obtuse React CAPTCHA challenge that screams death by a thousand iterations. We spent about half the interview confirming the esoteric requirements. Like any other interviewee, I second-guessed whether pushing back on a bizarre user experience might be part of the test, but it really did not appear that way. Luckily, I passed, but I have no idea if this gave me a weak signal to the team or not. One of the final rounds was with other engineers, which was more of a discussion. It was a panel of 3, who kept talking over each other and framing the question differently. This left me guessing who might be the most important person to address, but still trying to satisfy all three panelists, to an extent. Again, I had almost no idea if I was giving a good answer here, having to read the reaction and tone of three separate engineers. I understand the desire to have multiple engineers on hand to help the decision along, but most processes have them as *shadow* interviewers so that the conversation is more focused. Not sure what happened here. Anyway, I lost out at the last round, and the recruiters were very gracious in extending a courtesy debrief over the phone. I mentioned some of these pain points, but of course the recruiters themselves are somewhat powerless to shape how the engineering team chooses to hire. I hope someone there is reading this and rethinks parts of the process, because again, the team was delightful to speak with otherwise.