Good product, growing pains
Good product, growing pains
- Enthusiastic user base.
- Lots of interesting technical challenges.
- Interesting tech to work with (Elixir, Rust, etc.).
- Lots of product churn.
- Toxic positivity.
- Middle management has high variability in quality.
- Workloads are not fair. Some teams are overstaffed, some understaffed. On-call and interview duties are not fairly distributed.
Additional Ratings
Was this helpful?
Discord Interview Questions
Discord Interview Experiences
Staff Software Engineer
Technical Screen Conversation with Hiring Manager Onsite: * 2 technical interviews (both coding, with one including system design questions) * 1 values interview * 1 get-to-know-you interview with the team at Discord
Staff Software Engineer
In short, I had a bad experience here. The technical screen portion was poorly run due to a lack of communication and clarification of expectations. The screening call with the recruiter was pleasant and straightforward. Next, the call with the hiri
Staff Software Engineer
Applied online -> recruiter screen -> technical screen. Finished a two-part coding exercise. I thought it went extremely well, although it wasn't perfect. I had two "why is this not working" moments that I quickly corrected without any hints. After
Staff Software Engineer
San Francisco, California, United StatesMay 1, 2021Technical Screen Conversation with Hiring Manager Onsite: * 2 technical interviews (both coding, with one including system design questions) * 1 values interview * 1 get-to-know-you interview with the team at Discord
Staff Software Engineer
United StatesApril 1, 2025In short, I had a bad experience here. The technical screen portion was poorly run due to a lack of communication and clarification of expectations. The screening call with the recruiter was pleasant and straightforward. Next, the call with the hiri
Staff Software Engineer
United StatesMarch 21, 2025Applied online -> recruiter screen -> technical screen. Finished a two-part coding exercise. I thought it went extremely well, although it wasn't perfect. I had two "why is this not working" moments that I quickly corrected without any hints. After
