interviewquestions.

Big tech

Amazon4 rounds · $110.5k-$160kApple4 rounds · $145kGoogle6 rounds · $118k-$170kMeta6 rounds · $137kMicrosoft5 rounds · $84.2k-$165.2k

US and global tech

Netflix6 rounds · $100k-$300kUber5 rounds · $150k-$158kAirbnb6 rounds · $128k-$142kStripe7 rounds · $122.1k-$134.4kSalesforce3 rounds · $110k-$153kAdobe3 rounds · $76.7k-$152.2kLinkedIn6 rounds · $154kIntuit4 rounds · $55.5-$75/hrCisco4 rounds · $92.1k-$136kAtlassian3 rounds · $122.4k-$159.8kSpotify6 rounds · $125.6k-$179.4kTwitter4 rounds · $127k-$297kOpenAI5 rounds · $230k-$490kPalantir5 rounds · $145k-$155kTesla5 rounds · $140k-$300kTikTok5 rounds · $128k-$256kDatabricks6 rounds · $137.8k-$155kSnowflake5 rounds · $42-$60/hrDatadog6 rounds · $100k-$110kCloudflare6 rounds · $150k-$216kCoinbase6 rounds · $60/hrDoorDash6 rounds · $107.4k-$158kRoblox6 rounds · $153kEpic Systems5 rounds · $110kShopify5 rounds · $110kRobinhood6 rounds · $166k-$195k

Wall Street, banks and payments

Goldman Sachs4 rounds · $110k-$115kJP Morgan4 rounds · $95k-$125kMorgan Stanley3 rounds · $70k-$110kBank of America4 rounds · $94.2kCiti5 rounds · $80k-$115kWells Fargo5 rounds · $48.08/hrCapital One5 rounds · $140kBlackRock4 rounds · $105k-$125kBloomberg5 rounds · $158kD. E. Shaw4 rounds · $25kAmerican Express3 rounds · $78k-$124.8kMastercard2 rounds · $72k-$115kVisa4 rounds · $108k-$120kPayPal4 rounds · $116.5k-$173.3kDeutsche Bank4 rounds · $100kBarclays3 rounds · $110kHSBC5 rounds · ₹6-10 LPAArcesium4 rounds · $10kCitadel5 rounds · $200k-$250kJane Street4 rounds · $300kHudson River Trading5 rounds · $300kSusquehanna (SIG)5 rounds · $300kFidelity Investments4 rounds · $92kPNC5 rounds · $39.1k-$126.5kCharles Schwab4 rounds · $26.01/hrEdward Jones5 roundsVanguard4 rounds · $52k-$55kU.S. Bank5 rounds · $20-$22/hr

Consulting and Big 4

McKinsey4 rounds · $120kBCG4 rounds · $110kBain4 rounds · $120kDeloitte3 rounds · $75k-$78kEY3 rounds · $75k-$100kKPMG3 rounds · $78k-$90kPwC3 rounds · $61k-$100kAccenture5 rounds · ₹4.5-6.5 LPAIBM3 rounds · $121k-$181.4kZS Associates5 rounds · $90k-$102k

Enterprise and cloud

Oracle3 rounds · $61.2k-$141.2kServiceNow4 rounds · $130k-$136kDell3 rounds · $101.7k-$131.7kVMware5 rounds · ₹18-30 LPASAP5 rounds · ₹18-28 LPAAkamai5 rounds · $114.3k-$136.3kADP4 rounds · ₹6-11 LPAOptum4 rounds · $58.8k-$105k

Semiconductors and hardware

NVIDIA3 rounds · $100k-$166.75kIntel3 rounds · $105.7k-$149.2kQualcomm3 rounds · $122.8k-$184.2kTexas Instruments3 rounds · $100k-$137.5kCadence3 rounds · $74.2k-$137.8kSynopsys5 rounds · $92.6kMathWorks4 rounds · $100k-$130kSamsung3 rounds · ₹14-28 LPAAMD5 rounds · $119k-$170k

Retail and industrial

Walmart4 rounds · $80k-$155kTarget4 rounds · $34/hrHoneywell4 rounds · $68k-$115kSiemens4 rounds · $32.69-$58.84/hrBosch3 rounds · ₹6-9 LPAABB5 rounds · $80kCaterpillar7 rounds · $89.2k-$145kSchneider Electric4 rounds · $84k

Aerospace and defense

Boeing6 rounds · $82k-$89kLockheed Martin5 rounds · $91kNorthrop Grumman4 rounds · $62.3k-$114.4kRaytheon4 rounds · $68.9k-$144.2kSpaceX5 rounds · $125k-$145kBooz Allen Hamilton6 rounds · $52.9k-$108kLeidos5 rounds · $57.9k-$125.7kGeneral Dynamics6 rounds · $19.55-$34.5/hrAnduril Industries4 rounds · $112k-$149k

Telecom, media and consumer brands

