Discord Software Engineer Interview Questions
& Process

Didn't get far, but it was a good experience. I did the recruiter screen and then a technical screen with two engineers. The technical interview had this chat problem that others mentioned. My solution worked, but wasn't what they wanted and didn't show my best work, so I was relieved it passed. After not moving on, I asked the recruiter for feedback and got useful, practical tips for next time. Even though I didn't get the offer, I appreciated how open and helpful they were.

This was a coding problem interview, and honestly, it was the worst interview experience I've had this cycle. I actually knew the problem beforehand, but the actual interview itself was awful. There were two interviewers, and one was just shadowing. For half the interview, it was silent, and for the other half, the interviewer was basically yelling at me, saying things like '45 minutes left! Go faster! Fast fast!' and '2 minutes left!!! Finish the feature!'. I managed to finish the two parts of the problem, but the quality suffered at the end. They left only 2 minutes for questions. What a joke. I can't imagine working here.

I got an email from a Discord recruiter about my application. The recruiter call was to chat about my background and career history and for them to tell me more about the job. It felt like a formality to confirm I was real and honest on my application. Next, I had a skills assessment interview. Two engineers sent me a link with the task and offered some guidance. It was a multi-part assessment to get a Web Socket chat program running for multiple simultaneous users. I didn't do well because the documentation was confusing and lacked detail, like not mentioning multiple connections to a Web Socket, which is crucial for the software's purpose. I didn't pass the first stage and was told I wouldn't move forward. While I get Discord needs to vet engineers, using vague, lacking software for assessments isn't ideal. People apply based on the job description. Unless the role specifically involves maintaining a TCP Web Socket service, it shouldn't be used for vetting. An engineer could excel at TCP Web Socket services but be bad at the actual job, or vice versa. Using assessments unrelated to the actual position doesn't help anyone. It's like asking a biologist to take a geologist exam or a pastry chef to do a butcher's test.