Intuit Software Engineer interview typically runs 4-6 rounds: recruiter screen, online assessment, technical coding, take-home or build challenge, system design, and final hiring manager interview. The process usually takes a few weeks and is notably segmented, with AI and project discussion often included.
$152K
Avg. Base Comp
$202K
Avg. Total Comp
5-6
Typical Rounds
3-6 weeks
Process Length
We’ve seen a clear pattern across Intuit candidate experiences: the company is not just checking whether you can code, but whether you can explain, defend, and extend what you build. Multiple candidates reported being asked to walk through take-home work, repo-based exercises, or prior projects in detail, and the follow-up questions often centered on trade-offs, maintainability, and how the solution would scale. Even when the coding prompt itself was fairly standard, interviewers kept pushing toward the reasoning behind the implementation rather than stopping at correctness.
A recurring theme is Intuit’s comfort with mixing classic engineering with newer AI/product thinking. Candidates repeatedly mentioned questions on LLMs, RAG, prompt improvement, AI-native applications, and even architecture for model integration. That shows up alongside practical backend topics like Spring, APIs, caching, and REST service design, which tells us they want engineers who can operate in real product codebases, not just solve isolated algorithm problems. The non-obvious signal here is that communication quality is part of the technical bar: several candidates said they were evaluated on how clearly they narrated decisions, clarified requirements, and discussed their own work.
We also noticed that the process can feel segmented and sometimes inconsistent in expectations, especially when a round labeled one way turns into a discussion of projects or architecture instead of live coding. The candidates who seemed closest to the bar were the ones who treated every technical conversation as a chance to surface assumptions, explain design choices, and connect their work to product impact. At Intuit, that blend of practical engineering and thoughtful product judgment appears to matter as much as raw problem-solving speed.
Synthetized from 8 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.
The part that surprised me most was how much of the process was built around take-home style work rather than just live coding. After a recruiter reached out on LinkedIn, I first did a 1-hour LeetCode-like algorithm round, which was pretty standard, and then I was asked to prepare a project presentation about myself and my work. That led into a longer technical challenge and a discussion with the hiring manager, so the process felt very segmented and a bit compartmentalized. The coding itself was fair but definitely not trivial, and the architecture discussion made it clear they wanted to see how I think beyond just solving problems quickly.
The broader process was also slower than I expected. There was a recruiter screen, then a 90-minute code challenge, followed by a 30-minute recruiter call where we walked through a project I had used AI on, and then a build challenge that took a few hours. After that came a 30-minute tech screen and an hour-long final interview. In another part of the process, I also saw that the assessment could include a mix of MCQs, one LeetCode-style question, SQL, and even a Bash scripting task, which was the trickiest part because the solution was mostly hidden in the prompt and you had to read carefully. Overall, it felt like they cared about both practical coding and how you present your work, but the turnaround was slow and I didn’t get an offer. If you’re preparing, I’d make sure you’re comfortable with a timed algorithm round, a take-home or build challenge, and explaining a project clearly in front of interviewers.
Prep tip from this candidate
Be ready for a Bash scripting question embedded in a longer assessment, and read the prompt carefully because most of the solution may already be there. Also prepare a concise project presentation, since that came up alongside the technical rounds.
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 | |
|---|---|
| Hurdles In Data Projects | |
| Term Frequency | |
| Dijkstra implementation | |
| Digitizing Student Test Scores | |
| Subscription Retention | |
| Offer Matching API Design | |
| Check Matching Parentheses | |
| Ticket Reservation Locking | |
| Scalable Data Pipelines | |
| Youtube Recommendations | |
| Client Solution Pushback | |
| Above Average Product Prices | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Bagging vs Boosting | |
| Customer Orders | |
| String Shift | |
| Comments Histogram | |
| Random SQL Sample | |
| Prime to N | |
| Retailer Data Warehouse |
Synthesized from candidate reports. Individual experiences may vary.
An initial recruiter or staffing-agency call reviews background, resume, role fit, and expectations. Candidates may also discuss past projects, AI use in development, and what they expect from a team or manager.
A proctored assessment can include DSA, SQL, Bash/Git, and MCQ-style questions. The difficulty ranges from medium to harder-than-medium, and careful reading matters, especially for scripting or command-line portions.
The live coding interview focuses on algorithms and practical problem solving. Candidates reported DFS, graph problems, balanced parentheses, and Java coding, with interviewers asking for edge cases, complexity, and tradeoffs.
Some loops include a repo-based build task or small service implementation, often in a Spring or REST context. The follow-up discussion evaluates code quality, maintainability, architecture choices, and how the candidate approached implementation.
A longer panel-style round asks candidates to present or defend their solution and can include live coding, API design, caching, system design, and AI/LLM topics such as RAG, agents, prompt improvement, or LLM feature architecture.
The final stage combines hiring-manager discussion and broader fit evaluation. Expect questions about project ownership, product thinking, communication, and how you explain architectural decisions from prior work.