Intuit Data Scientist interviews typically run a recruiter screen, a SQL/Python technical screen, a hiring-manager conversation, and a final loop or craft presentation mixing business cases, A/B testing, and ML questions; one senior candidate also reported a week-long take-home.
$148K
Avg. Base Comp
$250K
Avg. Total Comp
4-6 rounds
Typical Rounds
Not reported
Process Length
Candidates describe an Intuit Data Scientist process that usually opens with a recruiter screen and a technical screen covering SQL and Python basics, sometimes paired with a written test or a Karat-administered coding round. From there, several reports describe a hiring-manager conversation focused on background and role fit, followed by a final stage that blends business-case reasoning with technical depth. One Senior Data Scientist candidate received a take-home with five parts: building a prediction algorithm, designing an A/B test, exploratory analysis on a dataset of around 250k rows, proposing solutions from experiment output, and a 15-20 slide presentation. That candidate was told two days of work wasn't sufficient, so plan for about a week. Other candidates describe a craft demo or craft presentation to a panel, including one report of a one-hour presentation, followed by individual interviews leaning toward ML theory and product sense. Expect to reason through A/B testing end-to-end, including primary, secondary, and guardrail metrics and sequential versus parallel experiment scaling. Also be ready to explain ML concepts such as linear regression or why you'd choose F1-score. The hiring-manager screen is not always light: one candidate found it heavy on causal inference and experimentation, while another described a single smooth conversation about past experiments and applying AI at work. Because round counts and depth differ by level and team, treat the structure below as the common pattern rather than a fixed script.
Synthesized from 14 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.
The interview process at Intuit was well-structured and thoughtful from start to finish—honestly one of the better experiences I've had interviewing. It kicked off with an online assessment, followed by several rounds coordinated through UptimeCrew. These included focused sessions on AI use cases and project evaluation, a longer technical round where I presented a previous project (roughly 60 minutes), walking through the technical work, the decisions I'd made along the way, and the real problems it solved, and then a brief but meaningful conversation with the hiring manager to discuss the team and the actual responsibilities.
What really made it stand out was the quality of the conversations. The interviewers weren't just working through a checklist or asking trivia. They genuinely wanted to understand my background and explore how my experience in machine learning and decision science could apply to their work. One interview specifically asked about technical versus non-technical tradeoffs and how I evaluate those kinds of decisions—not a gotcha question, but a real exploration of how I think through complex choices. We had a genuine discussion about the team's priorities, what the role would actually entail, and what success would look like.
I received an offer. The process was rigorous, sure, but in a way that felt fair and designed to evaluate genuine fit rather than just testing coding speed or domain trivia. It left me excited about the possibility of working there.
Prep tip from this candidate
Prepare to present and defend a past project in depth (60-90 minutes)—have clear explanations for your technical decisions, the problems it solved, and how it tied to business metrics or impact. Expect deep questions on technical versus non-technical tradeoffs and how you evaluate those decisions, plus questions on AI applications of your work.
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.
Most candidates report an initial recruiter call covering background, why they're looking, and basic role fit before any technical stage.
Candidates typically face a technical screen combining SQL queries, Python coding (string manipulation, basic data structures), and sometimes a stats or conditional probability question. Reported formats include CoderPad, a Karat round, and a notebook-style exercise on a provided CSV file. Difficulty ranges from an easy LeetCode-style string problem to building KPIs from a sample dataset in SQL.
A hiring-manager round typically explores your background and role fit, but it can also become a serious technical conversation. One report described heavy causal-inference and A/B testing questions here, while another described a smooth conversation about past experiments and how the candidate applied AI at work.
One Senior Data Scientist candidate received a five-part take-home covering a prediction algorithm, A/B test design, exploratory analysis on a roughly 250k-row dataset, proposed solutions, and a 15-20 slide presentation. That candidate was told two days of work was not enough. Other candidates instead describe a craft demo or presentation delivered to a panel as part of the final stage.
The final stage typically includes multiple interviews: a presentation of a past project or take-home, business-oriented case questions, and technical discussion covering ML concepts and A/B testing design, including guardrail metrics. One candidate reported interviewers drilling into gaps in real time during a roughly 20-minute A/B test scenario on a QuickBooks product.