Verizon5 rounds · $16-$21/hrT-Mobile5 rounds · $19.5/hrAT&T5 rounds · $21.43-$24.95/hrComcast6 rounds · $19/hrDisney5 roundsProcter & Gamble5 rounds · $85k-$122.2kPepsiCo5 rounds · $21.07-$25.8/hrThe Coca-Cola Company (and bottlers)5 rounds · $19.75-$27/hrNike5 rounds · $17/hr

Insurance, healthcare and pharma

State Farm6 rounds · $63.1k-$71.7kGEICO7 rounds · $20.65-$25.81/hrProgressive6 rounds · $54k-$63.5kUSAA6 rounds · $43.8k-$45.8kHumana5 rounds · $71.1k-$97.8kKaiser Permanente5 rounds · $38.15-$40.14/hrHCA Healthcare4 rounds · $19.29-$24.81/hrJohnson & Johnson5 rounds · $23.5-$52.5/hrPfizer4 rounds · $76k-$199.6k

Stores, grocery and pharmacies

Costco5 rounds · $20-$32.9/hrKroger4 rounds · $17-$26.85/hrPublix4 roundsTrader Joe's4 rounds · $16-$20/hrWhole Foods Market5 rounds · $17-$25.4/hrALDI (US)5 rounds · $18-$18.5/hrH-E-B6 roundsDollar General5 rounds · $18.31-$18.56/hrHome Depot5 rounds · $18.5-$21.5/hrLowe's5 rounds · $15.92-$16.15/hrCVS Health6 rounds · $16.5-$25/hrWalgreens5 rounds · $19.5-$23/hrBest Buy4 rounds · $16.9-$21.45/hrTJX (TJ Maxx, Marshalls, HomeGoods)5 rounds · $12.75-$13.25/hrMacy's5 rounds · $15-$19.51/hrKohl's4 rounds · $15/hrNordstrom4 rounds · $17.7-$21.9/hrSephora5 rounds · $22.6-$26/hrUlta Beauty5 rounds · $16.9-$24/hrDick's Sporting Goods5 rounds · $12.5-$31.5/hrPetSmart5 rounds · $15.08-$22.08/hrlululemon4 rounds

Restaurants and coffee

Starbucks4 rounds · $15.25-$24.69/hrChick-fil-A5 rounds · $15-$18/hrChipotle4 rounds · $20-$21/hrMcDonald's4 rounds · $15.5-$19.89/hrTaco Bell4 rounds · $14.42-$22.04/hrWendy's4 rounds · $11.5-$22.29/hrBurger King4 rounds · $12-$19.5/hrDunkin'3 rounds · $15-$20/hrPanera Bread4 rounds · $15-$20/hrDomino's4 rounds · $9/hr

Airlines, hotels and delivery

American Airlines5 rounds · $37.91/hrUnited Airlines5 rounds · $37.1/hrSouthwest Airlines5 rounds · $32.62/hrDelta Air Lines5 roundsMarriott International4 rounds · $16-$22/hrHilton4 rounds · $21/hrEnterprise Mobility (Enterprise Rent-A-Car)5 rounds · $62.7kFedEx4 rounds · $17.75-$18.25/hrUPS5 rounds · $21/hrUSPS (United States Postal Service)6 rounds

India: product companies and startups

Flipkart5 rounds · ₹22-28 LPAPaytm4 rounds · ₹16-22 LPASwiggy4 rounds · ₹16-22 LPAZoho6 rounds · ₹5-7 LPAZomato4 rounds · ₹18-25 LPAMeesho4 rounds · ₹25-35 LPANykaa4 rounds · ₹10-18 LPAOLA4 rounds · ₹16-22 LPACRED5 rounds · ₹18-25 LPAGroww5 rounds · ₹15-28 LPAPhonePe5 rounds · ₹18-25 LPARazorpay4 rounds · ₹18-25 LPAZerodha4 rounds · ₹12-25 LPADream114 rounds · ₹15-30 LPABrowserStack5 rounds · ₹15-28 LPAFreshworks4 rounds · ₹20-28 LPABlinkit5 rounds · ₹18-25 LPADunzo5 rounds · ₹12-18 LPALicious4 rounds · ₹12-18 LPAUrban Company4 rounds · ₹18-25 LPABigBasket4 rounds · ₹6-10 LPABYJU'S4 rounds · ₹4-8 LPADelhivery4 rounds · ₹10-20 LPAUnacademy5 rounds · ₹12-18 LPAJuspay5 roundsLenskart5 rounds

India: IT services and analytics

