Recruiter Call
This call involved usual behavioral questions, with the exception of a "tell me about a time when you were building something and had to make tradeoffs" question that caught me off guard. Apparently, my answer to this was satisfactory, as I progressed to the next stage. It's worth preparing for unexpected questions like this, even if you're not applying for a senior role. The recruiter was also about six minutes late.
Coding Test
The test featured a chat server question. I was able to solve the first part and progressed through the next section as well. I communicated my thought process to the interviewer throughout, outlining my approach and testing functionality. Afterward, we had a discussion about Discord and the work environment there. Unfortunately, this interview ultimately led to a rejection email received within three days. Given that I solved the question, including the "extra" part, I'm unsure what else was expected.
Additional Observation
It's worth noting that while the interviewers' emails appeared exceptionally supportive, my own emails sent with questions prior to the interviews, as they themselves seemed to encourage, went unanswered. This aspect felt disingenuous.
Tell me about a time when you needed to make tradeoffs.
The following metrics were computed from 6 interview experiences for the Discord Software Engineer role in San Francisco, California.
Discord's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Discord's Software Engineer interview process in San Francisco, California.