Product design question
How would you design a feature for cryptocurrency tax reporting on TurboTax?
- Intuit
- Product design
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests product design for a regulated, high-anxiety financial workflow: can you handle data complexity (multiple exchanges, wallets) and trust in a tax product.
How to approach it
- Define the user: a TurboTax filer who traded or held crypto across one or more exchanges and wallets and needs accurate capital gains reporting (Form 8949/Schedule D in the US).
- Identify the core pain points: manually reconciling transactions across exchanges, calculating cost basis (FIFO/LIFO), and handling non-trade events like staking rewards or airdrops.
- Prioritize: automated import from major exchanges (Coinbase, Binance.US) and wallets via API or CSV upload as the highest-leverage feature, since manual entry is the biggest drop-off point.
- Design the solution: an import wizard that pulls transaction history, auto-classifies events (trade, income, transfer), flags ambiguous transactions for user review, and shows a running gain/loss summary before filing.
- Address trust: show the user exactly how each number was calculated and let them override cost-basis method, since tax filers are risk-averse about errors.
- Define the success metric as percentage of crypto filers who complete filing without contacting support, plus reduction in manual transaction entries.
What a strong answer includes
- Names the real pain point precisely: cost-basis tracking across exchanges is what tax software historically got wrong, not the tax calculation itself.
- Proposes integration partnerships with exchanges or aggregators (like CoinTracker-style data feeds) rather than building every exchange connector from scratch.
- Includes an edge case: transfers between a user's own wallets should not be taxed as sales, and the design should auto-detect and flag these.
- Sets an illustrative target: reduce average crypto-filer time-to-complete from an assumed 45 minutes to under 15.
Common mistakes
- Designing a generic 'add transaction' form without addressing multi-exchange reconciliation, which is the actual hard problem.
- Ignoring non-trade taxable events like staking, mining, or airdrops.
- No mention of accuracy or trust signals in a domain where a mistake has real financial and legal cost.
Likely follow-up questions
- How would you handle a transaction history with missing cost-basis data from a defunct exchange?
- How would you prioritize which exchanges to support first?
- What would you do if the IRS changed crypto tax rules mid-filing-season?
More product design questions
- How can you improve Google Meet for the elderly?Intuit · Product design · Medium
- You are a Product Manager for the health ministry of India. Design a product for the efficient availability check and distribution of covid resources.Intuit · Product design · Hard
- Design a TV for a car.Google · Product design · Hard
- Design a refrigerator for the blind.Google · Product design · Hard
- Redesign Twitter for eCommerce.Shopify · Product design · Hard
- You are a PM at Flipkart. The company has decided to increase the userbase of age >60 years on the platform. What will you do?Flipkart · Product design · Hard
More questions from Intuit
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop