
Intuit Data Analyst candidates report SQL and case-based assessment, behavioral discussion, and—in one process—a presentation or craft-demo stage that tests how clearly they communicate analysis.
$105K
Avg. Base Comp
$135K
Avg. Total Comp
2-5 rounds
Typical Rounds
1-2 weeks
Process Length
Intuit Data Analyst interviews in the available reports center on applied analysis and how candidates explain it. One candidate who accepted an offer described a two-round process: an initial mix of medium-difficulty SQL and case work, plus a walkthrough of a prior Tableau project, followed by behavioral questions about influencing technical and non-technical stakeholders and prioritizing work. Their SQL examples included joins and window functions.
Two other candidates reported a different shape. One contract-role first round moved quickly from introductions into easy-to-medium, case-based SQL questions shared on screen, with no opportunity to run code. Another described a technical conversation combining SQL, behavioral discussion, resume questions, and a case-study-style component, then an A4A craft-demo deck and presentation followed by three deeper conversations. Prepare to articulate your SQL approach as you work, not only arrive at a query.
Bring a concise Tableau or other analytics-project story that covers the question, analysis, result, and audience. Pair it with examples of using analysis to gain adoption across different stakeholders and of choosing among competing priorities. The reports are limited, so the exact sequence and number of conversations may vary by team and role type.
Synthesized from 3 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.
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.
Featured question at Intuit
Minimum Change
| Question | |
|---|---|
| Size of Joins | |
| Subscription Retention | |
| Marketing Channel Metrics | |
| Hurdles In Data Projects | |
| Dijkstra implementation | |
| Spam Classifier | |
| Digitizing Student Test Scores | |
| Non-Normal AB Testing | |
| Check Matching Parentheses | |
| Ticket Reservation Locking | |
| Overfit Avoidance | |
| Approval Drop | |
| Above Average Product Prices | |
| Event Pickup Optimization | |
| Scalable Data Pipelines | |
| Marketing Workflow Optimization | |
| Youtube Recommendations | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Decreasing Payments | |
| Your Strengths and Weaknesses | |
| Call Center Resource Management | |
| Analyzing Multiple Data Sources | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Customer Orders | |
| Experiment Validity |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report SQL embedded in practical or case-based prompts. One first-round account says interviewers shared a screen and went directly into easy-to-medium SQL without a live execution environment; another offer recipient described medium SQL alongside case work, including joins and window functions.
One candidate presented a prior Tableau project during the technical stage. A separate candidate reported preparing an A4A craft-demo deck and presenting it before three deeper conversations. Prepare a compact narrative that makes the analytical decision-making and communication clear.
The accepted-offer candidate reported behavioral questions on communicating with technical and non-technical stakeholders to gain adoption and on prioritizing projects. Another candidate also described behavioral and resume discussion alongside SQL, so examples should connect work style to analysis.