Discord Data Scientist interview typically runs 4 rounds: recruiter screen, hiring manager screen, technical screen, and onsite panel. It usually takes about three weeks and is structured and professional.
$175K
Avg. Base Comp
$192K
Avg. Total Comp
4
Typical Rounds
3 weeks
Process Length
We’ve seen Discord care less about flashy technical depth for its own sake and more about whether a candidate can reason like a product scientist. In the candidate experience we reviewed, the hiring manager spent real time on past projects and alignment with Discord’s style and values, which is a strong signal that they’re looking for people who can connect analysis to how the product actually works. The technical screen was described as light on SQL and more focused on thought process, and that pattern carried through the rest of the process: the standout questions were about analytic methodology, hypothesis formation, and experimentation basics rather than obscure edge cases.
A recurring theme is the project retrospective. Multiple parts of the process pushed the candidate to explain a large project end to end, including what decisions were made and how the work turned out. That tells us Discord wants candidates who can defend tradeoffs, not just present polished results. We also noticed that the hard-skills case study was called out as the toughest part, alongside an ML system design and a coding challenge in the final panel. The non-obvious make-or-break here is being able to move fluidly between product analytics, experimentation, and technical execution without sounding compartmentalized. Candidates who can clearly connect a scenario, a hypothesis, and a measurement plan seem to fit what Discord is optimizing for.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Discord process.
The hardest part for me was the onsite, especially the DS hard-skills case study. The process was pretty standard overall and took about three weeks. It started with a recruiter screen, then a hiring manager screen where they cared a lot about past projects and whether I seemed aligned with Discord’s style and values. After that I had a 45-minute technical screen that was fairly light on SQL and included a case study, so it felt more like they wanted to see how I thought than whether I could grind through tricky syntax.
The final round was a full panel with four interviews. One was behavioral, one was SQL, and the other two were more DS-focused case studies, split between soft skills and hard skills. The most memorable question was a product analytics case study where I had to walk through a specific scenario and explain my analytic methodology, how I’d form hypotheses, and the basics of experimentation. I also got asked to talk through a large project and how it went, which tied back to the project-retrospective style of the onsite. There was also an ML system design and a coding challenge in the onsite flow, so it wasn’t just pure analytics. Overall the interviews felt structured and professional, and I was treated well throughout, but the process did take longer than I expected. I didn’t get the offer in the end, so I’d say the main takeaway is to be ready to clearly explain your project decisions, your experimentation thinking, and how you approach product analytics end to end.
Prep tip from this candidate
Be ready to walk through a real product analytics case study end to end, including hypothesis generation and experimentation basics. Also prepare a concise retrospective on a large past project, since that came up alongside the behavioral and DS case discussions.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Discord
Write a query to display the top three users by downloads each day
| Question | |
|---|---|
| Type-ahead Search | |
| Stories Feature Change | |
| Alternative Vendor Tradeoff | |
| Your Strengths and Weaknesses | |
| Dog Rescue Robot | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Button AB Test | |
| Subscription Overlap | |
| Top Three Salaries | |
| Experiment Validity | |
| Comments Histogram | |
| Compute Deviation | |
| Liked Pages | |
| First to Six | |
| 500 Cards | |
| Last Transaction | |
| Search Ratings | |
| User Experience Percentage | |
| WAU vs Open Rates | |
| Network Experiment Design | |
| Session Difference | |
| Raining in Seattle | |
| Notification Deliveries | |
| Random SQL Sample | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
An initial conversation with recruiting to cover your background, interest in Discord, and overall fit for the Data Scientist role. This stage appears to be a standard first pass before moving into more substantive interviews.
A conversation focused heavily on past projects, your working style, and whether you align with Discord’s culture, values, and product approach. The interviewer seems to care about how you think about your prior work and whether you’d fit the team.
A fairly light technical interview with some SQL and a case study component. The emphasis is more on how you reason through problems and structure your thinking than on difficult syntax or deep algorithmic grinding.
A full panel consisting of four interviews covering behavioral, SQL, and multiple data science case studies. The onsite included both soft-skills and hard-skills DS cases, plus an ML system design discussion and a coding challenge, with a strong focus on product analytics, experimentation, and project retrospectives.