Interview experience
Intuit Interview Questions
Overview
Section titled “Overview”Intuit’s engineering interviews pair standard DSA rounds with a live Craft Demo on real code, evaluated through its Design for Delight framework.
Intuit interview process at a glance
Section titled “Intuit interview process at a glance”| Round | Duration | What it tests |
|---|---|---|
| Recruiter screen | 30-40 min | Background, motivation, location/comp, logistics |
| Online Assessment | 60-90 min | 2-4 DSA problems on the Glider platform |
| Technical interview(s) | 30-60 min each | Coding, OOPs/DBMS/OS fundamentals, project deep-dive |
| Craft Demo (SDE-2+ / senior) | ~90 min | Live coding on a shared codebase - tests, error handling, communication |
| System design (SDE-2+) | 45-60 min | Scalable design and trade-offs (storage, notifications, etc.) |
| Hiring manager / HR | 20-30 min | Values fit, Design for Delight thinking, closing logistics |
Recruiter screen
Section titled “Recruiter screen”A 30-40 minute call to confirm background, work authorization, location, and current comp/notice period. It’s a logistics filter more than a technical bar - be direct about timeline and expectations.
Common questions
- Walk me through your resume/current role
- Why are you interested in Intuit right now?
- What are your compensation and location preferences?
- What’s your notice period / earliest start date?
Full behavioral frameworks are on the Intuit HR interview questions page.
Online Assessment
Section titled “Online Assessment”A 60-90 minute timed test, usually on the Glider platform: typically 2-4 coding problems spanning easy to hard difficulty. Candidates report that clean, fully-passing solutions on the easier problems weigh more than a partial attempt at the hardest one.
Common questions
- Matrix traversal: find a path/target in a grid of 0s and 1s
- Data structure design: O(1) insert, delete, and getRandom
- Tree/graph problems: e.g. delete a node and return the remaining forest as an array
- String/array problems in the “decode string” or “unique email addresses” family
See how real candidates handled this stage on the Intuit interview experience page.
Technical interviews
Section titled “Technical interviews”One or two rounds of 30-60 minutes each, usually with one or two interviewers. Expect a mix of live coding, core CS fundamentals, and a genuine deep-dive into a project from your resume - not just a listed-skills recap.
Common questions
- OOPs: polymorphism (compile-time vs runtime), inheritance, and where you’ve used them
- DBMS: ACID properties, indexing, normalization
- Operating systems: deadlocks, process vs thread
- Resume project deep-dive: architecture choices, the hardest bug, what you’d rebuild
Round-by-round breakdowns are on the Intuit interview experience page.
Craft Demo: Intuit’s distinctive round
Section titled “Craft Demo: Intuit’s distinctive round”This is the round most candidate reports single out as unusual to Intuit. Roughly 24-48 hours before the interview, you’re emailed access to a small GitHub repository with a partially-built application. In the ~90-minute session itself, 2-4 interviewers watch you implement one or two new user stories live inside that existing codebase - not a fresh whiteboard problem. The bar isn’t just “does it run”: interviewers are explicitly watching for test coverage, error handling, and whether you narrate your reasoning as you extend someone else’s code, since that’s closer to day-one engineering work than a LeetCode round.
Common questions
- Implement a new feature/user story inside the provided repo, matching existing code style
- Add unit tests and handle edge cases for the feature you just wrote
- Explain why you structured the change the way you did, and what you’d refactor with more time
- Follow-up questions tied to Design for Delight: how would you validate this feature actually solves the user’s problem?
Design for Delight and Intuit’s operating values
Section titled “Design for Delight and Intuit’s operating values”Intuit’s own innovation methodology - Design for Delight (D4D) - shows up as an evaluation lens in the Craft Demo and behavioral rounds, not just as company trivia. Its three principles are Deep Customer Empathy (understand the real problem before proposing a fix), Go Broad to Go Narrow (consider more than one option before committing), and Rapid Experimentation (test cheaply before building the whole thing). Layered on top are Intuit’s five operating values: Integrity without Compromise, Courage, Customer Obsession, Stronger Together, and We Care and Give Back. Interviewers use both as a shared vocabulary, so naming which principle or value a story maps to - briefly, not as a buzzword drop - tends to land better than a generic answer.
Common questions
- Tell me about a time you validated an idea with real users before building it (Deep Customer Empathy / Rapid Experimentation)
- Describe a time you considered multiple approaches before picking one (Go Broad to Go Narrow)
- Tell me about a time you did the right thing even when it was inconvenient (Integrity without Compromise)
- Why Intuit, specifically, over other fintech/SaaS companies?
System design (SDE-2 and above)
Section titled “System design (SDE-2 and above)”A 45-60 minute round for more senior candidates, focused on a concrete, scoped system rather than an open-ended “design Google” prompt. Interviewers probe estimation, trade-offs, and failure modes as much as the final diagram.
Common questions
- 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
- How would you estimate load and storage for the system you just designed?
Hiring manager / HR round
Section titled “Hiring manager / HR round”The closing conversation checks fit against Intuit’s values and logistics: location, compensation band, and a couple of behavioral stories. Prepare those answers on the dedicated page rather than cramming them into this hub.
Common questions
- Tell me about a time you advocated for the customer even when it meant pushing back internally
- Describe a decision you made by relying on data rather than intuition - what was the outcome?
- Are you willing to relocate / what’s your notice period?
- Do you have any questions for us?
Sample answer frameworks for each of these are on the Intuit HR interview questions page.
Frequently asked questions about Intuit interviews
Section titled “Frequently asked questions about Intuit interviews”What is the Intuit interview process for engineers?
Intuit’s engineering loop typically runs: 1. Recruiter screen (30-40 min) - background, motivation, logistics. 2. Online Assessment (60-90 min on the Glider platform) - 2-4 DSA problems. 3. One or two Technical interviews (30-60 min each) - coding, OOPs/CS fundamentals, and a project deep-dive. 4. Craft Demo (around 90 min, common on SDE-2+ and senior loops) - live coding on a codebase shared 24-48 hours in advance. 5. System design (SDE-2+) and a closing Hiring Manager/HR conversation (20-30 min). Community-reported timelines put the full process at roughly 3-6 weeks.
What is Intuit’s Craft Demo round?
The Craft Demo is Intuit’s most distinctive round, reported mainly on SDE-2 and senior loops. Candidates get access to a small GitHub repository 24-48 hours ahead of time and are asked to implement 1-2 new user stories live in front of 2-4 interviewers, roughly 90 minutes total. It’s scored on working code, but also on test coverage, error handling, and how clearly you explain trade-offs while you build - closer to a real code review than a whiteboard problem.
What is Design for Delight (D4D) and why does it come up in interviews?
Design for Delight is Intuit’s internal innovation framework, built on three principles: Deep Customer Empathy, Go Broad to Go Narrow, and Rapid Experimentation. Interviewers - especially in the Craft Demo and behavioral rounds - often use it as a lens: they want to hear how you understood a user’s real problem, considered more than one option, and tested an idea cheaply before committing, not just that you shipped something.
What questions are asked in Intuit interviews?
Coding rounds lean on arrays/strings, matrix traversal, tree/graph problems (e.g. delete a node and return the remaining forest), and data-structure design questions (O(1) insert/delete/getRandom). CS fundamentals cover OOPs, DBMS (ACID, indexing), and operating systems basics. System design rounds (mostly SDE-2+) ask for things like a photo-storage or notification service. Behavioral and Craft Demo rounds probe Intuit’s five operating values and its Design for Delight framework.
How many rounds are there in the Intuit interview?
Most community-reported loops describe 4-6 stages: recruiter screen, Online Assessment, one or two technical interviews, an optional Craft Demo (common at SDE-2+), and a closing hiring-manager/HR round. Exact composition varies by level and team, so treat this as a range, not a fixed script.
Does Intuit hire at TCS/Infosys-style campus scale?
No. Intuit’s Bengaluru office does hire new graduates, but candidate reports describe a smaller, more selective funnel - a targeted early-career program plus off-campus and referral hiring - not a multi-thousand-seat placement drive. Verify any specific college-drive or headcount claim with your placement cell or Intuit’s own careers page.
How should I prepare for Intuit interviews?
Drill medium DSA (arrays, trees, graphs, and O(1) data-structure design), revise OOPs/DBMS/OS fundamentals, and practice reading and extending someone else’s codebase quickly and cleanly - that’s exactly what the Craft Demo tests. For behavioral rounds, prepare STAR stories mapped to Intuit’s operating values (Customer Obsession, Courage, Integrity without Compromise) and be ready to describe a time you validated an idea with real users before building it (Design for Delight).