Intuit Interview Process 2026: Craft Demo, 4-6 Round Loop & Timeline

Last updated: August 2026

TL;DR

Intuit’s interview process runs a recruiter screen, then a live technical screen, then a virtual onsite “craft loop” of four to six interviews that includes the Craft Demonstration, a system design round, a behavioral round mapped to Intuit’s operating values, and a hiring manager conversation, with most candidates reporting two to four weeks end to end. The Craft Demonstration is the round that decides most outcomes: candidates are commonly given a repository 24 to 48 hours ahead and asked to implement user stories live in front of two to four interviewers, with clean code and unit tests weighted heavily. Rehearse it in OphyAI Coding Interview, drill the values stories in OphyAI Interview Practice, and use OphyAI Interview Copilot for mock rounds on Zoom, Teams or Meet.

Quick Answer: Intuit Interview Process

Stage	What to prepare
Recruiter screen	A specific “why Intuit” answer tied to a product you have used (TurboTax, QuickBooks, Credit Karma, Mailchimp) and the problem it solves for a small business or a filer.
Technical screen	Live coding, commonly 60-90 minutes, on data structures and algorithms with some practical design; candidates frequently report the Glider platform.
Craft Demonstration	A shared repository given in advance, then live implementation of user stories with tests, plus a walkthrough of your architectural choices and trade-offs.
System design round	A product-shaped design problem: financial data pipelines, tax or ledger correctness, multi-tenant SaaS, third-party integrations.
Values and behavioral round	STAR stories mapped to Customer Obsession, Stronger Together, Integrity Without Compromise and Courage.
Hiring manager conversation	What you own, how you decide, how you handle being wrong, and what you want next.

Action Plan: Prepare for Intuit by Round

Round	What Intuit tests	What to do before the interview
Recruiter screen	Motivation, level fit, logistics	Name the product line and the customer problem you find interesting; know whether you are being considered for SE1, SE2, Senior or Staff
Technical screen	Whether you code cleanly under time pressure and explain complexity	Solve 30-50 medium problems narrating aloud; practise in the language you will actually use
Craft Demonstration	Production judgment: naming, structure, tests, incremental delivery	Practise picking up an unfamiliar repository and shipping one small, tested change in 45 minutes
System design	Data correctness, integrations, scale, failure modes	Prepare one financial-data design end to end: ingestion, reconciliation, idempotency, audit trail
Values round	Whether your stories evidence the five operating values	Write six STAR stories and label each with the value it demonstrates
Hiring manager	Ownership and judgment	Prepare one story about a decision you got wrong and what you changed

If you have only one week, spend it on the Craft Demonstration. It is the round most candidates have never done before, and the failure mode is not weak coding but weak process: no tests, no incremental commits, and no narration of why one approach was chosen over another.

What Makes Intuit Different

Intuit builds financial software used by consumers, the self-employed, and small businesses: TurboTax for filing, QuickBooks for accounting and payroll, Credit Karma for credit and lending, and Mailchimp for marketing. The company describes its mission as powering prosperity around the world, and the interview process is unusually explicit about mapping candidate answers back to that mission and to a published set of operating values.

Several characteristics shape what Intuit interviewers look for:

Five published operating values. Intuit’s operating values are Integrity Without Compromise, Courage, Customer Obsession, Stronger Together, and We Care and Give Back. Behavioral interviewers are trained to map your answers onto them, and Intuit runs a dedicated cross-functional session focused on values alignment. Knowing the exact wording is worth the ten minutes it takes.
Customer Obsession has a specific meaning. Intuit frames it as falling in love with the customer’s problem rather than with your solution. Candidates who describe a feature they built score lower than candidates who describe the customer pain they measured, the thing they tried, and what the data said afterwards.
The Craft Demonstration replaces the whiteboard. Rather than testing whether you can invent an algorithm on the spot, Intuit’s signature round tests whether you can work inside an existing codebase the way an engineer actually does: read it, extend it, test it, and defend the choices.
Correctness carries unusual weight. This is tax, payroll and accounting software. A rounding error is not a cosmetic bug. Design and coding rounds reward candidates who name the failure modes, the reconciliation strategy, and the audit trail without being prompted.
AI fluency is now part of the conversation. Candidate reports through 2026 describe questions about working with AI-assisted development: how you validate generated code, where you would not use it, and how you keep an AI-assisted change reviewable. Treat it as a judgment question rather than a tools question.