TCS4 rounds · ₹3.4-3.6 LPAInfosys3 rounds · ₹3.6-4.5 LPAWipro3 rounds · ₹4-4.5 LPAHCL3 rounds · ₹4-4.5 LPATech Mahindra6 rounds · ₹3.5-4.5 LPACognizant4 rounds · ₹4-4.5 LPACapgemini4 roundsThoughtworks4 rounds · ₹10-18 LPAAmdocs4 rounds · ₹5-7 LPACGI5 rounds · ₹4.5-7 LPACoforge4 rounds · ₹4.5-7 LPADXC Technology4 rounds · ₹4-4.5 LPAEPAM6 rounds · ₹8-14 LPAGenpact4 rounds · ₹3-4.5 LPAGlobalLogic4 rounds · ₹5-9 LPAGlobant3 rounds · ₹7-12 LPAHexaware6 rounds · ₹4 LPALTTS3 rounds · ₹4-4.5 LPAMindtree3 rounds · ₹4.0-4.5 LPAmPhasis5 rounds · ₹4-5 LPANagarro4 rounds · ₹6-10 LPANTT Data4 rounds · ₹4-5.5 LPAPersistent Systems4 rounds · ₹5-8 LPAPublicis Sapient3 rounds · ₹8-12 LPAVirtusa4 rounds · ₹4-5.5 LPAZensar4 rounds · ₹4-6.5 LPABirlasoft4 rounds · ₹4-6.5 LPAEXL6 rounds · ₹5-9 LPAFractal Analytics5 rounds · ₹8-14 LPAMuSigma6 rounds · ₹6-9 LPATiger Analytics4 rounds · ₹8-14 LPAWNS6 rounds · ₹5.6 LeClerx6 rounds · ₹2.8-3.1 L

India: banks, conglomerates and PSUs

SBI6 rounds · ₹21.97 LHDFC Bank4 rounds · ₹4-6 LPAICICI Bank4 rounds · ₹6-8 LPAAxis Bank3 rounds · ₹5-10 LPABank of Baroda4 rounds · ₹4-8 LPACanara Bank5 rounds · ₹4-8 LPABajaj Finserv4 rounds · ₹8-12 LPAAirtel5 rounds · ₹6-12 LPAJio5 rounds · ₹6-14 LPAL&T4 rounds · ₹8-15 LPAReliance3 rounds · ₹7.5 LPAAdani4 rounds · ₹8-15 LPABHEL4 rounds · ₹6-10 LPAMahindra3 rounds · ₹8-14 LPAMaruti Suzuki4 rounds · ₹7-12 LPATata Motors4 rounds · ₹7-13 LPAISRO3 rounds · ₹8-12 LPADRDO6 rounds · ₹8-12 LPABARC3 rounds · ₹74,000/moBEL5 rounds · ₹10-14 LPANTPC4 rounds · ₹7.2-12 LPABPCL4 rounds · ₹12-16 LPAHPCL5 rounds · ₹17.7-18.1 LIOCL5 rounds · ₹12-17 LPAONGC4 rounds · ₹20-26 LPAcdac4 rounds · ₹6-12 LPA

Intuit

US and global tech · Mountain View, California · Updated Oct 31, 2026

Intuit interview process: OA, technical screen and Craft Demo

Intuit’s interview process for US Software Engineer 1 candidates is an online assessment (LeetCode-style problems plus SQL or Bash), a recruiter call, a technical screen with one LeetCode medium, and a 3-4 hour final block. That superday is the distinctive part: you add features to a code repository from user stories, with unit and end-to-end tests, then face an architecture or design round, AI questions and a behavioral round on Intuit’s values.

Intuit interview process

  1. Online assessmentNot published
  2. Recruiter call30-40 min
  3. Technical screenAbout 60-90 min
  4. Final interviews3-4 hours
Round Duration What it tests
Online assessment Not published DSA problems, plus SQL, Bash or web basics in some 2025 US reports
Recruiter call 30-40 min Background, location, start date, work authorization, sometimes a few technical questions
Technical screen About 60-90 min One LeetCode medium; interns reported a 1-hour object-oriented round on Karat instead
Final interviews 3-4 hours Live coding in a codebase with user stories and tests, architecture or system design, AI questions, behavioral on Intuit’s values

Intuit Software Engineer 1 and Craft Demo interview

Intuit posts US new grad roles as “Software Engineer 1”, which the postings call an early-career position, asking for a bachelor’s or master’s in computer science or a related field, or equivalent practical experience. A Mountain View posting lists a Bay Area base of $55.50-$75.00 an hour. Interns apply to summer postings such as Backend Engineering Intern or Full Stack Engineering Intern; the Summer 2026 backend posting wanted students graduating in December 2026 or later. Intuit’s entry-level careers page also names an Accelerator Program as one route from intern to full-time.

The Intuit online assessment in US reports is broader than plain DSA. A November 2025 new grad had Bash and SQL questions alongside LeetCode-style problems, and a May 2025 Mountain View intern had data structures, algorithms and web development basics. Interns then had a 1-hour object-oriented round on Karat, debugging a class and adding methods, and a short behavioral interview on Intuit’s values.

For full-time candidates, the Intuit interview process ends in a long block of build-style interviews. A Mountain View software engineer who accepted an offer in September 2025 had a LeetCode medium screen, then a 4-hour superday: live coding in a repository with user stories, end-to-end and unit tests; a round on AWS, Jenkins and architecture; an AI round; and a behavioral round. A June 2025 New York candidate had a 90-minute pre-screen with a coding problem and AI questions, then a 3-hour onsite with a mock CRUD project, a design question on how to build Airbnb, and behavioral questions. At SDE-2 and above this becomes the Craft Demo, where you extend a codebase shared a day or two before the onsite.

