
One candidate for a FanDuel Business Analyst role describes a fast recruiter Zoom screen of behavioral questions on resume, customer-facing change, salary and notice period, followed by a rejection email. See how to prepare.
$95K
Avg. Base Comp
$110K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
The FanDuel Business Analyst experience reported here is a recruiter screen, and it was almost entirely behavioral. The candidate was asked to walk through their resume and to describe times they handled customer-facing change. They were also asked about salary expectations and whether they could give their current employer two or three weeks' notice. The call ended with a chance to ask questions.
This candidate did not report SQL, case or technical questions at this stage, and the interviewer moved quickly. If you reach a similar screen, it makes sense to prepare two or three concise STAR-style stories about change you drove or supported with customers or stakeholders. State the situation, your actions and the measurable result. Have a clear salary range and notice-period answer ready, because those came up directly.
Scheduling was the messier part. The original recruiter was replaced just before a holiday weekend, the format changed from a phone screen to Zoom, and the call was pushed back by an hour shortly before it started. If you hit similar friction, respond quickly, confirm the time in writing and ask what the next steps and timeline are. This candidate was told to expect news midweek, and a system-generated rejection arrived the following Friday. The experience is a single data point from one candidate and may not reflect later rounds or other teams.
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 Fanduel process.
I want to be upfront that this one ended with a quick rejection, but the process itself was messy enough that it's worth knowing about. A recruiter reached out about a phone screen for a Business Analyst role at FanDuel about a week before Labor Day weekend. Right before the holiday started, a different recruiter contacted me saying the original recruiter was no longer able to run the interview, and she would take over. The catch was that she was going to be out the entire following week, so I had only a few hours to get the interview rescheduled. I managed to squeeze it in, and it was switched from a phone screen to a Zoom interview. About half an hour before the call, she asked to push it back by an hour, which was the first sign that scheduling on her side was going to be rough. When we finally met, she moved through a series of behavioral questions at a fast clip. The questions were things like walking through my resume, describing times I handled customer-facing change, my salary expectations, whether I could give my current employer two or three weeks' notice, and whether I had questions for her. It felt less like a conversation and more like a box being checked, as if the decision had already been made. She said I would hear back in the middle of the following week. Instead, the rejection came the next Friday, and it was a system-generated email rather than anything from her. My advice is to prepare strong, specific STAR-style stories about change you drove with customers, have your salary and notice-period answers ready, and don't read too much into a rushed interview, though if the recruiter is this disorganized, it may be worth asking early about the timeline.
Prep tip from this candidate
Have concrete stories ready about handling customer-facing change, since the interviewer moved straight through behavioral prompts on that theme. Also be prepared to answer salary requirements and notice period questions directly and early.
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 Fanduel
How would you improve Google Maps?
| Question | |
|---|---|
| Safe Deployments | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Button AB Test | |
| P-value to a Layman | |
| WAU vs Open Rates | |
| Groups of Anagrams | |
| Compute Deviation | |
| Scalped Ticket | |
| Youtube Recommendations | |
| Random Forest from Scratch | |
| Friend Requests Down | |
| Comparing Search Engines | |
| Docs Metrics | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Subscription Retention | |
| Hurdles In Data Projects | |
| Group Success | |
| Justify a Neural Network | |
| Loan Model | |
| Confidence Interval Explanation | |
| Ranking Metrics | |
| Analyzing Churn Behavior | |
| Rider Discount | |
| Statistically Significant Test | |
| Evaluating Revenue Decline | |
| Processing Large CSV | |
| Marketing Channel Metrics | |
| Significance Time Series |
Synthesized from candidate reports. Individual experiences may vary.
The candidate reports being contacted about a phone screen for a Business Analyst role roughly a week before a holiday weekend. A different recruiter then took over the interview and the time had to be rearranged quickly. Expect that scheduling may move, so confirm details in writing.
The screen was switched from phone to Zoom and the recruiter moved quickly through behavioral prompts. The candidate reports being asked to walk through their resume, describe times they handled customer-facing change, share salary expectations, say whether they could give two or three weeks' notice, and ask any questions.
The candidate was told they would hear back in the middle of the following week. They report receiving a system-generated rejection email the next Friday instead, with no further rounds described. No other stages are reported, so later steps, if any, are unknown.