Product work at Intuit is about people who would rather not think about tax or bookkeeping at all. TurboTax guides them through filing, QuickBooks keeps the books of small businesses, and Credit Karma and Mailchimp serve personal finance and marketing. Prepare stories about watching customers do real tasks, easing fear of mistakes, serving both owners and their accountants, and reacting to a rule change late in the season. What to show here: time spent with customers and problems found at the source. Each question below has what the interviewer is checking, an answer frame and a sample spoken answer to adapt.
How Intuit hires, in its own words, and its questions for every job →
“I would start by talking to first-time filers to learn what exactly they fear. Often it is not the sums but not knowing what they have missed. So the product should ask only what applies to them, in everyday words, and say why each question matters. I would show progress clearly, so the task feels finite. Before filing, the product reviews the return and explains anything unusual, which answers the question of whether they did it right. At points where many people hesitate, I would make it easy to reach a human expert. I would measure completion and also how confident users say they feel.”
Weak answers add more help text everywhere, or design for the task and ignore the fear behind it.
“I would first learn why invoices are late. From talks with owners, I would expect a few causes: the customer forgot, paying was awkward, the invoice had a mistake, or the owner felt uneasy about chasing. Each needs a different answer. For forgetting, polite automatic reminders that the owner can edit. For awkward payment, a button on the invoice to settle it online. For uneasy owners, wording that sounds like them and not like a debt collector, because they want to keep the customer. I would start with reminders and the payment button, and measure the days from invoice to payment.”
Weak answers jump to one feature with no look at causes, or suggest harsh chasing that would harm the owner's customer relationships.
“For the customer, success means they finish the return and trust it. So I would measure the completion rate and the confidence rating of those who used the expert, against similar users who did not. For quality, I would track wait time, whether the question was settled in one session, and later corrections to the return. The option also has to work as a service, so I would watch expert time per session and demand at peak hours. If the same question comes up again and again, that tells me the product itself should be fixed, and I would count those as feedback.”
Weak answers measure only how many people used the option, or forget that expert time is limited.
“I would not treat it as one against the other, because they work on the same books. The owner enters data through the year and the accountant cleans and closes it. If the owner's side is too loose, the accountant pays for it later. If it is too strict, the owner stops using it. I would give each a view fitted to their job on the same data. For priorities, I would look first at the handover points where both lose time, such as transactions in the wrong category. I would test changes with real pairs of owner and accountant together.”
Weak answers pick one user and ignore the other, or add every accountant option to the owner's screen.
“At your company I visited a small bakery that used our billing product. In surveys, owners had asked for more reports. On the visit I saw the owner doing her books late at night on a phone, one hand holding papers. She never opened the reports. What slowed her was typing supplier bills by hand. I came back and argued for moving bill capture by photo ahead of the reports work. It was a hard case to make, since reports had more survey votes. We built it. The result was your result.”
Weak answers rely on surveys and requests alone, or describe a visit that confirmed everything they already thought.
“At your company we had a custom invoice designer that few customers used, but it caused many support tickets and slowed every change to invoices. I looked at usage and found that most of its users changed only the logo and the colours. I proposed replacing it with a few good templates with those two options. Before removing it, I wrote to the heavy users, explained why and offered to move their designs for them. A few were unhappy, and I spoke to them myself. The result was your result.”
Weak answers remove a feature with no warning, or keep everything for ever to avoid complaints.
“First I would get the facts from our tax and legal experts: what changed, who is affected and what the agency expects from people who already filed. Then I would split users into three groups. Those who have not filed need the product updated quickly and correctly. Those in progress need their return checked again, with a clear note on what changed. Those who already filed need plain guidance on whether to do anything, and help if an amendment is required. I would bring engineering, support and communications together daily until it is done. I would not send a message until the experts have approved every word.”
Weak answers send a quick message before the facts are confirmed, or forget the users who have already filed.
“I am drawn to problems that people avoid because they feel too hard, and money tasks are high on that list. Intuit's products take tax filing and bookkeeping, which most people dread, and make them doable without an expert. The customers are individuals and small business owners with little time and no room for mistakes. In my work on your project I learned that the best ideas came from sitting with customers while they did the task. I want to work where that habit is normal, and to learn how to make products that are simple on top and correct underneath.”
Weak answers talk about the growth of financial technology in general, and never about the customer.
No figures on this page: pay depends on the level, the city and the offer in front of you. When the offer comes, the free salary negotiation script helps with that part.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your live interview audio and screen are never stored. Your resume and notes are saved to your account so the app fills them in on any computer. It is hidden from screen share on every plan, including Free; only you can see it.