Intuit Data Analyst interviews typically pair a recruiter screen with a medium-difficulty, case-based SQL round and a Tableau or A4A-style case study presentation, followed by behavioral rounds on stakeholder communication; candidates report 2-5 rounds, and end-to-end timelines are rarely stated.
$120K
Avg. Base Comp
$223K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Data Analyst interviews at Intuit typically open with a recruiter or HR screen covering background and interest in the role, then move into a SQL round built around medium-difficulty joins and window functions rather than heavy algorithmic puzzles. Several candidates describe the SQL as case-based. One report says the hiring managers shared their screen and went straight into questions with no way to run code, so practicing queries verbally or on paper can help.
A presentation stage shows up across multiple reports, though the exact format varies. Some candidates built and presented a Tableau dashboard from a provided client dataset or a past project. Another prepared a deck for an "A4A" craft demo before three deeper rounds. One candidate was also asked how they'd assess a rule's performance and write SQL-based controls around it, so be ready to talk through data governance and risk, not just query syntax.
Behavioral rounds focus on how you've influenced both technical and non-technical stakeholders and how you prioritize competing work. Reported round counts range from two in one offer-track process up to about five when a case-study presentation is followed by several deeper interviews. Communication after interviews was uneven in some accounts. One candidate heard nothing for more than two weeks after the final stage despite following up twice, and another never heard back after a first-round SQL screen. Ask for a clear follow-up timeline early in the process.
Synthesized from 11 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.
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.
| Question | |
|---|---|
| Size of Joins | |
| Minimum Change | |
| Above Average Product Prices | |
| Youtube Recommendations | |
| Decreasing Payments | |
| Marketing Channel Metrics | |
| Dijkstra implementation | |
| Hurdles In Data Projects | |
| Spam Classifier | |
| Digitizing Student Test Scores | |
| Non-Normal AB Testing | |
| Client Solution Pushback | |
| Check Matching Parentheses | |
| Ticket Reservation Locking | |
| Overfit Avoidance | |
| Approval Drop | |
| Event Pickup Optimization | |
| Scalable Data Pipelines | |
| Marketing Workflow Optimization | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Call Center Resource Management | |
| Analyzing Multiple Data Sources | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Last Transaction | |
| First to Six |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR phone screen covering resume background, motivation for joining Intuit, and general fit questions. One candidate applying to a contract role received only vague guidance beforehand from a third-party recruiter, so expectations going in can vary.
Multiple candidates describe a SQL-focused round centered on joins, window functions, and filtering logic at a medium difficulty level rather than pure algorithmic puzzles. In one report the round ran over screen share with no way to run code, and that candidate recommends practicing writing and explaining queries without executing them. One report also included a question about writing SQL-based controls and assessing rule performance.
Several candidates prepared a presentation. Some built a Tableau dashboard from a provided dataset or presented a past project; another prepared a case-study deck for an A4A craft demo. In that account, the presentation was a meaningful part of the evaluation alongside the technical and behavioral conversations.
Behavioral rounds typically ask candidates to describe how they influenced both technical and non-technical stakeholders and how they prioritize competing projects. Some candidates had additional deeper rounds that explored their case-study reasoning, such as risk management in data decisions, extending the total round count on that track.
One candidate who received an offer described the cycle as taking a few weeks. Others reported gaps in communication: one heard nothing for more than two weeks after the final stage despite following up twice, and another never heard back after a first-round screen. Ask for a follow-up timeline early.
