Intuit Data Scientist Interview Guide

We’ve seen Intuit evaluate for more than polished answers; they want candidates who can hold a product and an experiment in their head at the same time. A recurring theme in candidate reports is the intensity of the probing once you get past the screens: interviewers quickly moved from a take-home into old projects, recommendation systems, ML choices like XGBoost, and then a full QuickBooks A/B test scenario. The signal is clear: they care about how you reason through tradeoffs, metrics, and failure modes, not just whether you can name the right method.

Another pattern we’ve noticed is how much weight they place on specificity. One candidate said the team expected a week-long take-home and still pressed on the depth of the analysis, which included prediction, experiment design, EDA on a 250k-row dataset, recommendations, and a slide deck. That tells us Intuit is looking for people who can turn analysis into a decision-ready narrative. When candidates got vague, the follow-up questions got sharper, especially around primary vs. guardrail metrics, hypothesis framing, and what could go wrong.

The non-obvious part here is that the bar seems tied to calibration as much as capability. Multiple candidates reported that interview performance influenced compensation placement, and that the questioning was intentionally exhaustive. In practice, that means the strongest candidates are the ones who can stay crisp under pressure and defend every assumption without drifting into generic explanations. At Intuit, the difference between “good” and “hire” often comes down to whether your thinking feels operational enough to ship inside a product team.