Intuit - interview guide

Intuit interview questions - a complete guide

Intuit's most distinctive round is the craft demo - you build a small app in advance and then explain and extend its code in the interview. Here is how to prepare for it and the other rounds.

Language:EnglishHinglish

About Intuit

Intuit makes financial and small-business products such as TurboTax, QuickBooks, Credit Karma and Mailchimp, with a large development centre in Bengaluru. The work involves money and tax, so correctness and customer focus matter.

This guide covers 13 Intuit interview questions with answers - what each question checks and how to answer it - plus the Intuit interview process, round by round, a 7-day preparation plan for freshers, tips and the mistakes to avoid.

Intuit hiring process

  1. Recruiter call

    The role, your background and the timeline.

  2. Online coding screen

    Reported as coding questions on a platform such as Glider.

  3. Craft demo

    Build a small given problem at home, then show the code in the interview, explain your decisions and make changes live.

  4. Technical and HM rounds

    DSA, low-level/high-level design, and behavioural with the hiring manager.

Intuit does not publish its India fresher interview process in detail (as of our check). This is based on candidate reports - many of them for experienced roles, so the fresher process can differ. Confirm with the recruiter.

Sources (checked 16 October 2026): Intuit Careers. Hiring processes change - read the official notice before you apply.

Intuit interview questions and answers

Craft demo

This looks at clean code, tests and your decisions - not just an app that runs.

  1. 1.What will you show in the craft demo?

    What they're checking
    Your way of engineering.
    How to answer
    A small scope that fully works, a clean folder structure, a few key tests, a README (how to run it), and 2-3 decisions whose reasons you can explain - such as why this database.

  2. 2.What will you do if the interviewer asks for a new feature mid-demo?

    What they're checking
    A live change - the real test of understanding the code.
    How to answer
    Clarify the requirement with 1-2 questions, say where the change will go in the code, make a small change and add a test. Don't panic - talk while you think.

  3. 3.Name one decision in your demo you would make differently now.

    What they're checking
    Self-review and maturity.
    How to answer
    Admit a real weakness (such as validation not being in one place), its impact, and the better way. It shows you look at code critically.
    Example answer
    “I stored amounts as floats in my expense app. Later I saw errors like 0.1 + 0.2, so now I would store money in paise (integers) - 10.50 rupees as 1050.”

Coding and design

  1. 4.Write a function that calculates tax on income by slab.

    What they're checking
    Logic like a tax product - boundary cases.
    How to answer
    Keep the slabs in a list (limit, rate). Apply the rate to the income falling in each slab and add it up. Always test income exactly at a slab limit.

  2. 5.Why don't we keep money in float/double?

    What they're checking
    Financial correctness.
    How to answer
    Floats can't store numbers like 0.1 exactly in binary - small errors add up. Use integers (paise/cents) or BigDecimal.

  3. 6.Catch duplicate payments in invoices - same customer, same amount, within 24 hours.

    What they're checking
    A real-world data problem.
    How to answer
    Group by customer and amount, sort each group by time, and flag neighbouring payments less than 24 hours apart. O(n log n).

  4. 7.Find the common free slots in two people's calendars.

    What they're checking
    Intervals.
    How to answer
    Combine both people's busy intervals, sort by start time, merge overlaps, and the gaps between merged intervals (within working hours) are free slots.

  5. 8.Low-level design of an expense tracker - categories and a monthly budget alert.

    What they're checking
    LLD.
    How to answer
    Classes: User, Expense (amount, category, date), Category, Budget (category, monthly limit). When an expense is added, check that month's total; alert through a Notifier at 80% and 100% of the limit.

  6. 9.High-level design of an invoicing service that takes heavy load at month-end.

    What they're checking
    HLD.
    How to answer
    Invoice requests in a queue, workers that scale horizontally, an idempotency key per invoice so it isn't created twice, PDF generation as a separate service, and a database + retries for status.

  7. 10.How do you stop a double charge if the payment API is called twice?

    What they're checking
    The effect of retries.
    How to answer
    The client sends a unique key with each payment; the server first checks whether a result exists for that key - if so, return that result instead of charging again.

Behavioural

Intuit's values include things like customer obsession and courage.

  1. 11.When did you build something users didn't ask for but actually needed?

    What they're checking
    Customer focus.
    How to answer
    How you understood the user's real problem (by talking, by looking at data), what you built, and what difference it made.

  2. 12.When did you show courage and question a wrong decision?

    What they're checking
    Courage.
    How to answer
    What seemed wrong, how you made your case with data, and the result - whether or not your view was accepted.

  3. 13.Why Intuit?

    What they're checking
    Motivation.
    How to answer
    A genuine interest in fintech/tax or helping small businesses, and why a hands-on process like the craft demo suits you.

7-day preparation plan for the Intuit interview

  1. Day 1: Craft demo - decide the scope and build the basic app.
  2. Day 2: Tests, a README and clean-up for the demo.
  3. Day 3: Arrays, intervals, sorting - five problems.
  4. Day 4: Low-level design (expense tracker, invoices).
  5. Day 5: High-level design - queues, idempotency, scaling.
  6. Day 6: Present the demo to a friend, with a live change.
  7. Day 7: Behavioural stories + mock coding.

Preparation tips

  • Build a small but complete app for the craft demo - not a big unfinished one.
  • Practise explaining every decision in your demo.
  • Integers/BigDecimal and boundary tests for money logic.
  • Talk about idempotency and retries in design.

Mistakes to avoid

  • Using someone else's code or a template in the craft demo that you can't explain.
  • Keeping money in floats.
  • Panicking at a live change and writing code without thinking.

Frequently asked questions

What is the Intuit craft demo?

A round where you build a given problem at home, then explain the code and make live changes in the interview.

Where is Intuit's coding screen held?

Reports say on an online platform such as Glider.

Where is Intuit's India office?

It has a large development centre in Bengaluru.

What is asked in Intuit's design round?

According to reports, both low-level and high-level design - often on finance or small-business use cases.

Similar companies - Product and internet companies

More company guides

Read next

On a live call, Cuelyte AI hears questions like these and has an answer ready in about a second, built from your resume and notes. Coding interviews: how Cuelyte AI helps

Ready for your Intuit interview?

Practise these questions with Cuelyte AI: add your resume, type a question and get a clear answer in your own words - in English, Hindi or Hinglish. Free to start.

Start free - no card neededSee pricing