Many candidates use OphyAI Interview Copilot during Intuit-style mock interviews on Zoom, Teams or Meet to keep answers structured and to rehearse narrating code while they type. Intuit has not published a policy on candidate use of AI tools during its live interviews, so ask your recruiter what is permitted and follow their answer; the Craft Demonstration in particular is a round where you must be able to defend every line yourself.

Interview Process Overview

The shape below is what most software candidates report. Product, data and design loops follow the same spine with the craft round swapped for a portfolio or case round.

Stage	Format	Duration	Timeline
Recruiter screen	Phone or video	30-40 minutes	Week 1
Technical screen	Live coding, shared editor, commonly Glider	60-90 minutes	Week 1-2
Craft Demonstration	Video, 2-4 interviewers, repo shared 24-48 hours ahead	About 90 minutes	Week 2-3
Onsite craft loop (remaining rounds)	4-6 interviews total, often on one day	4-6 hours	Week 2-3
Hiring manager and values round	Video	30-60 minutes	Week 2-3
Decision and offer	Written	-	Week 3-4

The recruiter screen is short and covers motivation, level, location and compensation expectations. Intuit hires across several distinct product organisations, so ask which one the requisition sits in: the work in TurboTax’s tax engine looks nothing like the work in Mailchimp’s marketing platform. Draft a 60-second “why Intuit” answer in OphyAI Interview Practice and read the transcript back for filler.

The technical screen is a conventional live coding round. Candidates report data structures and algorithms problems at medium difficulty, some basic design discussion, and increasingly a question about how you would work with AI-generated code. The platform most often named is Glider. Rehearse narrating trade-offs while typing with OphyAI Coding Interview, then re-solve the same problem with nothing open.

The Craft Demonstration is Intuit’s distinctive round and gets its own section below. The rest of the onsite loop typically adds a system design interview, a values-focused behavioral interview, and a hiring manager conversation, run back to back over four to six hours. Drill the behavioral half in OphyAI Interview Practice in behavioral format and use the per-answer feedback to cut each story to under two minutes.

The offer stage moves quickly by industry standards. Candidates commonly describe the whole process wrapping in two to four weeks, which is faster than most companies of comparable size. Intuit has not published a target time to hire, so treat that as candidate-reported.

The Craft Demonstration

The Craft Demonstration is the round that separates Intuit’s loop from a standard tech interview, and the one candidates most often walk into unprepared.

The format. Candidates commonly report being given access to a GitHub repository 24 to 48 hours before the session, then joining a roughly 90-minute call with two to four interviewers and implementing user stories live inside that codebase. Some candidates instead present a past project or a take-home and walk through the architecture, testing strategy and trade-offs. Ask your recruiter which variant your loop uses, because the preparation differs.

What is actually scored. Not the volume of code you produce. Interviewers watch how you orient yourself in an unfamiliar repository, whether you write a test before or alongside the change, whether your naming and structure would survive review, whether you deliver something working incrementally rather than a large unfinished refactor, and whether you say out loud why you chose one approach over another. Engineering judgment is the phrase candidates hear most often afterwards.

The red flags. Shipping no tests is the single most cited failure. Beyond that: silently rewriting parts of the codebase the story did not ask you to touch; freezing when the repository does not look like what you expected; refusing to ask clarifying questions about the user story; and producing something that works but that you cannot explain when questioned.

How to prepare. Take any open-source repository you have never seen, give yourself 45 minutes, and ship one small, tested change while narrating what you are doing. Do that three times. Then, when the real repository arrives, spend your prep window reading the build, the test setup and the existing patterns rather than writing speculative code: the interview is graded on the hour you spend with them, but it is won by knowing how to run the tests before the call starts. Use OphyAI Coding Interview to pressure-test your approach on a practice problem, then implement it unassisted.

Role-Specific Breakdowns

Software Engineer

The core track, spanning TurboTax, QuickBooks, Credit Karma, Mailchimp and the platform and AI organisations.

Technical screen (60-90 minutes). Medium-difficulty data structures and algorithms, complexity discussion, and a practical follow-up that changes the constraints.

Craft Demonstration (about 90 minutes). As above. Bring test-writing muscle memory in your primary language.

System design (mid-level and above). Prompts skew toward financial data rather than generic web scale: ingesting bank transactions and reconciling them, designing a payroll calculation service where correctness is non-negotiable, multi-tenant isolation for small business accounts, or an integration layer over dozens of third-party financial institutions. Idempotency, audit trails and eventual consistency are the vocabulary that scores. See our system design interview guide for a framework.

