Intuit Data Analyst interview typically runs 2 rounds: technical SQL/case study and behavioral. It usually takes about 2 rounds and feels practical, with a strong focus on communication and business context.
$135K
Avg. Base Comp
$223K
Avg. Total Comp
2
Typical Rounds
1-2 weeks
Process Length
We've seen Intuit lean hard into practical analytics rather than puzzle-style screening. In the candidate experience we have, the technical discussion centered on medium-difficulty SQL with joins and window functions, plus a case study that felt close to day-to-day work. That lines up with the broader pattern we hear from candidates at product-driven companies: they want to know whether you can reason through real subscription and retention problems, not whether you can memorize edge-case syntax. The Tableau presentation piece also stands out because it turns the interview into a working session on your judgment, not just your query-writing speed.
A recurring theme is that Intuit is evaluating how well you translate analysis into action. Our candidate reported behavioral questions about influencing both technical and non-technical stakeholders and prioritizing work, which suggests the team is listening for clear business communication as much as analytical rigor. The non-obvious make-or-break factor here is whether your examples sound useful to a product and finance organization: can you explain what the analysis changed, who used it, and why it mattered? Candidates who treat the conversation like a pure SQL test tend to undersell themselves; the stronger ones show they can connect data to customer outcomes and team decisions.
Synthetized from 1 candidates 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.
I enjoyed the interview process because it felt pretty aligned with the actual work. For the role I went through two rounds, and the first one was the one that mattered most technically. It was a mix of SQL and case study work, and the SQL was around medium difficulty rather than anything overly algorithmic. I remember getting questions that touched joins and window functions, so it was less about tricking me and more about seeing whether I could work through real analytical problems. There was also a Tableau presentation component where I had to walk through a project I had done before, which made the round feel more practical and role-specific than a standard coding screen.
The second round was behavioral and focused on how I work with others. I was asked about a time I communicated with both technical and non-technical stakeholders to get my ideas adopted, and also how I prioritize projects. That part felt straightforward, but they were clearly listening for whether I could explain my thinking clearly and not just do the analysis. Overall, the interview team was kind and the process felt fair. I ended up getting the offer, and my main takeaway was that Intuit seems to care a lot about communication and business context, not just SQL ability. If you’re preparing, I’d spend time on medium-level SQL, especially joins and window functions, and be ready to present one of your past Tableau projects in a clear, concise way.
Prep tip from this candidate
Brush up on medium SQL with joins and window functions, and practice presenting a Tableau project from start to finish. Also prepare a concrete example of influencing both technical and non-technical stakeholders, since that came up directly in behavioral.
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 | |
|---|---|
| Digitizing Student Test Scores | |
| Overfit Avoidance | |
| Approval Drop | |
| Above Average Product Prices | |
| Event Pickup Optimization | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Experiment Validity | |
| First to Six | |
| Last Transaction | |
| Compute Deviation | |
| Download Facts | |
| Button AB Test | |
| Bank Fraud Model | |
| Top 3 Users | |
| 500 Cards | |
| Random SQL Sample | |
| Bagging vs Boosting | |
| Subscription Overlap |
Synthesized from candidate reports. Individual experiences may vary.
The first round was the main technical screen and focused on medium-difficulty SQL. Candidates were asked to solve practical analytical problems involving joins and window functions rather than algorithmic puzzles.
This stage also included a case study component and a presentation of a past Tableau project. The interviewer expected the candidate to walk through the work clearly and explain the analysis in a business-relevant way.
The second round was behavioral and centered on collaboration, communication, and prioritization. Candidates were asked for examples of influencing both technical and non-technical stakeholders and how they decide what to prioritize.