The Software Engineer 1 postings do not mention visa sponsorship, so ask your recruiter before the final interviews.

Intuit senior and staff interviews

Experienced loops center on the build round. A senior software engineer in Mountain View who accepted an offer (Taro, January 2025) had a DSA tech screen, then a full-day onsite that opened with solving a full project in 90 minutes, followed by discussion rounds on scaling and operating costs. A staff candidate in Mountain View (August 2025, no offer) faced a three-person “craft panel” built around debugging a repository shared in advance, and advised running the project locally first, checking the output is correct (for example, whether the UI shows the right key-value pairs) and practicing breaking and fixing it.

Intuit’s US ladder runs Software Engineer 1, Software Engineer 2, Senior, Staff, Senior Staff, then Principal and Architect. Levels.fyi US medians (October 2026) are about $157,000 total pay at Software Engineer 1, $194,000 at Software Engineer 2 and $264,000 at Senior.

Intuit interview questions with answers

Q: Design a data structure supporting insert, delete, and getRandom in O(1).

Combine a dynamic array with a hash map from value to that value’s index in the array. Insert appends to the array and records the index in the map. getRandom picks a uniformly random index into the array, which is O(1) precisely because the array is dense with no holes. The trick is delete: instead of removing from the middle and shifting, look up the index of the target, swap in the last element of the array, update that moved element’s index in the map, then pop the last slot and erase the target from the map. All three operations are O(1) average and the structure uses O(n) space. The follow-up variant that allows duplicates replaces the map value with a set of indices per value.

Q: Given a binary tree and a list of values to delete, return the remaining forest.

Do a post-order traversal so children are processed before their parent, carrying the deletion values in a hash set for O(1) membership checks. At each node, recurse left and right first, then check whether the node itself is to be deleted: if it is, add its surviving children to the result list as new roots and return null to its parent so the parent unlinks it; if it is not, return the node unchanged. After the traversal, add the original root to the result only if it was not itself deleted. This is O(n) time and O(h) space for the recursion stack. Post-order matters because you must know whether a child survived before you can decide whether it becomes a new root.

Q: Implement decode string - for example, 3[a2[c]] returns accaccacc.

Use two stacks, one for repeat counts and one for partial strings, walking the input once. On a digit, accumulate the full multi-digit number. On an opening bracket, push the current count and the current partial string, then reset both. On a closing bracket, pop the count and the previous string, and set the current string to the previous string plus the current string repeated count times. On a letter, append it to the current string. This runs in O(total output length) time and O(depth) stack space. The two details interviewers probe are multi-digit numbers such as 12[ab], and nested brackets, both of which the two-stack approach handles naturally.

Q: What is the difference between compile-time and runtime polymorphism?

Compile-time polymorphism, also called static binding, is method overloading and operator overloading: several methods share a name but differ in their parameter lists, and the compiler picks one from the declared argument types. Runtime polymorphism, or dynamic binding, is method overriding: a subclass redefines a parent method with the same signature, and the decision of which implementation runs is deferred to run time based on the object’s actual type, dispatched through a vtable in C++ or by the JVM in Java. The practical consequence Intuit interviewers look for is extensibility - runtime polymorphism lets you add a new subclass without touching the calling code, whereas overloading is only a convenience for the caller. Note that in Java, static, private, and final methods are bound at compile time and therefore cannot be overridden.

Q: Explain normalization, and when would you deliberately denormalize?

Normalization decomposes tables so each fact is stored exactly once: 1NF requires atomic columns, 2NF removes partial dependencies on part of a composite key, and 3NF removes transitive dependencies between non-key columns. The payoff is that an update touches one row, so update, insert, and delete anomalies disappear. You denormalize when read performance under a known access pattern matters more than write simplicity - for example, storing a precomputed comment_count on a post rather than running a COUNT join on every page load, or duplicating a product name into an order-line row so historical orders do not change when the catalogue does. The cost is that you now own the consistency: every write path must update both copies, usually via a transaction, a trigger, or an asynchronous job that you must then monitor for drift.

Q: What is the difference between a mutex and a semaphore?

A mutex is a locking mechanism with ownership: exactly one thread holds it at a time, and only the thread that locked it may unlock it, which makes it the right tool for guarding a critical section. A semaphore is a signalling mechanism holding a counter: threads call wait to decrement (blocking at zero) and signal to increment, and any thread may signal, including one that never waited. A binary semaphore looks superficially like a mutex but lacks ownership, so it cannot support priority inheritance and is easier to misuse. Use a counting semaphore when you are limiting access to N interchangeable resources, such as a pool of ten database connections, and a mutex when you are protecting one shared piece of state.

Q: How would you design a notification service?

Start with an ingestion API that accepts a notification request and immediately writes it to a durable queue such as Kafka, so the caller is not blocked by delivery latency. Workers consume from that queue, look up the user’s channel preferences and quiet hours, apply rate limiting and deduplication (a hash of user, template, and time bucket held in Redis), and then fan out to channel-specific senders for push, email, and SMS. Each sender needs retries with exponential backoff and a dead-letter queue for permanent failures, since third-party providers fail transiently. Make delivery idempotent using a notification ID, because at-least-once queue semantics guarantee some messages get replayed - without that, users receive duplicates. For estimation, state your assumptions out loud: notifications per day divided by 86400 gives average writes per second, and you should size for a peak several times that.