Values round. Six STAR stories, labelled by value.

Use OphyAI Coding Interview to rehearse one financial-data design prompt from requirements through failure modes, then explain it aloud with no tool open.

Product Manager

Intuit PM loops weight customer discovery heavily, in line with the company’s Customer Obsession value and its long association with design-led product development.

What is tested. How you find a real customer problem rather than assume one, how you size it, how you decide what not to build, and how you work with engineering and design. Expect a product case, a metrics discussion, and a values round.

How to prepare. Prepare one story where customer research changed your plan and one where you killed something you had built. Practise product cases in OphyAI Interview Practice case format and make sure every answer names a metric and a trade-off.

Data Scientist and Data Analyst

What is tested. SQL fluency, experiment design, and whether your analysis leads to a decision. Expect a technical screen with SQL and statistics, a case round on a product metric, and the same values round as everyone else.

How to prepare. Practise writing SQL out loud, and bring one analysis where the result was inconvenient and you reported it anyway; that story maps directly onto Integrity Without Compromise. Rehearse in OphyAI Interview Practice technical format.

TurboTax Live Expert and Bookkeeping Expert (Seasonal)

Intuit hires credentialed tax preparers, CPAs, enrolled agents and bookkeepers for remote seasonal roles supporting filers.

What is tested. Credential verification, tax or bookkeeping knowledge assessments, customer communication over video, and comfort with Intuit’s tooling. The interview is far more about explaining a complex rule in plain language than about coding.

How to prepare. Rehearse explaining one complicated tax or accounting concept to a non-expert in 90 seconds, and have your credential details and continuing education status ready. Practise the customer-facing rounds in OphyAI Interview Practice behavioral format.

New Grad and Intern

Stages. Recruiter screen, a technical screen, and a shortened loop that usually still includes a craft-style round and a values conversation.

How to prepare. Be able to go several layers deep on one class or personal project, down to why you chose the data structure and how you tested it. That depth is what new-grad craft rounds probe.

Common Questions with Frameworks

1. “Walk us through this repository and implement the first user story.” (Craft Demonstration)

Approach: Orient out loud before typing: where the entry point is, how tests run, what pattern the existing code follows. Ask one clarifying question about the story’s edge cases. Write or extend a test, make it pass, commit, then move on. Narrate every choice. A smaller, tested, explained change beats a larger silent one.

2. “Design a system that ingests bank transactions and reconciles them against a ledger.” (System Design)

Approach: Clarify volume, latency tolerance and what “reconciled” means. Then cover ingestion and deduplication with idempotency keys, the canonical ledger and why it is append-only, the matching strategy and what happens to unmatched items, replay and audit, and the failure modes: duplicate webhooks, out-of-order events, a provider that restates history. Money handled in integer minor units, never floating point.

3. “Tell me about a time you fell in love with a customer’s problem.” (Customer Obsession)

Approach: Use the STAR method. Lead with the customer and the evidence you gathered, not the feature. Name what you learned that you did not expect, what you decided not to build because of it, and how you measured whether the problem actually went away.

4. “Describe a time you spoke up when it was uncomfortable.” (Integrity Without Compromise / Courage)

Approach: Pick a real disagreement with a cost to you: a deadline you said would slip, a metric you reported that undermined your own project, a shortcut you refused. Explain the reasoning, how you raised it, and what happened, including if it went badly. Stories where speaking up cost nothing do not test the value.

5. “How do you validate code an AI assistant generated for you?” (Judgment)

Approach: Answer as a reviewer, not a user. Describe reading the change for correctness against the requirement, checking edge cases and error paths, writing or extending tests that would fail if the logic were wrong, checking dependencies and licences, and keeping the change small enough to review. Say where you would not use generated code: unfamiliar security-sensitive paths, or anything you could not explain in review.

6. “Tell me about a time you worked across teams to ship something.” (Stronger Together)

Approach: Choose a story where the other team had a competing priority. Describe how you found the shared goal, what you gave up, and how the handoff actually worked. Interviewers are checking whether you can name the other side’s constraints fairly.

For more practice, see our guide to common interview questions and answers.

Culture Fit: The Five Operating Values

Integrity Without Compromise. Intuit describes this as speaking the truth and assuming the best intent. In interviews it surfaces as questions about mistakes, bad news you delivered, and moments where the honest answer was inconvenient.

