Intuit Software Engineer candidates describe assessments that blend DSA, SQL, and Bash, followed in some paths by build reviews, design discussions, AI-use questions, and manager conversations.
$159K
Avg. Base Comp
$209K
Avg. Total Comp
3-5 rounds
Typical Rounds
3-6 weeks
Process Length
Intuit Software Engineer interviews reported here do not follow one uniform loop, but a recurring preparation theme is practical engineering judgment alongside coding. Candidates describe online assessments that can mix a coding problem with SQL, Bash, or multiple-choice questions. Reported coding topics include graphs, balanced parentheses, word-frequency counting, and a queue-scheduling problem. Because formats vary, practice moving between implementation, database queries, scripting, and concise technical explanations.
Later stages may shift toward a take-home assignment, a repository shared before the interview, or live work on an existing project. Candidates report building or extending REST services, implementing user stories, correcting code during a review, and discussing architecture even when the session is primarily presented as coding. Treat any project discussion as an engineering conversation, not merely a demo: explain your choices, clarify requirements, narrate tradeoffs, and state what you would improve.
AI questions appear repeatedly, but in different forms. Reported topics include RAG, agents, LLM integration, prompt improvement, AI-native applications, and recommendation-system design. Prepare truthful examples that show what you built, which model or storage choices were involved, and how the AI component fit the product. Other reports emphasize Java, Spring, APIs, caching, HTTP responses, OOP, exceptions, and asynchronous calls. Recruiter, hiring-manager, and project conversations may also cover your background, teamwork, values, and working style. Use these as preparation areas rather than expecting every topic or stage in one process.
Synthesized from 26 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 most unusual part of my Intuit process was the build challenge: after the initial online assessment, I had seven days to complete it and was explicitly allowed to use Copilot or other coding agents. It was challenging and took me roughly eight to ten hours, but the time window made it manageable. I applied directly through the website and waited about a month before receiving the assessment, which had to be completed within a couple of weeks. That first round covered SQL, Bash, a medium-level DSA problem, and basic coding concepts.
After the take-home, I had a recruiter screening that focused less on a standard resume walkthrough and more on how I used AI in the project, including how I prompted it and evaluated its help. I was also asked about the project I was most proud of, so I made sure I could explain my individual contribution clearly. The technical discussion was moderate but occasionally tricky; the emphasis was more on computer science fundamentals than on a long sequence of algorithm questions. I prepared for topics such as deadlocks, process scheduling, object-oriented programming, basic SQL queries, stack storage, and the difference between a HashMap and a TreeMap. There was still some coding, including an array-based task involving saving the result in a string.
Overall, the interviewers were approachable and the experience felt fair. I received an offer. My biggest takeaway is to treat the build challenge as both an implementation exercise and an AI-collaboration discussion: be ready to explain exactly how you used coding agents, not just show the finished project.
Prep tip from this candidate
Practice explaining your use of Copilot or coding agents in a seven-day build challenge, including how you prompted and validated the output. Review OS and database fundamentals—especially deadlocks, scheduling, basic SQL, stack storage, and HashMap versus TreeMap—alongside a medium DSA problem.
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 | |
| Term Frequency | |
| Hurdles In Data Projects | |
| Dijkstra implementation | |
| Spam Classifier | |
| 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 | |
| Marketing Workflow Optimization | |
| Decreasing Payments | |
| Your Strengths and Weaknesses | |
| Call Center Resource Management | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Closest SAT Scores | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Top 3 Users | |
| Top 5 Turnover Risk |
Synthesized from candidate reports. Individual experiences may vary.
Candidates frequently report an asynchronous assessment with a coding problem plus SQL and Bash, Git, Linux, or regex work. Reported difficulty varies from easy-to-medium coding to a hard calculator-style problem; practice solving and explaining each component under a shared time limit.
Candidates report screens that may cover past projects, working style, a live DSA problem, or how they use AI in development. Some reports include graph or DFS questions, while others focus on explaining a technical background and project choices.
Several candidates describe a take-home, advance repository, or GitHub-based exercise followed by a review. Be prepared to walk through code quality, tradeoffs, debugging, scalability, and how any AI assistance was prompted and validated.
Later technical conversations may include API or Spring implementation, caching, system design, or an open-ended recommendation or AI-integration scenario. Candidates report both live coding and discussion-heavy formats, so clarify the task while communicating assumptions.
Candidates report conversations about prior work, teamwork, values, and influencing decisions. Use concrete examples that identify your contribution and connect technical choices to the product or team outcome.