Q: How would you find the shortest path through a grid of 0s and 1s?

Use BFS from the start cell, because BFS on an unweighted graph reaches every cell by the fewest moves the first time it arrives there - so the moment you dequeue the target, the distance recorded is optimal. Push the start into a queue with distance 0, mark it visited, and on each pop expand the four neighbours that are in bounds, are passable, and are unvisited. Time and space are both O(rows x cols) since each cell is enqueued at most once. DFS is the wrong choice here: it will find a path but not necessarily the shortest one. If the cells carry different traversal costs, upgrade to Dijkstra with a priority queue, and if a good heuristic exists such as Manhattan distance, A-star prunes the search further.

Q: Count robot paths in a binary grid (down/right only)?

Classic OA variant: from top-left to bottom-right through cells marked 1, moving only right or down. Use DFS with memoization or DP on (row,col) storing paths from that cell to the destination; add paths from (r+1,c) and (r,c+1) when those cells are valid. Base case: destination cell returns 1; invalid or 0-cell returns 0. Time O(rows × cols), space O(rows × cols) for memo. Clarify whether the start/end must be 1 and whether the grid can be empty.

Q: Largest n-digit number whose digits sum to s?

Greedy from the leftmost digit: for each position, pick the largest digit d such that the remaining positions can still reach sum s (remaining positions × 9 ≥ s - d). Avoid leading zero unless n=1 and s=0. If no valid digit exists at any step, return -1. Watch constraints up to n=10⁵ - the greedy check is O(1) per digit, so overall O(n). Reported in Glider mass-screening OAs.

Q: What does Intuit’s Craft Demo REST task usually look like?

Common pattern: Spring Boot (or similar) repo with H2/Postgres, implement a user story such as GET /players?isAdmin=true returning first+last names for admins and first names only for regular users; add JUnit tests; demonstrate in Postman; extend with pagination/sorting and role-based access in follow-ups. Panels grade requirement clarification, HTTP status codes, exception handling, and tests - Bengaluru SDE-2 reports cite rejections when error codes were sloppy even if happy path worked.

Q: How should you answer “how would you validate this feature with customers?”

Use Design for Delight language: state a customer problem statement, propose a cheap experiment (prototype, concierge test, A/B on a small cohort), define success metrics before building, and say what you’d pivot if results fail. Tie to TurboTax/QuickBooks-style users if relevant - small business owners, filers, not abstract “users.”

Intuit recruiter screen

A 30-40 minute call to confirm background, work authorization, location, start date, and pay expectations. In 2025 US new grad reports it came after the online assessment, and some recruiters asked a few technical questions. Since the Software Engineer 1 postings say nothing about sponsorship, settle it here.

Common questions

  • Walk me through your resume/current role
  • Why are you interested in Intuit right now?
  • What are your compensation and location preferences?
  • What’s your earliest start date, and do you need visa sponsorship?

Intuit online assessment

US reports describe a test that is broader than plain DSA: a November 2025 new grad had Bash and SQL questions alongside LeetCode-style problems, and a May 2025 Mountain View intern had data structures, algorithms and web development basics. Intuit does not publish the length. Interns then had a 1-hour object-oriented round on Karat, debugging a class and adding methods.

Common questions

  • Matrix traversal: find a path/target in a grid of 0s and 1s (robot paths down/right only - count ways)
  • Data structure design: O(1) insert, delete, and getRandom
  • Tree/graph problems: e.g. delete a node and return the remaining forest as an array
  • String/array problems in the “decode string” or “unique email addresses” family
  • SQL queries (joins, duplicates, group by) and basic shell commands

Intuit technical screen

US candidates usually get one screen before the final block: a LeetCode medium in the September 2025 Mountain View report, a “typical DSA question” for the January 2025 senior hire, and a 90-minute pre-screen with a coding problem and AI questions for a June 2025 New York candidate. India loops run one or two 30-60 minute technical rounds that add CS fundamentals and a project deep dive.

Common questions

  • OOPs: polymorphism (compile-time vs runtime), inheritance, and where you’ve used them
  • DBMS: ACID properties, indexing, normalization
  • Operating systems: deadlocks, process vs thread
  • Resume project deep-dive: architecture choices, the hardest bug, what you’d rebuild

Craft Demo and superday: Intuit’s build round

This is the round most candidate reports single out as unusual to Intuit. US new grads meet it as live coding in a repository inside a 3-4 hour superday; senior and staff candidates get a named Craft Demo or “craft panel”, sometimes as a 90-minute full project or as debugging a repository shared in advance. In the classic format, roughly 24-48 hours before the interview, you’re emailed access to a small GitHub repository with a partially-built application. In the ~90-minute session itself, 2-4 interviewers watch you implement one or two new user stories live inside that existing codebase - not a fresh whiteboard problem. The bar isn’t just “does it run”: interviewers are explicitly watching for test coverage, error handling, and whether you narrate your reasoning as you extend someone else’s code, since that’s closer to day-one engineering work than a LeetCode round.