Customer Obsession. Fall in love with the customer’s problem, not your solution. Answers that start with a feature and never reach a customer are the most common way strong engineers under-score here.

Courage. Questions about risk, dissent, and doing the unpopular thing. Bring at least one story where you were the only person arguing a position.

Stronger Together. Cross-functional collaboration and diverse input. Prepare a story involving design, data, support or a partner team, not just your own squad.

We Care and Give Back. The least-tested value in interviews, but worth knowing it exists; it occasionally appears as a question about mentoring or community work.

What interviewers screen for: production judgment over cleverness, evidence you talked to a real customer, comfort saying “I do not know”, precision about correctness in financial contexts, and stories where you personally did the thing rather than described a team’s outcome.

Compensation Overview (2026 Estimates, USD)

The figures below are candidate-reported United States medians from Levels.fyi, checked in August 2026. Intuit does not publish a pay table; United States pay transparency laws mean many Intuit job postings carry a base range, which is the most reliable number available to you before an offer. Packages are cash-heavy relative to pre-IPO startups, with restricted stock units on a standard multi-year schedule and an annual bonus.

Role	Base Salary	Total Compensation (Base + Bonus + Equity)
Software Engineer 1 (new grad)	~$137,000-$165,000	~$154,000
Software Engineer 2	Level-dependent, ask for the posted band	~$201,000
Senior Software Engineer	Level-dependent, ask for the posted band	~$244,000
Staff Software Engineer	Level-dependent, ask for the posted band	~$365,000
Senior Staff Software Engineer	Level-dependent, ask for the posted band	~$552,000
All engineering levels (median package)	-	~$260,000

Sample sizes thin out quickly above Staff, and Bay Area figures pull the medians up relative to Intuit’s other United States sites. Ask your recruiter for the level, the posted base range for the location, the initial grant value in dollars, the vesting schedule and the refresh policy before you respond. For strategies on the conversation, see our salary negotiation guide.

Preparation Timeline: 4-6 Weeks

Week	Focus	Activities
1	Product and values research	Pick the product organisation you are interviewing for and use the product. Read Intuit’s operating values and write the exact wording down. Draft your “why Intuit” answer.
2	Coding fluency	Solve 30-50 medium problems in your interview language, narrating aloud. Review complexity, hash maps, trees and string manipulation. Use OphyAI Coding Interview for approach checks, then re-solve unassisted.
3	Craft rehearsal	Three times: take an unfamiliar open-source repository and ship one small tested change in 45 minutes while narrating. Practise running an unknown test suite fast.
4	System design	Build one financial-data design end to end: ingestion, idempotency, reconciliation, audit trail, failure modes. Review our technical interview prep guide.
5	Values and behavioral	Write six STAR stories, one per value plus a spare, and drill them in OphyAI Interview Practice until each is under two minutes.
6	Integration	Run one full mock loop back to back. Prepare five questions per interviewer. Confirm the craft round variant and the repository access with your recruiter.

Common Mistakes

Shipping the craft round with no tests. The most cited rejection reason. Even one meaningful test, written before the implementation, changes how the round reads.

Rewriting code the user story did not ask you to touch. Interviewers read unrequested refactoring as poor judgment about scope, not as initiative.

Describing features instead of customer problems. Customer Obsession is scored on evidence. A story with no customer in it does not satisfy it, however impressive the engineering.

Generic values answers. Intuit publishes its values, and interviewers map answers to them explicitly. Turning up without knowing the five is an avoidable loss.

Floating point for money. In tax, payroll and accounting contexts this is read as inexperience with financial systems. Use integer minor units and say so.

Not asking which craft variant you will get. Preparing to present a past project and then being handed a repository, or the reverse, wastes the one round that matters most.

Prepare for Intuit with OphyAI

Intuit’s loop rewards engineers who work well inside someone else’s codebase, who test by reflex, and who can point at a real customer behind the work. All three improve fast with structured rehearsal.

Use OphyAI Interview Practice for voice or text mock interviews in behavioral, technical, system design and case formats, with a transcript and per-answer feedback on each values story. Use OphyAI Coding Interview to rehearse the technical screen and a financial-data design prompt, then re-solve unassisted. Use OphyAI Interview Copilot on mock Zoom, Teams or Meet calls to check your structure; Intuit has not published a policy on candidate AI use in live interviews, so ask your recruiter and follow their answer. Start practicing →

Start Your Intuit Application

Ready to apply? OphyAI can help at every stage:

