INTERVIEW GUIDE

Intuit Software Engineer Interview: Questions & Process

Intuit's software engineer interview balances solid data-structures coding with practical, product-minded problems and a strong behavioral emphasis on customer obsession (their 'True North' values). Expect a recruiter screen, a technical phone screen, and a 3-4 round onsite that often includes a design/craft discussion. It's fair and fundamentals-driven rather than brutally hard.

The interview process

1. Recruiter screen — ~30 min call

Tests: background, interest in Intuit's products and mission, logistics

2. Technical phone screen — 45-60 min, shared editor

Tests: a data-structures/algorithms problem and clear, working code

3. Coding round — 45-60 min onsite

Tests: arrays, strings, hash maps, and a practical twist tied to a real scenario

4. Craft / design discussion — 45 min

Tests: designing a small system or feature, API and data-model thinking, and tradeoffs

5. Behavioral / values — 30-45 min

Tests: customer obsession, ownership, collaboration, and motivation for Intuit

Questions you're likely to get

Technical

Find two numbers in an array that add up to a target value.
Given daily prices, find the maximum profit from a single buy and sell.
Determine whether a string of parentheses and brackets is valid.
Group a list of strings into anagrams.
Find the maximum-sum contiguous subarray and explain your approach.
Count connected regions in a grid (e.g., number of islands).

Role-specific

Design a simple expense-categorization feature: how would you model transactions and categories?
How would you design an API to import a user's bank transactions and de-duplicate them?
Walk me through validating user-entered financial data — what edge cases matter?
How would you represent money in code, and why is a floating-point dollar amount a bug?

Behavioral

Tell me about a time you went out of your way to improve a customer's experience.
Describe a project you owned end to end and a problem you had to solve along the way.
Tell me about a time you received tough feedback and what you did with it.
Why Intuit? What draws you to consumer-finance products like TurboTax or QuickBooks?

Practice these problems live

Relevant LeetCode problems for the Intuit Software Engineer loop. Start a live, AI-run coding interview on any of them — or open the problem on LeetCode.

▶ Two Sum· Easy · LeetCode #1

A standard warm-up that checks you can reach the one-pass hash-map solution.

▶ Best Time to Buy and Sell Stock· Easy · LeetCode #121

Single-pass array scan that fits Intuit's fundamentals-first style.

▶ Valid Parentheses· Easy · LeetCode #20

Stack basics with clean edge-case handling on a short problem.

▶ Group Anagrams· Medium · LeetCode #49

Practical hash-map grouping that rewards readable code.

▶ Maximum Subarray· Medium · LeetCode #53

Tests recognition of the linear Kadane pattern and complexity reasoning.

▶ Number of Islands· Medium · LeetCode #200

Grid traversal (BFS/DFS) to confirm comfort with graphs on a grid.

How to answer (worked examples)

Design a simple expense-categorization feature.

Clarify the goal and scale first, then model the core entities — Transaction, Category, Rule/Mapping — and how a transaction gets assigned a category (explicit rules, then a fallback). Sketch the API and call out edge cases that matter in finance: re-categorization, splits, and idempotent imports. Tie it back to the user. Intuit rewards designs that keep the customer's real workflow in view.

How would you represent money in code, and why is a float a bug?

State the failure plainly: floating-point can't represent many decimal values exactly, so cents drift and totals don't reconcile — unacceptable in financial software. Propose integer cents or a decimal type, and mention currency handling and rounding rules. Showing correctness instincts around money is a strong signal for a fintech company.

Tell me about a time you improved a customer's experience.

STAR, aimed at Intuit's customer-obsession value. Situation: a real user pain point you noticed. Action: what you built or changed and why it helped the customer specifically. Result: the measurable improvement. Authentic customer empathy lands harder than a generic project story here.

What Intuit looks for

Solid data-structures fundamentals and clean, tested code
Practical design sense — sensible data models and APIs for real product features
Customer obsession — you reason from the user's actual needs, not just the spec
Correctness instincts, especially around money and data validation
Ownership and growth mindset — you take feedback well and drive problems to done
Red flag: ignoring edge cases or treating the values round as a checkbox

FAQ

How hard is the Intuit SWE interview?

Fair and fundamentals-driven. Expect easy-to-medium data-structures problems plus a design discussion — challenging but rarely the brutal hard-LeetCode bar of some top-tier loops.

How much do values and behavioral matter?

A lot. Intuit's 'True North' values, especially customer obsession, get a dedicated round — prepare specific stories about helping real users.

Is there a system design round for new grads?

Often a scoped craft/design discussion rather than full distributed-systems design — think modeling a feature, its data, and its API at your level.

What language should I use?

Whatever you're strongest in. Intuit cares about clear, correct code and your reasoning, not a particular stack.

How long is the process?

Generally a few weeks from recruiter screen to decision, depending on scheduling.

Practice the coding and the customer stories

Intuit weighs your values answers as heavily as your code. Rehearse the data-structures round, the design discussion, and your customer-obsession stories — out loud — with OfferLoop's realtime voice coach before your loop.

Practice this interview out loud →

All Intuit interviews →Intuit Data Analyst interview →Intuit Data Scientist interview →Intuit Data Engineer interview →Intuit Machine Learning Engineer interview →

OfferLoop is an independent interview-practice tool and is not affiliated with, endorsed by, or sponsored by Intuit. All company names and trademarks are the property of their respective owners.

Interview formats vary by team, level and year, and this guide is compiled from general knowledge of publicly discussed hiring processes — treat it as preparation material, not an official description of Intuit's current process.