How Intuit Interviews in 2026: Process, Questions & What They Score
The complete process, reported questions, and what interviewers score.
Intuit / Interview snapshot
12
stages from
application to offer
49
reported questions
20
public sources
Independent: SupaCV is not affiliated with or endorsed by Intuit. This is one well-documented shape of Intuit's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.
On this page
01 / For every Intuit candidate
The process, start to finish.
This playbook covers software engineering hiring, the track Intuit (TurboTax, QuickBooks, Credit Karma, Mailchimp) is best known for and the one nearly all interview guides cover. Intuit's official hiring-process page describes an interview day made up of a set-up block (15 minutes, or 90 minutes for engineers), a 60 minute Craft Demonstration before four hiring team members, a 45 minute Assessors interview, a 30 minute Team Member interview that often includes questions about Intuit values, and a 30-60 minute Manager interview.
Intuit says feedback comes within 24 hours of the interview. The page lists no stage before that day. Third-party guides and candidate reports describe a recruiter screen, often a timed online coding assessment (Glider or HackerEarth) and a live technical screen; one guide describes a hands-on build challenge instead.
Recent guides also describe a system design round and a newer AI or GenAI round in the onsite loop, but other guides list no separate AI round and place AI questions inside the recruiter call, technical screen or craft round. The Craft Demonstration is the stage guides focus on most.
Most accounts say candidates get a repository in advance (from 24 hours to 5 days, depending on the source), implement user stories, then demo and explain their code, tests and design choices before a panel. Intuit's own page instead says engineers solve a technical question during the 90 minute set-up block, and one Blind poster at level 2 was handed the prompt on the day.
A Blind commenter says Staff-level candidates may get a business problem to answer with a high-level design. Intuit publishes five operating values, and its hiring page says the Team Member interview often includes questions about values. Intuit does not publish a scoring rubric, so the values are listed as the framework only in that sense. Third-party guides disagree on durations, lead times and total process length, and these are flagged below.
Stage 1: Recruiter screen
25-40 min
Covers background, motivation and fit. Sources state 25-35 min, 30-40 min and 30 min. One Intuit-hosted candidate account (a principal engineer in India) describes a technical recruiter who checked the candidate's skills against the role. Intuit's own hiring page does not mention this step.
Third-party and candidate sources only; not on the official page
Stage 2: Online coding assessment
about 90 min
Timed coding test. Two entry-level candidate reports each describe 4 problems in about 90 minutes, one on Glider and one on HackerEarth. Codemia also says Glider, 90 min, but with 2-3 easy-to-medium problems. Design Gurus and the Interview Guys describe a timed or HackerRank/LeetCode-style test with no duration, and one guide describes a test covering algorithms, SQL and Bash. Not every route includes it: Techprep and Ophy AI describe a Glider technical screen instead of a separate assessment.
Not universal; third-party and candidate sources only
Stage 3: Technical phone or video screen
30-90 min
Live coding in data structures and algorithms, sometimes with resume and CS-fundamentals questions. Guides state 60 min, 60-75 min and 60-90 min, and two guides name Glider as the platform. Entry-level candidates report two rounds, of 30 and 60 minutes. One Intuit-hosted account describes a phone screen with an Intuit assessor but gives no duration.
Third-party and candidate sources only; not on the official page
Stage 4: Craft demo preparation
varies
Varies by source, level and interviewer. Intuit's own page says engineers spend the 90-minute set-up block downloading tools and solving a technical question on their own. Guides report a GitHub repo with user stories sent 24-48 hours ahead, or 3-5 days ahead (Codemia, Interview Kickstart), with an existing Spring Boot app in Codemia's version. Ophy AI adds that some loops ask for a past project or take-home presentation instead. One Blind poster at level 2 got the prompt on the day. At Staff level, a commenter reports a business problem answered with a high-level design. Any stack is generally accepted unless one is specified.
Lead time conflicts across sources
Stage 5: Interview set-up
15 min (90 min for engineers)
Intuit's own page says engineers usually spend this block downloading coding tools and solving a technical question on their own, which they then present at the craft demo.
Stage 6: Craft Demonstration
60-90 min
Intuit's page says 60 min with 4 hiring team members. It opens with a short personal introduction with pictures and achievements, including things not on the resume, followed by a case study. Third-party guides say about 90 min with 2-4 interviewers, implementing or demoing user stories, and grading clean code, unit tests, error handling and design trade-offs. An Intuit-hosted candidate account describes a five-person panel that cross-questioned the solution.
Duration and panel size conflict: the official page says 60 min and 4 people, most third-party guides say about 90 min and 2-4 people, one account says 5 people
Stage 7: Assessors interview
45 min
Two interviewers whose work closely aligns to the role ask about skills and experience, plus follow-up questions on the case study.
Stage 8: System design round
about 60 min
Recent third-party guides list this as a separate onsite round, often set in financial domains such as tax, payments or bookkeeping. Design Gurus mentions system design in the onsite loop without a duration. Intuit's own hiring page does not list it. Its position in the loop differs by guide: Techprep puts it after the AI round, Codemia before it.
Third-party only; not on the official page
Stage 9: AI or GenAI round
30-60 min
Techprep lists a 30-45 min AI assessment round and Codemia a 45 min AI/GenAI round. An Intuit-hosted candidate account describes a 60 min product engineering and AI proficiency session, half on design and tooling and half on AI solutions the candidate had developed. Ophy AI, Prachub and Design Gurus list no separate AI round and place AI questions inside the recruiter call, technical screen, craft round or onsite loop.
Newer stage; sources disagree on whether it is a separate round
Stage 10: Team Member interview
30 min
One assessor, a cross-functional colleague or people manager whose work is closely connected to the role. Intuit's page says this interview often includes questions about Intuit values and the team environments where you do your best work.
Stage 11: Manager interview
30-60 min
A manager who supports similar roles asks what motivates you, about your experience, and about your key successes and learnings. Intuit's page recommends using this interview to ask about the team and career development.
Stage 12: Decision and offer
feedback within 24 hours; whole process about 2-6 weeks by source
Intuit's page says feedback comes within 24 hours of the interview, and to email its Talent Acquisition team if you hear nothing within a week. Whole-process estimates conflict: 2-4 weeks (Techprep, Ophy AI), 3-5 weeks (Codemia), 4-6 weeks (Design Gurus, Prachub), and a 24-day average from application to offer that the Interview Guys attribute to Glassdoor data. Guides describe the virtual onsite as 4-6 interviews over about 4-6 hours. Intuit's page does not say how long the whole process takes.
Total process length conflicts across sources
02 / What Intuit scores
Intuit Operating Values
01
Integrity Without Compromise
02
Courage
03
Customer Obsession
04
Stronger Together
05
We Care And Give Back
The five values are published on Intuit's operating values page, each with three behavior statements (for example, under Courage: \"We value speed, a bias for learning and action\"). Intuit's hiring-process page says the Team Member interview often includes questions about Intuit values and tells candidates to review them. Intuit does not publish a scoring rubric or say how the values are weighted.
Some third-party guides list fewer than five (Codemia names four and leaves out We Care And Give Back) or add items that are not on the official values page, such as craft and responsible-AI judgment (Design Gurus). Those extras are left out of the framework here.
03 / Coach's notes
Coach's tips.
01
Treat the Craft Demonstration like a real work ticket. Run the repo, read the existing tests to learn its conventions, write unit tests as you go, and finish one user story fully before starting the next. Design Gurus says clean code and unit testing are explicitly graded and that a working story beats two half-stories, and a level 2 Blind poster says Intuit looks for unit testing.
02
Show less and be ready to defend all of it. One Blind commenter warns that the panel will question whatever you put on screen. Another advises stating your requirements and assumptions before you explain your solution. Only claim knowledge you can back up.
03
Prepare the craft demo opening as well as the code. Intuit's page says the session starts with a short personal introduction, with pictures, followed by personal and professional achievements.
04
Map your stories to the five published operating values (Integrity Without Compromise, Courage, Customer Obsession, Stronger Together, We Care And Give Back). The official page says the Team Member interview often includes questions about values, and customer-impact-over-elegance questions appear in more than one guide.
05
Expect AI to come up, though where it appears varies. Some guides list a dedicated round, an Intuit-hosted candidate account describes a 60 minute AI proficiency session, and other guides fold AI questions into the technical screen, craft round or onsite loop. Be ready to explain how you validate AI output in a financial product, and where you would not use it.
06
Practice system design set in Intuit's own domains: seasonal tax-filing spikes, small-business payments and reconciliation, bookkeeping and email campaigns.
07
A Blind commenter says Intuit uses Java Spring Boot and React internally, so those are a reasonable choice if the stack is open. Ask your recruiter which craft demo version you will get (repo in advance, work during the set-up block, or a past-project presentation), and use the recruiter prep call if one is offered; the Interview Guys cite Glassdoor reviewers describing one about a week before the craft round.
08
Prepare questions for the Manager interview. Intuit's page recommends asking about the team and career development.
04 / The research
Where this page comes from.
Compiled from public sources across 12 sites. Intuit's own page is among them: intuit.com/careers/hiring-process.
- sites
- 12
- coaching and prep guides
- 12
- Intuit's own pages
- 4
- candidate reports and forums
- 4
Source composition
Where the research comes from
Grouped by the kind of site that published each source: Intuit's own domain, candidate forums, and everything else.
- Coaching and prep guides12
- Intuit's own pages4
- Candidate reports and forums4
05 / The questions
Reported questions, by category.
Showing questions for
Roles are grouped by the category each question fits, not by the source.
Craft Demo and Coding
15 questions
Implement the provided user stories live in an existing codebase (a GitHub repo shared in advance), with clean code and unit tests.
Tests extending an existing codebase with unit-tested features that match its conventions, then explaining the design.
Build a working application for an open-ended problem and present your solution.
Tests building a small working app under time pressure and explaining design, error handling and testing choices.
Extend your craft demo solution to support an additional requirement.
Tests how cleanly your design absorbs a new requirement and whether tests still pass after the change.
Get data from an API and display it (front-end craft demo prompt).
Tests basic front-end API integration: fetching data over HTTP and rendering it, ideally with unit tests.
Find the maximum sum of a contiguous subarray in an array of integers (Maximum Subarray).
Tests Kadane's algorithm or dynamic programming for a linear-time maximum subarray sum.
Valid Parentheses: check that the brackets in a string are properly matched.
Tests stack-based matching of nested brackets in a single pass.
Number of Connected Components in an Undirected Graph.
Tests graph traversal with DFS, BFS or union-find to count connected components.
Edit Distance.
Tests 2D dynamic programming over string prefixes with insert, delete and replace transitions.
Design and implement a Least Recently Used (LRU) cache with O(1) get and put.
Tests combining a hash map with a doubly linked list for O(1) lookup and eviction.
Merge Intervals: merge all overlapping intervals.
Tests sorting by start time, then one linear merge pass with edge case handling.
Design a data structure that supports insert, delete and get-random-element in O(1) time.
Tests pairing a hash map with a dynamic array and swapping with the last element on delete.
Reverse Nodes in K Group, then optimize your solution.
Tests linked list pointer reversal in groups of k, with recursive and stack-based approaches.
Count occurrences of a string in a file, handling case sensitivity, then explain how to optimize it (for example with Rabin-Karp or KMP).
Tests substring search with case handling, then optimizing with a Rabin-Karp rolling hash or KMP.
What key things would you look for when reviewing a code?
Tests code review judgment: correctness, readability, test coverage, error handling and maintainability.
What are the differences between faking, mocking, and stubbing?
Tests knowledge of test doubles: fakes run lightweight logic, mocks verify interactions, stubs return canned data.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
System and Low-Level Design
12 questions
Design a system that processes millions of tax returns during peak season, with complex rules that change every year.
Tests scaling for seasonal traffic spikes, versioned rules engines, calculation accuracy and audit trails.
Design a payment system for small businesses that handles invoicing, payment collection and reconciliation, with idempotency and failed-payment retries.
Tests idempotent payment APIs, retry logic for failed payments, reconciliation and PCI compliance.
Design a payment gateway (a Stripe-style service).
Tests payment flow design: idempotency keys, ledger consistency, retries and webhook handling.
Design a digital wallet (a Venmo or Cash App style service).
Tests ledger design, balance consistency under concurrent transfers and double-spend prevention.
Design a real-time bookkeeping system like QuickBooks that handles invoicing, expense tracking and financial reporting, with concurrent edits.
Tests concurrent edit handling and data accuracy, for example with versioning, for real-time financial summaries.
Design an email campaign delivery system like Mailchimp that sends billions of marketing emails, with scheduling, bounce handling and rate limiting across ISPs.
Tests queue-based fan-out, per-ISP rate limiting, bounce handling and deliverability at huge send volumes.
Design a notification system (for example, notifications for TurboTax).
Tests multi-channel fan-out, queues, retries, deduplication and user preference handling.
Design a nested comment service.
Tests tree-shaped data modeling for threaded replies, pagination and efficient subtree retrieval.
Design an API rate limiter.
Tests rate limiting algorithms such as token bucket or sliding window and per-client state handling.
Design an in-memory file system.
Tests tree-based directory modeling with path parsing and operations like create, list and read.
Design a fraud detection system for financial transactions.
Tests real-time scoring of transactions with rules and models, false positive trade-offs and latency limits.
Design a system that ingests bank transactions and reconciles them against a ledger.
Tests ingestion pipelines, idempotent matching, ledger reconciliation and handling late or duplicate transactions.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Every role
AI Readiness
5 questions
Design an AI assistant for small business owners' bookkeeping questions, covering RAG architecture, financial data guardrails and accuracy.
Tests RAG architecture, financial data guardrails, accuracy evaluation and user trust handling.
How do you validate AI outputs before customers see them?
Tests validation of LLM output before release: evals, guardrails, human review and monitoring.
How do you validate code an AI assistant generated for you?
Tests reviewing AI-generated code with tests, diff review, edge cases and security checks.
Where would you refuse to use AI in a financial product?
How do you use AI tools in your day-to-day work, and where do you see AI changing your role?
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Every role
Behavioral and Values
13 questions
Describe a situation where you had to prioritize customer impact over technical elegance.
Tell me about a time you had a conflict with a product manager over a technical trade-off.
Tell me about a time you championed a customer need that others overlooked.
Tell me about a time direct customer feedback changed what you built.
Describe a time you went above and beyond to solve a customer's problem.
Tell me about a time you delivered a customer-focused solution.
Tell me about a time you fell in love with a customer's problem.
Tell me about a time you were pressured to ship something you were not confident in.
Tell me about a time doing the right thing was expensive.
Describe a time you spoke up when it was uncomfortable.
Describe a time you pushed back on a timeline to protect quality.
Tell me about a time you worked across teams to ship something.
Tell me about past cross-team work with project management, design or AI teams.
Every role
Motivation and Fit
4 questions
Share a short intro about you (with pictures), then tell us about your personal and professional achievements, including things not on your resume.
What kind of team environment do you do your best work in?
What motivates you, and what are your key successes and learnings?
Why Intuit? How does the mission of powering prosperity align with your goals?
Your next step
Interviewing at Intuit?
Make sure your resume gets you to the first round.
Practicing for Intuit against your resume is in Interview Prep on Career.
Common questions
Quick answers.
How many stages are in Intuit's interview process?
Intuit has 12 stages, set out in The process.
What framework does Intuit use to evaluate candidates?
Intuit evaluates candidates against Intuit Operating Values, set out in What Intuit scores.
What kinds of questions does Intuit ask?
Intuit's questions fall into 5 categories, grouped in The questions.
How reliable is this Intuit interview playbook?
It is compiled from public sources, and the evidence is in The research.
Sources (20)
Every public source this page was compiled from. Links open in a new tab.
12 sites, by sources
- intuit.com4
- teamblind.com4
- designgurus.io2
- roundz.substack.com2
- techprep.app1
- codemia.io1
- blog.theinterviewguys.com1
- interviewkickstart.com1
- cleverprep.com1
- ophyai.com1
- prachub.com1
- hyring.com1
- 01intuit.com/careers/hiring-process
- 02intuit.com/company/operating-values
- 03intuit.com/company
- 04intuit.com/blog/social-responsibility/job-readiness/how-to-ace-yo…
- 05techprep.app/blog/intuit-interview-process
- 06designgurus.io/answers/detail/what-is-the-intuit-interview-process-li…
- 07designgurus.io/answers/detail/top-intuit-behavioral-interview-questio…
- 08codemia.io/guides/intuit-software-engineer
- 09blog.theinterviewguys.com
- 10interviewkickstart.com/blogs/interview-questions/intuit-interview-questions
- 11cleverprep.com/companies/intuit
- 12ophyai.com/blog/company-guides/intuit-interview-guide
- 13prachub.com/interview-guide/intuit-software-engineer-interview-que…
- 14hyring.com/jobseeker-toolkit/interview-questions/company/intuit
- 15teamblind.com/post/intuit-craft-demo-tips-swe-2-pqztez7j
- 16teamblind.com/post/intuit-craft-demo-interview-suggestionstips-4i4gb…
- 17teamblind.com/post/intuit-craft-interview-ayf4nzdk
- 18teamblind.com/post/intuit-onsite-interview-qgq6cac2
- 19roundz.substack.com/p/interview-experience-intuit-sde1
- 20roundz.substack.com/p/interview-experience-46-intuit-software-development-…
Related reading
- STAR, XYZ, or CAR: Which Resume Bullet Formula Actually Works?STAR, XYZ and CAR all collapse to the same bullet in practice, why "quantify everything" is more contested than it sounds, and the one modern use of STAR that actually earns its keep.
- Jake's Resume: Why One LaTeX Template Took Over Tech HiringThe history behind the internet's most-copied resume template, why its formatting choices actually work, and how to get the same layout without touching LaTeX.
How similar companies interview
Compare Intuit's process with other Enterprise Tech companies in this playbook: