Intuit Software Engineer Interview Guide

The Intuit Software Engineer interview, as candidates describe it, is less about a single algorithm round and more about a chain of practical tasks. Candidates report an early online assessment. One called its proctored coding problem medium-hard, and another describes a coding problem plus SQL, a harder-than-expected Bash task and a short multiple-choice section. A different candidate says the process began through a staffing agency, Uptime Crew, before a HackerRank assessment.

The build challenge is the stage that shaped one candidate's process most. They describe a 2 to 4 hour build task on concurrency and file parsing that drove two later rounds, including a walkthrough of the submission. Another candidate had three days to build a basic REST service, where code maturity mattered more than features, followed by a call reviewing the solution. Others describe live work on a supplied repository: implementing user stories in one case, and a 90-minute craft round coding in front of five people in another.

AI shows up in several forms. Candidates report recruiter questions about how they use AI in development, and technical discussion of RAG, LLMs, agents or prompt design. Others describe fundamentals such as Java and Spring, a word-count file exercise, or graph-focused DSA. Accounts differ, so prepare broadly rather than for one fixed loop.

Outcomes in the reports are mostly rejections. One candidate was told afterward they had not asked enough clarifying questions or discussed architecture, so narrate your reasoning and design choices even when interviewers say little. Some candidates also mention slow or missing communication, so keep your own record of what you submitted and when.