Didn't actively apply, responded to a sourcer that reached out. The process is your standard recruiter screen, meet with hiring manager, take home assignment, and full day "on-site" interview via Discord. Overall, everyone was super nice and accommodating during the process. I met some really great people and had general excitement for the product, the vision, and its future. This especially given the current products I work on that entertain hundreds of millions around the world. This seemed like a wonderful new space to build great new user experiences, in an area to help with growth. However, similar to what other's have mentioned here, be prepared to be ghosted after the interview. The final talent person I talked to during the on-site ended with a "we'll follow up with a call or email in a couple of days", but I ended up having to re-engage after hearing nothing back for 3 weeks. Given the time sink, which I think was about ~10 plus hours, at least keep in contact or provide updates (even if it's a yay or nay) vs zero communication. This can help interviewees manage other conversations they are having with other companies without keeping others in limbo. Only other feedback, have collaborative environments ready for coding exercises, so you don't waste time setting up vs working towards a resolution. If operating in ambiguity around this is the point, be up front on that.

In short, I had a bad experience here. The tech screen portion was poorly run due to a lack of communication and clarifying expectations. The screening call with the recruiter was pleasant and straightforward. Next, the call with the hiring manager was similarly pleasant and straightforward; however, he repeated his thoughts that teams should consist mainly of junior engineers and that there were very few principal engineers in the company. His remarks gave the impression of ageism towards experienced candidates and that the deck was already stacked against me; it also gave me a negative impression of possible career growth and, thus, little to look forward to. Next was a tech screen. The interviewer was friendly, but it was poorly run. The task was to build a socket server servicing multiple clients; straightforward enough but the instructions were extremely terse. I wondered what else they were looking for (architecture, class design, error handling, fault tolerance, testing, performance, style, docs, etc?), but the interviewer wouldn't answer any questions and just shrugged. It turns out they were looking for speed. I can go fast when called for but in my experience, most interviewers are looking for more than speed. I created a socket server that handled communication with multiple clients but was rejected because I wasn't fast enough. I left the interview feeling frustrated at how inefficient the process was. The whole thing felt like a waste of time simply due to poor communication. I would have had a better experience if the interviewer had simply communicated. In hindsight, however, I doubt Discord would have been a place I would have enjoyed working if my experience is indicative of what it's like to work there.