Intuit Software Engineer Interview Guide

Several candidates report an early call with recruiters or with Uptime Crew, an Intuit staffing partner, rather than an Intuit employee directly. The conversation is typically non-technical, covering resume background, tech stack, and expectations for a team and manager. A handful of candidates were also asked how they use AI tools in their day-to-day development, so it's worth having a concrete example ready even at this early stage.

Most reports describe a single proctored assessment combining a LeetCode-style algorithm problem, a SQL query, and a Bash or Git task, occasionally with added multiple-choice questions. Reported difficulty ranges from medium to hard, and one candidate specifically named Basic Calculator III as the coding problem, while SQL questions often involve joins, min/max logic, or ranking salaries by group. The test is commonly timed around 90 minutes, though a couple of candidates instead worked through a HackerRank-style format with a similar three-part structure.

This stage varies widely in scope. One candidate describes a two-to-four-hour repo-based assignment that involved designing systems such as a gradebook or a bank-transaction system, while another was given seven days and explicitly told that Copilot or other coding agents were allowed. A separate report described a four-hour 'Superday' that included a live-coding round built around an existing repository and user stories. Whichever format you get, expect a follow-up conversation where you defend your design choices, discuss tradeoffs and scaling, and explain any AI assistance you used rather than just showing that the code runs.

Rounds at this stage differ by candidate. One report described designing a sliding-window running-median system and then implementing a thread-safe LRU cache with O(1) operations; another involved implementing an API against a provided Spring project, including a task where a TinyLlama model generated a nickname from a player table. A separate candidate instead faced a three-person 'craft' panel focused on debugging and extending a repository they'd been given ahead of time. AI and LLM topics surface often here too, including RAG basics and, in one case, designing a recommendation system with LLM integration.

The closing stage is usually a conversation about past projects, teamwork, and fit with the hiring manager. One candidate was asked to describe how they embody each of Intuit's five core values with concrete examples. Communication after this point isn't guaranteed to be smooth: one candidate who cleared a Staff-level interview loop had a hiring-manager conversation as part of team matching, then found the recruiter stopped responding with no final decision ever given.