Search for open roles at Intuit and similar companies with AI-powered job matching
Generate a tailored cover letter that highlights your fit for the role, plus follow-up emails and thank-you notes for after your interviews
Track your application status alongside every other role you’re pursuing

Pair these with Interview Copilot for structured mock interviews, or practise first with OphyAI Interview Practice.

For product details, see Interview Copilot.

Frequently Asked Questions

How many rounds are in the Intuit interview process?

Most software candidates report five to seven conversations: a recruiter screen, a live technical screen, and then a virtual onsite craft loop of four to six interviews that includes the Craft Demonstration, a system design round, a values-focused behavioral round and a hiring manager conversation. New grad and intern loops are shorter. Product, data and design loops follow the same spine with the craft round replaced by a case or portfolio round. Ask your recruiter for the exact list, because it varies by organisation and level.

What is the Intuit Craft Demonstration?

It is Intuit’s signature technical round, usually around 90 minutes with two to four interviewers. Candidates commonly report being given a GitHub repository 24 to 48 hours in advance and then implementing user stories live inside it, with clean code and unit tests weighted heavily. Some loops instead ask you to present a past project or take-home and defend the architecture, testing strategy and trade-offs. Interviewers say they are assessing engineering judgment rather than polish, so narrate why you chose each approach.

How long does Intuit take to make a decision?

Candidates commonly describe the whole process finishing in two to four weeks from recruiter screen to offer, which is faster than most companies of similar size, partly because the onsite rounds are usually scheduled together on one day. Intuit has not published a target time to hire, so treat that as candidate-reported. If you have not heard back a week after the loop, one polite follow-up to the recruiter is appropriate; hiring committees and level calibration are the usual reason for a delay.

What are Intuit’s core values and do they matter in the interview?

Intuit’s operating values are Integrity Without Compromise, Courage, Customer Obsession, Stronger Together, and We Care and Give Back. They matter more than at most companies because interviewers are trained to map your answers onto them and Intuit runs a dedicated session focused on values alignment. Prepare six STAR stories and label each with the value it evidences. The two that carry the most weight in practice are Customer Obsession and Integrity Without Compromise.

Does Intuit ask about AI tools in interviews?

Candidate reports through 2026 describe questions about AI-assisted development in both the technical screen and the craft round: how you validate generated code, how you keep an AI-assisted change reviewable, and where you would not use it. Answer as a reviewer rather than a user, and name the checks you run. This is a judgment question about production risk, not a test of which assistant you prefer.

Can I use an AI interview copilot during an Intuit interview?

Intuit has not published a policy we could verify on candidate use of AI assistants during live interviews, and rules differ by employer, role and round, so ask your recruiter and follow what they say. The Craft Demonstration in particular is a defend-your-choices round, so anything you cannot explain yourself is a liability. The dependable use is preparation: rehearse with Interview Practice and Interview Copilot before the real loop.

Sources and verification notes

All sources were checked in August 2026. Direct first-party fetches were blocked by the network policy where this post was written, so Intuit’s own pages were consulted through search result summaries and are flagged as such. Intuit does not publish round counts, craft-round formats or interview timelines, so every number here is a candidate-reported range rather than a company commitment. Where official statements and candidate reports differ, the text says so.

Intuit, Operating Values: the five published operating values and their definitions. Consulted via search summary in August 2026.
Intuit Blog, “How to ace your software engineer interview at Intuit”: first-party preparation guidance for engineering candidates. Consulted via search summary in August 2026.
Intuit Careers, Working at Intuit: culture language and hiring context. Consulted via search summary in August 2026.
InterviewQuery, Intuit Software Engineer interview guide: reported loop shape, technical screen length, Glider platform, craft loop composition. Third-party, checked August 2026.
TechPrep, Intuit’s Interview Process 2026: reported two to four week timeline, recruiter screen length, and stage-by-stage breakdown. Third-party, checked August 2026.
The Interview Guys, Intuit interview questions 2026: reported Craft Demonstration format (repository shared 24-48 hours ahead, two to four interviewers, live user stories, unit testing emphasis) and the 2026 AI-readiness questions, plus role variants including TurboTax expert roles. Third-party, checked August 2026.
Interview Kickstart, Intuit interview questions and Intuit software engineer salary: reported behavioral emphasis and values mapping. Third-party, checked August 2026.
Levels.fyi, Intuit Software Engineer salaries: candidate-reported United States medians by level and the overall median package. Self-reported sample, checked August 2026.