Common questions

  • Implement a new feature/user story inside the provided repo, matching existing code style
  • Add unit tests and handle edge cases for the feature you just wrote
  • Explain why you structured the change the way you did, and what you’d refactor with more time
  • Follow-up questions tied to Design for Delight: how would you validate this feature actually solves the user’s problem?

Design for Delight and Intuit’s operating values

Intuit’s own innovation methodology - Design for Delight (D4D) - shows up as an evaluation lens in the Craft Demo and behavioral rounds, not just as company trivia. Its three principles are Deep Customer Empathy (understand the real problem before proposing a fix), Go Broad to Go Narrow (consider more than one option before committing), and Rapid Experimentation (test cheaply before building the whole thing). Layered on top are Intuit’s five operating values: Integrity without Compromise, Courage, Customer Obsession, Stronger Together, and We Care and Give Back. Interviewers use both as a shared vocabulary, so naming which principle or value a story maps to - briefly, not as a buzzword drop - tends to land better than a generic answer.

Common questions

  • Tell me about a time you validated an idea with real users before building it (Deep Customer Empathy / Rapid Experimentation)
  • Describe a time you considered multiple approaches before picking one (Go Broad to Go Narrow)
  • Tell me about a time you did the right thing even when it was inconvenient (Integrity without Compromise)
  • Why Intuit, specifically, over other fintech/SaaS companies?

Intuit system design round

A 45-60 minute round, standard from Software Engineer 2 up, focused on a concrete, scoped system rather than an open-ended “design Google” prompt. Interviewers probe estimation, trade-offs, and failure modes as much as the final diagram. New grads get a lighter version inside the superday: AWS, Jenkins and architecture questions in the September 2025 Mountain View loop, and “how would you build Airbnb” in the June 2025 New York onsite. The January 2025 senior hire was asked about scaling and operating costs.

Common questions

  • Design a photo/file storage service - upload, download, sharing at scale
  • Design a notification or alerting service
  • Design a roles-and-permissions system for a multi-tenant product
  • How would you estimate load and storage for the system you just designed?

Intuit behavioral and hiring manager round

In US superdays this is one round of the final block, after the build, design and AI rounds; experienced loops add a hiring manager conversation on fit and scope. It checks your stories against Intuit’s values and Design for Delight, plus logistics: location and compensation band.

Common questions

  • Tell me about a time you advocated for the customer even when it meant pushing back internally
  • Describe a decision you made by relying on data rather than intuition - what was the outcome?
  • Are you willing to relocate, and when can you start?
  • Do you have any questions for us?

STAR sample answers mapped to Intuit’s values are on the Intuit behavioral interview questions page.

Who does well in the Intuit loop

Good fit: You solve LeetCode mediums under a timer, write SQL without looking up joins, and can open an unfamiliar repository, find where a feature belongs, and add it with unit tests in under 90 minutes. You have a considered answer on how you use AI coding tools, since US superdays now include an AI round.

Harder path: You only practiced isolated problems and have never extended someone else’s codebase; you skip tests or error handling in the build round; your “Why Intuit?” never mentions TurboTax, QuickBooks, Credit Karma or Mailchimp customers.

What interviewers score

Stage Strong signal Weak signal
Online coding Medium DSA under timer with tests Untimed grind; no complexity talk
Build / craft demo Working feature + trade-offs + tests Buzzword design without bottlenecks
Technical deep dive Defend concurrency, edge cases, metrics Cannot explain your own submission
HR / values Design for Delight + customer-impact STAR Generic fintech praise with no customer story

Intuit weighs customer outcome and craft. Financial correctness, idempotency, and seasonal load show up in design talks more than social-feed templates.

Red flags that kill Intuit offers

  • Build challenge code you cannot defend in the deep-dive
  • Ignoring customer impact in behavioral stories
  • System design without consistency/idempotency for money-adjacent flows
  • “Why Intuit?” that never mentions TurboTax/QuickBooks/customer problems
  • Zero questions about craft expectations or team rituals

How to prepare for Intuit interviews: a four-week plan

A four-week plan for after you apply. Shorten it if your OA link arrives sooner.

  1. Week 1: One timed LeetCode medium a day from strings, hash maps, matrices and design-a-data-structure problems, plus 20 SQL queries (joins, group by, window functions) and basic shell commands, since US OA reports include SQL and Bash.
  2. Week 2: Practice building, not just solving: clone a small CRUD app, then add a feature from a one-line user story with unit tests and error handling in under 90 minutes. Do this three times.
  3. Week 3: Prepare the design and AI questions: one product design such as a booking site or tax-filing flow at a whiteboard level, and a clear answer on how you use AI coding tools and check their output.
  4. Week 4: Write STAR stories for customer impact, a decision made with data and a disagreement, using Intuit’s Design for Delight ideas (deep customer empathy, go broad to go narrow, rapid experiments). Run one mock final of 3-4 hours.

