Draftkings Data Analyst interview typically runs 3 rounds: HR screen, phone interview, case study. It usually takes about 2-4 weeks and becomes more selective at the case stage.
$97K
Avg. Base Comp
$110K
Avg. Total Comp
4
Typical Rounds
2-4 weeks
Process Length
Our candidates report that DraftKings is less interested in polished textbook answers than in whether you can frame an ambiguous business problem cleanly and keep your reasoning organized under pressure. The most telling signal from the experience we saw was the shift from a fairly routine early conversation into a case-heavy discussion with an analytics manager, where the interviewer seemed to care more about how the candidate approached the problem than about any single right answer.
A recurring theme is the use of estimation and probability prompts that feel grounded in the product’s real-world decision making. One candidate described a train-style time-sink question and another about estimating ticket odds for a bowling game, which suggests they want analysts who can reason through messy, incomplete inputs without freezing up. We’ve seen that the bar here is not just analytical accuracy; it’s clear structure, defensible assumptions, and the ability to explain tradeoffs out loud. Candidates who struggle tend to be the ones who treat the case like a puzzle to solve silently rather than a business conversation.
What stands out most is that DraftKings appears to value practical judgment over abstract technical depth for this role. The process felt manageable until the case, then noticeably more selective, which is a strong hint that the team is screening for people who can translate numbers into decisions in a fast-moving gaming environment. If you can stay calm, make your assumptions explicit, and walk the interviewer through your logic without overcomplicating it, you’re already aligned with what they seem to reward.
Synthesized from 1 candidate report by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Draftkings process.
I started with an HR screen that came inbound from the recruiter, and that part was pretty straightforward. After that, the process moved into a phone interview that leaned technical, but not in a super hard way. The main thing I remember is that they asked EV-style questions and then shifted into a case study format. The case itself was on Zoom with a manager from analytics, and that was where the interview got more interesting. It felt less like a pure coding screen and more like they wanted to see how I thought through a business problem and whether I could structure an answer clearly under pressure.
The case questions were the part that stood out most. One prompt was framed like a train question from other interviews, where you have to find the time sink, and another question was about probability, like estimating the chances of getting tickets for a bowling game on the ground or online. That gave me the sense they were testing both analytical reasoning and comfort with ambiguous, estimation-style problems. I didn’t make it past the first case, even though there was apparently another round after that, which I never reached. Overall the process felt manageable up front and then more selective once the case study started. If I had to do it again, I’d spend more time practicing how to talk through estimation and case prompts out loud, because that was clearly the filter.
Prep tip from this candidate
Practice estimation and probability-style case prompts, especially “find the time sink” train-type questions and business scenarios where you have to reason through assumptions out loud. Be ready to explain your approach clearly in a Zoom case with an analytics manager, since that seemed to be the main cutoff.
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 Draftkings
How much do you expect to pay and how much money should you set aside for the game
| Question | |
|---|---|
| Rider Discount | |
| Why Do You Want to Work With Us | |
| 2nd Highest Salary | |
| Compute Deviation | |
| Button AB Test | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Group Success | |
| Significance Time Series | |
| Hurdles In Data Projects | |
| Subscription Retention | |
| Centralized Event Ingestion | |
| Comparing Search Engines | |
| Time on FB Distribution | |
| Marketing Channel Metrics | |
| WAU vs Open Rates | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Spam Classifier | |
| Customer Success vs. Free Trial | |
| Distribution of 2X - Y | |
| Compute Variance | |
| Track Your Most Valuable Gamers | |
| Matrix Rotation | |
| KNN From Scratch | |
| Interquartile Distance | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Concurrent LLM Serving | |
| User Event Data Pipeline |
Synthesized from candidate reports. Individual experiences may vary.
An inbound recruiter or HR screen to cover basic background, role fit, and logistics. This part was described as straightforward and not especially technical.
A phone interview that leaned technical but was not overly difficult. The interviewer asked EV-style questions and then moved into a case-study format to assess analytical reasoning.
A Zoom case interview with a manager from analytics focused on business problem solving and structured thinking under pressure. Questions included estimation and ambiguity-heavy prompts, such as identifying a time sink in a train-style question and a probability estimate about getting tickets for a bowling game.
The candidate noted there was apparently another round after the first case, but they did not reach it. No details were provided about the format or content of this stage.
