Intuit Interview Experiences

Overview

Intuit’s loop mixes a Glider-based online assessment with standard technical rounds, then adds a live Craft Demo where SDE-2+ candidates extend a real codebase instead of solving a fresh whiteboard problem.

Bengaluru hiring, not a multi-thousand-seat drive

Intuit does hire new graduates out of its Bengaluru office, but candidate reports describe a smaller, more selective funnel - a targeted early-career program plus off-campus and referral hiring - not the multi-thousand-seat placement drive some forwarded messages imply. Verify any specific college-drive or headcount claim with your placement cell or Intuit’s own careers page before repeating it.

How to use this page

Read the round table first, then the experiences below. Practise DSA with edge cases, keep one repo-based project you can extend live, and prepare a Design for Delight story where you validated an idea with real users before building it.

Round-wise process

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

Real interview experiences

Experience 1: SDE-2, backend (2025)

Profile: B.Tech CSE, ~4 years experience, applied off-campus after a referral, comfortable with mid-level DSA

Recruiter screen

• 30-minute call: current role, why Intuit, comp band, and notice period. No coding.

Online Assessment

• Glider platform, 75 minutes, 3 problems: a matrix traversal, an O(1) insert/delete/getRandom data-structure design question, and a string-decoding problem.
• Fully-passing solutions on the two easier problems mattered more than a half-finished attempt at the hardest one.

Technical rounds

• Round 1: delete a node from a binary tree and return the remaining forest as an array - DFS with a visited set.
• Round 2: OOPs (runtime vs compile-time polymorphism with a real example) and DBMS (ACID properties, when to add an index).
• Project deep-dive: architecture choices, the hardest production bug, and what they’d rebuild.

Craft Demo

• Emailed a small GitHub repo 48 hours ahead: a partially built expense-tracking service.
• In the session, implemented one new user story (a filter endpoint) live in front of three interviewers, then added unit tests and handled a null-input edge case they raised on the spot.
• Follow-up: “How would you check that this feature actually solves the user’s problem?” - answered with a Design for Delight framing (small experiment before full rollout).

Hiring manager / HR

• A time they advocated for the customer even when it meant pushing back internally.
• Notice period and relocation flexibility.

Result: Selected What helped: Narrating trade-offs out loud during the Craft Demo instead of coding in silence, and tying the follow-up answer explicitly to Design for Delight.

Experience 2: SDE-1, new grad (2024-2025)

Profile: B.Tech IT, Bengaluru-based early-career program, one internship, average contest rating

What differed

• No Craft Demo at this level - the loop was recruiter screen, Online Assessment, two technical rounds, and HR.
• Online Assessment felt tighter on time; one matrix problem needed an optimised BFS pass to finish inside the limit.
• Second technical round leaned harder into operating-systems basics (process vs thread, deadlock conditions) than DSA.

Mistakes that hurt other candidates in the same cycle

• Jumping into code before clarifying the OA’s edge cases (empty grid, duplicate values)
• Treating the HR round as a formality rather than a real evaluation of values fit
• Answering “why Intuit” with a generic tax-software line instead of anything about Design for Delight or the operating values

Result: Selected after HR Takeaway: At Intuit, a clean OA plus a values-specific HR story usually beat strong DSA with a generic “why us” answer.

Questions that come up often

Coding / technical

1. Matrix traversal - find a path or target in a grid of 0s and 1s
2. O(1) insert, delete, and getRandom data-structure design
3. Delete a node from a tree/graph and return the remaining forest as an array
4. Decode string / unique email addresses style string-parsing problems
5. OOPs: polymorphism, inheritance, with a real example from a project
6. DBMS: ACID properties, indexing, normalization
7. Operating systems: deadlocks, process vs thread
8. Craft Demo: implement a user story in a shared repo, add tests, handle edge cases live

System design (SDE-2+)

1. Design a photo/file storage service - upload, download, sharing at scale
2. Design a notification or alerting service
3. Design a roles-and-permissions system for a multi-tenant product
4. Estimate load and storage for the system you just designed

Behavioural

1. Tell me about a time you validated an idea with real users before building it (Design for Delight)
2. Describe a time you considered multiple approaches before picking one
3. Tell me about a time you did the right thing even when it was inconvenient
4. Why Intuit, specifically, over other fintech/SaaS companies?

Practical tips for Intuit

• 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 you do not know something, say so and outline how you would find out - Intuit’s Craft Demo rewards that more than a confident guess.

HR interview

After technical rounds, Intuit closes with a hiring-manager/HR conversation that checks fit against its five operating values - Integrity without Compromise, Courage, Customer Obsession, Stronger Together, and We Care and Give Back - alongside location, compensation, and notice period. Prepare those answers on the dedicated page rather than cramming them into this hub.

HR interview questions→

Common Intuit HR questions, sample answer frames, and STAR tips built around its operating values.

Similar companies

Adobe · Salesforce · Oracle · SAP · Microsoft · Google