10-day version: Days 1-3 timed mediums and SQL, days 4-6 build a feature with tests in an existing repo, days 7-8 one design question and AI talking points, days 9-10 STAR stories and one full mock.

Intuit US compensation

A Mountain View Software Engineer 1 posting, which Intuit labels early-career, lists an expected Bay Area base pay range of $55.50-$75.00 an hour. For a full-time year of 2,080 hours that is about $115,000-$156,000. Bonus and stock are not included in that range, and other US locations have their own ranges. Levels.fyi’s US medians (October 2026), which include stock and bonus, are about $157,000 total at Software Engineer 1 and $194,000 at Software Engineer 2.

Intuit India: Glider online test, Bengaluru hiring and pay

Intuit Glider test and India hiring

In India, the Intuit online test is usually on Glider, often 4 coding problems in about 90 minutes or MCQs on Java, OOP and SQL with a short coding section, and you cannot return to an earlier question. Campus notices commonly list 7.5+ CGPA or 75%+ with no active backlogs, though Intuit does not publish one rule. India new grad loops then run one or two technical rounds on DSA, OOP, DBMS and OS and close with an HR or hiring manager round, with no Craft Demo in most reports.

Intuit online assessment in India: quick answers

Question Answer
Which platform is it on? Glider (Glider.ai) in most candidate reports, including a 2025 Bengaluru SDE-1 write-up. A 2021 off-campus SDE-1 candidate took it on HackerEarth.
How many questions and how long? Reports vary. One format is 4 coding problems (one easy, two medium, one hard) in about 90 minutes. Others pair 5-10 MCQs with a coding section capped at 30 minutes. A November 2025 SDE-1 test had two DSA problems and one SQL problem; a September 2025 intern test had five DSA problems.
What do the MCQs cover? Java, OOP, design patterns and SQL, with each MCQ timed separately (30-90 seconds in one report). 2025 mass-screening reports also mention static vs instance methods, factory patterns and JSON or API basics.
Can I go back to a question? Usually no. Candidates report that each question has a fixed time limit and you cannot return to an earlier question, so do not skip expecting to come back.
Does it have negative marking? No public candidate report mentions negative marking, and Intuit does not publish a marking scheme.
Is there a sectional cutoff? Not published. Reports say fully passing the easier coding problems counts for more than a partial attempt at the hardest one.
How much is the cutoff? No test cutoff is published; shortlists are relative to the batch. Intuit does not publish a CGPA rule for India hiring, so follow your campus notice or the job listing.
Is the Craft Demo part of the fresher process? Usually not. The Craft Demo is reported mainly on SDE-2 and senior loops; fresher and intern loops are the online test, technical rounds and an HR or recruiter round.

Intuit online assessment in India: Glider format

A 60-90 minute timed test, usually on the Glider platform: typically 2-4 coding problems spanning easy to hard difficulty, often paired with MCQs on OOP, SQL, and JSON/API basics. Mass-screening reports (2025) describe a balanced mix - static vs instance methods, encapsulation, factory patterns, SQL for duplicate salary rows, plus coding such as largest n-digit number with digit sum s and minimum operations to transform array A into B (+1, -1, copy). Candidates report that clean, fully-passing solutions on the easier problems weigh more than a partial attempt at the hardest one.

Intuit interview questions by level in India

These themes come from candidate reports on Glassdoor, LeetCode Discuss, Naukri Code360 and the Roundz SDE-1 write-up for Intuit Bengaluru.

Level Reported questions and topics
Intern Arrays and linked lists plus CS fundamentals across two technical rounds (September 2025); C++, DBMS, BSTs and the Sieve of Eratosthenes (2024 report).
SDE-1 (new grad) Decode string, searching a sorted matrix, an O(1) insert-delete-getRandom structure, ACID properties, OOP and OS (2025 Roundz write-up); graph-heavy coding with DP and arrays (January 2024); a string-counting problem with Rabin-Karp and KMP follow-ups (2021). A March 2026 candidate was also asked how they use AI coding assistants and about code quality.
SDE-2 / senior The Craft Demo: implement one or two user stories live in a GitHub repo shared 24-48 hours earlier, with tests and error handling, then a system design round (file storage, notifications, roles and permissions).
Senior (OA) An experienced-hire India OA reported on LeetCode Discuss asked for a palindrome linked-list check.

Asked across every level: a deep project walk-through, edge cases and optimization on every coding answer, and a story that maps to Design for Delight (customer empathy or rapid experimentation).

Intuit India pay

Candidate-reported early-career packages for Intuit India often cite ₹30-40 LPA CTC (Software Engineer). For OA papers and coding drills, see Intuit on placementpapers.app.

Frequently asked questions about Intuit interviews

What is the Intuit interview process for new grads in the US?

New grads are hired as Software Engineer 1, which Intuit’s postings call an early-career role; a Mountain View posting lists a Bay Area base of $55.50-$75.00 an hour. 2025 US reports describe an online assessment with DSA plus SQL or Bash questions, a recruiter call, a technical screen with a LeetCode medium problem, and 3-4 hours of final interviews: live coding in a repository with user stories and tests, an architecture or design discussion, AI questions and a behavioral round on Intuit’s values.

