Intuit Data Scientist candidates report recruiter and hiring-manager conversations, SQL/Python screening, and role-dependent loops that emphasize experimentation, product metrics, practical data analysis, presentations, and discussion of prior work.
$176K
Avg. Base Comp
$310K
Avg. Total Comp
4 rounds
Typical Rounds
3-5 weeks
Process Length
Intuit Data Scientist interviews vary by team and level, but the candidate reports consistently combine technical analysis with product-facing judgment. Candidates describe recruiter and hiring-manager conversations followed by screens that may cover SQL, Python, coding, or causal inference. One marketing candidate discussed how and why to build a marketing-mix model, while another was asked about running an experiment with unusual user assignments.
For product analytics and experimentation roles, metric definition and experimental reasoning are central themes. A Senior Data Scientist candidate completed a roughly week-long case using customer and feature-usage data. The work included interpreting unlabeled features from usage patterns and defining a North Star metric and guardrails for acquisition and retention. The subsequent loop covered the case presentation, a business question, past-project discussion, experimentation, and an exercise using LTV/CAC to assess a marketing channel.
Another candidate described a substantial take-home spanning prediction, exploratory analysis, experiment design, recommendations, and a presentation. Reports also include technical screening through CoderPad, a craft presentation, and detailed questions about previous projects. Prepare to explain not only what you built but why you selected particular metrics, methods, and tradeoffs. Because the reported sequences differ, do not assume every role uses the same stages. Prioritize SQL and Python fluency, end-to-end experimentation, product metrics, and a clear presentation of your analytical decisions.
Synthesized from 9 candidate 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 Intuit process.
1 round. Nothing surprised me, and it was a smooth interview experience. The hiring manager mainly wanted to get to know me, so the HM dived deep into the experiences I listed on my resume, and some scenario based questions such as talk me about an experiment you recently conducted
Questions asked: talk me about an experiment you recently conducted; how did you apply AI at work? What would you normally do when the experiment results are mixed
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 Intuit
Minimum Change
| Question | |
|---|---|
| Size of Joins | |
| Subscription Retention | |
| Marketing Channel Metrics | |
| Term Frequency | |
| Hurdles In Data Projects | |
| Dijkstra implementation | |
| Spam Classifier | |
| Running Dog | |
| Digitizing Student Test Scores | |
| Non-Normal AB Testing | |
| Offer Matching API Design | |
| Overfit Avoidance | |
| Approval Drop | |
| Above Average Product Prices | |
| Check Matching Parentheses | |
| Scalable Data Pipelines | |
| Youtube Recommendations | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Marketing Workflow Optimization | |
| Decreasing Payments | |
| Your Strengths and Weaknesses | |
| Call Center Resource Management | |
| Analyzing Multiple Data Sources | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Top Three Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter screens and, in several processes, a hiring-manager conversation about role fit, background, and prior experience. Some hiring managers also asked scenario questions about recent experiments, mixed results, or applying AI at work.
Technical screens may include SQL and Python, coding, probability, or causal-inference discussion. One candidate spent an entire planned SQL/Python and causal-inference screen on coding, while another described SQL KPI construction and practical Python tasks.
Candidates report team-specific practical work rather than one universal assignment. One product-analytics candidate had about a week for a customer and feature-usage case that required feature inference, a North Star metric, and guardrails; others described notebook or presentation exercises.
Later stages may require presenting a take-home or craft exercise to a panel. Candidates also report detailed discussion of a favorite or proud past project, so be prepared to explain the problem, analytical choices, tradeoffs, and impact.
Candidates report questions on A/B testing, causal inference, metric definition, business cases, and marketing-channel performance. Product-facing examples included retention changes, nonstandard experiment assignment, and using LTV/CAC to assess a channel.
