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.
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
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| Dog Rescue Robot | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Employee Salaries | |
| Top Three Salaries | |
| Button AB Test | |
| Subscription Overlap | |
| Merge Sorted Lists | |
| Comments Histogram | |
| Experiment Validity | |
| Liked Pages | |
| Last Transaction | |
| First to Six | |
| Session Difference | |
| Compute Deviation | |
| Search Ratings | |
| User Experience Percentage | |
| Network Experiment Design | |
| P-value to a Layman | |
| 500 Cards | |
| Raining in Seattle | |
| Random SQL Sample | |
| WAU vs Open Rates | |
| Job Recommendation | |
| Like Tracker | |
| Month Over Month | |
| Flight Records | |
| Bank Fraud Model |
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.