What is the Intuit interview process for engineers?

Intuit’s engineering loop typically runs: 1. Recruiter screen (30-40 min) - background, motivation, logistics. 2. Online Assessment (60-90 min on the Glider platform) - 2-4 DSA problems. 3. One or two Technical interviews (30-60 min each) - coding, OOPs/CS fundamentals, and a project deep-dive. 4. Craft Demo (around 90 min, common on SDE-2+ and senior loops) - live coding on a codebase shared 24-48 hours in advance. 5. System design (SDE-2+) and a closing Hiring Manager/HR conversation (20-30 min). Community-reported timelines put the full process at roughly 3-6 weeks.

What is Intuit’s Craft Demo round?

The Craft Demo is Intuit’s most distinctive round, reported mainly on SDE-2 and senior loops. Candidates get access to a small GitHub repository 24-48 hours ahead of time and are asked to implement 1-2 new user stories live in front of 2-4 interviewers, roughly 90 minutes total. It’s scored on working code, but also on test coverage, error handling, and how clearly you explain trade-offs while you build - closer to a real code review than a whiteboard problem.

What is Design for Delight (D4D) and why does it come up in interviews?

Design for Delight is Intuit’s internal innovation framework, built on three principles: Deep Customer Empathy, Go Broad to Go Narrow, and Rapid Experimentation. Interviewers - especially in the Craft Demo and behavioral rounds - often use it as a lens: they want to hear how you understood a user’s real problem, considered more than one option, and tested an idea cheaply before committing, not just that you shipped something.

What questions are asked in Intuit interviews?

Coding rounds lean on arrays/strings, matrix traversal, tree/graph problems (e.g. delete a node and return the remaining forest), and data-structure design questions (O(1) insert/delete/getRandom). CS fundamentals cover OOPs, DBMS (ACID, indexing), and operating systems basics. System design rounds (mostly SDE-2+) ask for things like a photo-storage or notification service. Behavioral and Craft Demo rounds probe Intuit’s five operating values and its Design for Delight framework.

How many rounds are there in the Intuit interview?

Most community-reported loops describe 4-6 stages: recruiter screen, Online Assessment, one or two technical interviews, an optional Craft Demo (common at SDE-2+), and a closing hiring-manager/HR round. Exact composition varies by level and team, so treat this as a range, not a fixed script.

How should I prepare for Intuit interviews?

Drill medium DSA (arrays, trees, graphs, and O(1) data-structure design), revise OOPs/DBMS/OS fundamentals, and practice reading and extending someone else’s codebase quickly and cleanly - that’s exactly what the Craft Demo tests. For behavioral rounds, prepare STAR stories mapped to Intuit’s operating values (Customer Obsession, Courage, Integrity without Compromise) and be ready to describe a time you validated an idea with real users before building it (Design for Delight).

What is Intuit’s craft / build demonstration?

It is a practical round where you implement features in a real-ish codebase or a timed Java build challenge, then face a deep dive on concurrency, tests, and trade-offs. Treat it like production craft, not a LeetCode paste.

Does Intuit hire at TCS/Infosys-style campus scale?

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

Which platform is the Intuit online assessment on?

Glider (Glider.ai) in most candidate reports, including 2025 Bengaluru SDE-1 reports; one 2021 off-campus candidate took it on HackerEarth. Formats vary from 4 coding problems in about 90 minutes to 5-10 timed MCQs plus a 30-minute coding section.

Does the Intuit online assessment have negative marking?

No public candidate report mentions negative marking, and Intuit does not publish a marking scheme. The test is usually on Glider with timed MCQs on Java, OOP, design patterns and SQL plus coding problems, and candidates report you cannot go back to an earlier question once you move on.

Intuit new grad loop vs experienced loop

The two loops share a name but not a shape. US Software Engineer 1 candidates take the online assessment, a recruiter call and a technical screen, then a 3-4 hour superday that already includes live coding in a codebase with user stories and tests, plus architecture, AI and behavioral rounds.

Experienced candidates (Software Engineer 2 and above) usually skip the online assessment, and the loop centers on the Craft Demo, where you build or debug a real codebase live, plus system design on scaling and operating costs and a hiring manager round on Intuit’s values. India new grad loops are the exception: no Craft Demo in most reports. Check your invite to see which loop you are in before you prepare.

Sources

OA quick answers and level-wise questions draw on Glassdoor candidate reviews for Intuit Bengaluru (2024-2026), LeetCode Discuss Intuit SDE-1 and SSE posts, Naukri Code360 Intuit interview experiences and the Roundz Intuit SDE-1 write-up. The US section draws on a Mountain View Software Engineer 1 posting, Intuit’s entry-level careers page, and 2025 US reports on Taro, including a November 2025 new grad report a September 2025 Mountain View offer, a January 2025 Mountain View senior offer and an August 2025 Mountain View staff report, plus Levels.fyi Intuit software engineer pay by level (October 2026).

Popular

↑↓ navigate↵ open