Intuit’s interview process for US new grads, as 2025 candidates describe it, is an online assessment with LeetCode-style problems plus Bash or SQL, a recruiter call, a LeetCode medium screen, and a 3-4 hour superday: live coding in a repository from user stories with unit and end-to-end tests, an architecture round, an AI round and a behavioral round on Intuit’s values. Senior and staff candidates get the build as a Craft Demo, scored on tests, error handling and how you explain the change.
A Mountain View Software Engineer 1 posting lists a Bay Area base of $55.50-$75.00 an hour (about $115,000-$156,000 a year). India hiring out of Bengaluru follows similar rounds with the online test usually on Glider; those reports are grouped near the end of the page.
Intuit interview process, round by round
| Round | Duration | What it tests |
|---|---|---|
| Online assessment | Not published | LeetCode-style problems plus Bash, SQL or web basics in 2025 US reports |
| Recruiter call | 30-40 min | Background, location, pay, logistics; some technical questions |
| Technical screen | 60-90 min | One LeetCode medium; AI questions in a June 2025 New York pre-screen |
| Build round (superday or Craft Demo) | About 90 min within a 3-4 hour block | Features from user stories in a repository, unit and end-to-end tests, error handling |
| Architecture or system design | 45-60 min | AWS, CI and architecture for new grads; scaling and operating costs for senior hires |
| AI round | Not published | How you use AI tools and why AI matters now |
| Behavioral | Not published | Intuit’s values and Design for Delight stories |
Intuit interview process reports from US new grads and interns, 2025
These come from short candidate posts on Taro, not full write-ups.
- US new grad, November 2025, no offer. About five stages: an online assessment with Bash and SQL questions as well as LeetCode-style problems, a recruiter call that included some technical questions, a technical screen, 3-4 build challenges and a technical interview.
- Mountain View intern, May 2025, no offer. An OA on data structures, algorithms and web development basics, a 1-hour object-oriented round on Karat (debugging a class and adding methods), then a short behavioral interview on Intuit’s values.
- Mountain View software engineer, September 2025, accepted offer. A LeetCode medium screen, then a 4-hour superday: live coding in a repository with user stories, end-to-end and unit tests; a technical round on AWS, Jenkins and architecture; an AI round; and a behavioral round.
- New York software engineer, June 2025, no offer. A 90-minute pre-screen with one coding problem and AI questions, then a 3-hour onsite with coding on a mock CRUD project, a design question on how to build Airbnb, and behavioral questions. The candidate passed and reached team matching but heard nothing after that.
- Mountain View senior software engineer, January 2025, accepted offer. A tech screen with a typical DSA question, then a full-day onsite that opened with solving a full project in 90 minutes, followed by discussion rounds with questions about scaling and operating costs.
- Mountain View staff software engineer, August 2025, no offer. A three-person craft panel built around debugging a repository shared in advance. The candidate’s advice: run the project locally first, check that the output is right (for example, whether the UI shows the correct key-value pairs), and practice breaking and fixing it.
What the US reports share: Intuit cares more about working, tested code in a realistic repository than about hard LeetCode, and AI questions now show up at every level.
Intuit interview questions that come up often
Coding / technical
- Matrix traversal - find a path or target in a grid of 0s and 1s
- O(1) insert, delete, and getRandom data-structure design
- Delete a node from a tree/graph and return the remaining forest as an array
- Decode string / unique email addresses style string-parsing problems
- OOPs: polymorphism, inheritance, with a real example from a project
- DBMS: ACID properties, indexing, normalization
- Operating systems: deadlocks, process vs thread
- Craft Demo: implement a user story in a shared repo, add tests, handle edge cases live
System design (SDE-2+)
- Design a photo/file storage service - upload, download, sharing at scale
- Design a notification or alerting service
- Design a roles-and-permissions system for a multi-tenant product
- Estimate load and storage for the system you just designed
Behavioral
- Tell me about a time you validated an idea with real users before building it (Design for Delight)
- Describe a time you considered multiple approaches before picking one
- Tell me about a time you did the right thing even when it was inconvenient
- Why Intuit, specifically, over other fintech/SaaS companies?
Intuit interview tips from candidate reports
- Treat the Craft Demo like a real code review, not a LeetCode round: read the existing style before you write a line, and narrate why you’re structuring the change the way you are.
- Have one Design for Delight story ready - a time you tested an idea cheaply with real users before committing to build it.
- OOPs and DBMS fundamentals still open a lot of Intuit panels. Do not skip the basics assuming they only ask hard DSA.
- For system design, a scoped, concrete answer (photo storage, notifications) beats an open-ended “design a big platform” pitch.
- If the repository arrives in advance, run it locally, check its output and try breaking it; the August 2025 staff candidate’s panel was built on debugging it.
- Prepare a short, honest answer on how you use AI coding tools; 2025 US superdays and pre-screens asked about AI directly.
Behavioral interview
In US superdays the behavioral interview is one round of the final block; the May 2025 intern loop ended with a short behavioral interview on Intuit’s values. It checks fit against the five operating values - Integrity without Compromise, Courage, Customer Obsession, Stronger Together, and We Care and Give Back. One Bengaluru SDE-2 candidate cleared the craft round and was still rejected after team-member rounds with behavioral questions, with no feedback given. The Intuit behavioral interview questions page has STAR answers mapped to those values.
Sample answers for high-frequency questions
Q. Design a data structure supporting insert, delete, and getRandom in O(1).
A. Combine a dynamic array with a hash map from value to that value’s index in the array. Insert appends to the array and records the index in the map. getRandom picks a uniformly random index into the array, which is O(1) precisely because the array is dense with no holes. The trick is delete: instead of removing from the middle and shifting, look up the index of the target, swap in the last element of the array, update that moved element’s index in the map, then pop the last slot and erase the target from the map. All three operations are O(1) average and the structure uses O(n) space. The follow-up variant that allows duplicates replaces the map value with a set of indices per value.
Q. Given a binary tree and a list of values to delete, return the remaining forest.
A. Do a post-order traversal so children are processed before their parent, carrying the deletion values in a hash set for O(1) membership checks. At each node, recurse left and right first, then check whether the node itself is to be deleted: if it is, add its surviving children to the result list as new roots and return null to its parent so the parent unlinks it; if it is not, return the node unchanged. After the traversal, add the original root to the result only if it was not itself deleted. This is O(n) time and O(h) space for the recursion stack. Post-order matters because you must know whether a child survived before you can decide whether it becomes a new root.
Q. Implement decode string - for example, 3[a2[c]] returns accaccacc.
A. Use two stacks, one for repeat counts and one for partial strings, walking the input once. On a digit, accumulate the full multi-digit number. On an opening bracket, push the current count and the current partial string, then reset both. On a closing bracket, pop the count and the previous string, and set the current string to the previous string plus the current string repeated count times. On a letter, append it to the current string. This runs in O(total output length) time and O(depth) stack space. The two details interviewers probe are multi-digit numbers such as 12[ab], and nested brackets, both of which the two-stack approach handles naturally.
Q. What is the difference between compile-time and runtime polymorphism?
A. Compile-time polymorphism, also called static binding, is method overloading and operator overloading: several methods share a name but differ in their parameter lists, and the compiler picks one from the declared argument types. Runtime polymorphism, or dynamic binding, is method overriding: a subclass redefines a parent method with the same signature, and the decision of which implementation runs is deferred to run time based on the object’s actual type, dispatched through a vtable in C++ or by the JVM in Java. The practical consequence Intuit interviewers look for is extensibility - runtime polymorphism lets you add a new subclass without touching the calling code, whereas overloading is only a convenience for the caller. Note that in Java, static, private, and final methods are bound at compile time and therefore cannot be overridden.
Q. Explain normalization, and when would you deliberately denormalize?
A. Normalization decomposes tables so each fact is stored exactly once: 1NF requires atomic columns, 2NF removes partial dependencies on part of a composite key, and 3NF removes transitive dependencies between non-key columns. The payoff is that an update touches one row, so update, insert, and delete anomalies disappear. You denormalize when read performance under a known access pattern matters more than write simplicity - for example, storing a precomputed comment_count on a post rather than running a COUNT join on every page load, or duplicating a product name into an order-line row so historical orders do not change when the catalogue does. The cost is that you now own the consistency: every write path must update both copies, usually via a transaction, a trigger, or an asynchronous job that you must then monitor for drift.
Intuit online assessment and interview tips
Online assessment
- A November 2025 US new grad OA included Bash and SQL questions, not only DSA
- On Glider in India, each question is timed and you usually cannot go back to an earlier one
Build-style rounds
- US final interviews included live coding in a repository with user stories, end-to-end and unit tests
- India SDE-2 Craft rounds asked candidates to add APIs, tests and pagination to a working project; one candidate was rejected over HTTP status codes and exception handling
Values round
- Interviewers use Design for Delight (Deep Customer Empathy, Go Broad to Go Narrow, Rapid Experimentation) as shared vocabulary
- 2025 US reports also included an AI round or AI questions
Intuit India: SDE-1 and SDE-2 interview experiences from Bengaluru
India loops usually start with a Glider online test in which each question is timed and you cannot go back, then one or two technical rounds on DSA, OOP, DBMS and OS. SDE-2 loops add the Craft Demo and a system design round.
Real interview experiences from India
Experience 1: SDE-2 (Nov 2024, selected)
Source: interviewexperiences.in, Intuit SDE-2 selected
Profile: SDE-2 candidate with an ML project background.
Online assessment
- MCQs on CS fundamentals and SQL, plus two LeetCode medium DSA problems.
Phone screens (60 min each)
- Screen 1: two DSA problems, plus Java threads, Runnable vs Callable and the Singleton pattern.
- Screen 2: two DSA problems, a design for an online bidding system focused on scale and performance, and Java, Spring Boot, MVC, bean creation and design patterns.
Craft Demo (90 min)
- Set up boilerplate locally (backend track) and build a REST API that returns a player list whose fields depend on an
isAdminparameter, with JUnit tests. The panel wanted to see it running.
Later rounds
- Technical (60 min): two DSA problems, pagination and sorting added to the Craft API with JPA
Specification, threading, design patterns, microservice resiliency patterns. - AI/ML (30 min): the candidate’s ML projects, when to use or avoid AI, and a producer-consumer problem with a blocking queue.
- Manager (30 min): standard managerial questions.
- DSA asked across the loop included max number with a given digit sum and count, largest-perimeter rectangle of ones, max sum of non-adjacent elements, longest consecutive subsequence and tree height.
Result: Selected; positive feedback two days later.
Experience 2: SDE-2, Bengaluru (Dec 2024, rejected)
Source: interviewexperiences.in, Intuit SDE-2 Bengaluru Dec 2024
Profile: 2.5 years of experience; recruiter outreach on LinkedIn; OA score of 94%.
Online assessment
- Two medium DSA problems (linked list, arrays) plus five core CS MCQs, with a two-day window.
Phone screens
- A multi-source BFS problem similar to rotting oranges, and one similar to largest rectangle in a histogram. Both coded and run.
Onsite
- Craft round (90 min): build a POST API to save player details, with follow-ups on payload design, error handling and logging, tested in Postman; then an API that forwards a prompt to a provided LLM endpoint and returns the response.
- DSA: next permutation, in place.
- After 30 minutes on engineering fundamentals, add pagination (page number, page size, total count) to the earlier GET API.
- Hiring manager (30 min): day-to-day work, teamwork, culture fit.
Result: Rejected two days later. The feedback named the HTTP error codes used and weak exception handling in the APIs.
Takeaway: In Craft rounds, API robustness is scored as hard as the algorithm. Practice status codes and exception handling before the onsite.
Experience 3: SDE-2 via referral (2025, offer declined)
Source: interviewexperiences.in, offer declined, SDE-2
Profile: About 2 years of experience, referred by a friend.
Eliminator round
- Count paths for a robot through a 0/1 grid moving only right or down; GenAI experience and tools; a model with 95% test accuracy but about 10% in production; write a prompt that returns only valid JSON; an edit-distance-style problem solved with recursion and DP.
Craft and Demo (90 min)
- Slide intro on projects and achievements, then about 15 minutes of design questions on high load and large data retrieval (the candidate brought up pagination) before adding an API, service layer and unit tests to a Java/H2 REST project, demonstrated in Postman.
Other rounds
- Problem solving (60 min): balanced brackets, scaling under heavy load (load balancers, rate limiters, exponential backoff, thundering herd), a Two Sum variant three ways.
- Team member and hiring manager rounds (30 min each).
Result: Offer, declined because the candidate had a better offer and wanted a remote role.
Takeaway: The requirements and scaling discussion before coding is part of the Craft score.
Experience 4: SDE-2, Bengaluru via referral (rejected)
Source: interviewexperiences.in, Intuit SDE-2 Bengaluru rejected
Profile: 3 years of experience; referral.
Phone screen (60 min)
- 25 minutes drawing the HLD of the current team’s work, 15 minutes designing APIs for a BookMyShow-like platform, 20 minutes on LRU Cache.
- Then a craft project with a two-week deadline.
Craft round (60 min, four-person panel)
- Presented assumptions, functional and non-functional requirements, stack, HLD and LLD, Postman collection and schema; questions on edge cases, PUT vs PATCH, path vs query parameters, database design and authorization.
Team member rounds (two, 30 min each)
- Current project, design patterns, caching; then why leave your current company and how you would debug a production issue.
Result: Rejected after the team member rounds; no feedback was given.
Sources
US reports: Taro: US new grad, November 2025, Taro: Mountain View intern, May 2025, Taro: Mountain View, September 2025, Taro: New York, June 2025, Taro: Mountain View senior, January 2025, Taro: Mountain View staff, August 2025, and a Mountain View Software Engineer 1 posting.
India reports:
- InterviewExperiences.in - Intuit SDE-2 Bengaluru Dec 2024 (API feedback)
- InterviewExperiences.in - Intuit SDE-2 selected (Craft Demo + pagination)
- InterviewExperiences.in - Offer declined SDE-2 craft loop
- InterviewExperiences.in - SDE-2 Bengaluru referral / craft project
- LinkedIn - Intuit Glider OA question mix (2025)