Expect a mix of portfolio storytelling, product thinking, system literacy, and collaboration scenarios. Questions are designed to probe your thinking, not to trick you—show your process, trade-offs, and results.

Portfolio & Craft

These questions assess your end-to-end process, quality bar, and rationale.

• Walk us through a recent project end-to-end. What problem were you solving and how did you measure success?
• Show a flow you simplified. What did you remove and why?
• How did you design for error states and edge cases?
• Share a prototype that changed a stakeholder’s mind. What was the moment of clarity?
• Tell us about a design you would change in hindsight and why.

Product Thinking & Metrics

We probe how you connect design choices to outcomes.

• How would you improve first-time user activation for a tax product?
• Which metrics would you track post-launch for an onboarding redesign?
• Describe a time when data contradicted your intuition. What did you do?
• How do you prioritize when everything feels important?
• What trade-offs did you make to ship on time, and how did you mitigate risks?

Design Systems & Accessibility

We evaluate system literacy and inclusive design.

• Describe a contribution you made to a design system and the adoption results.
• When do you propose a net-new component vs. adapt an existing one?
• How do you structure tokens to support theming at scale?
• Walk through your accessibility checklist for a complex form.
• How have you handled a token change that caused regressions?

Collaboration & Leadership

We look for influence, clarity, and execution.

• Tell us about a difficult cross-functional alignment moment. How did you resolve it?
• How do you handle conflicting feedback from PM and engineering?
• Describe how you run design reviews for productive outcomes.
• Share a time you advocated for the customer in a high-stakes decision.
• How do you mentor or uplevel peers’ craft?

Process, Research, and Validation

We assess pragmatic research usage and iteration.

• Which research method did you choose for your last project and why?
• How do you structure a quick usability test to validate a risky assumption?
• What signals tell you a design is ready to ship vs. needs more iteration?
• How do you incorporate support tickets or analytics into your roadmap?
• Describe your approach when timelines compress but quality must hold.

Deep Dive into Evaluation Areas

Product Thinking & Problem Framing

Intuit cares deeply about how you identify the right problem before designing the solution. We will probe how you use data, research, and constraints to frame opportunities and define success metrics. Expect to show how you de-risk decisions and thread customer value to business outcomes.

Be ready to go over:

• Problem framing and hypotheses: How you clarify scope, users, jobs-to-be-done, and constraints.
• Prioritization and trade-offs: How you choose what to solve first and why.
• Impact and metrics: How you define success (conversion, task time, completion rate, NPS) and measure outcomes.
• Advanced concepts (less common): Experiment design, opportunity sizing, cost-of-delay, north star metrics vs. guardrail metrics.

Example questions or scenarios:

• "Walk us through a complex flow you simplified. How did you decide what to cut?"
• "How would you improve TurboTax’s first-time filer onboarding? What metrics would move?"
• "Tell us about a time research changed your roadmap. What did you do next?"

Interaction Design, Visual Craft, and Prototyping

You’ll be assessed on the quality of your interaction patterns, hierarchy, motion, and responsiveness across breakpoints. Expect to justify your choices and demonstrate how you prototype to learn quickly. Show how design decisions scale in real systems, not just one-off screens.

Be ready to go over:

• Information architecture and flows: Navigation, error states, edge cases.
• Component-level decisions: Inputs, tables, pagination, and data density.
• Prototyping: High/low fidelity, clickable prototypes, motion to convey state.
• Advanced concepts (less common): Complex states, progressive disclosure in regulated flows, microcopy design with content partners.

Example questions or scenarios:

• "Redesign the payment step to reduce abandonment—what patterns do you consider?"
• "Show a prototype that unblocked a decision. What did it prove or disprove?"
• "How do you handle error states for form-heavy tasks?"

Design Systems, Tokens, and Accessibility

With multiple product lines and surfaces, system thinking is essential. We evaluate how you leverage and evolve design systems (components, tokens, patterns) and ensure WCAG-compliant experiences. You’ll need to balance consistency with the realities of product constraints.

Be ready to go over:

• Component reuse vs. net-new: Criteria for proposing system changes.
• Design tokens and theming: How tokens support consistency and velocity.
• Accessibility: Color contrast, focus states, keyboard nav, screen reader semantics.
• Advanced concepts (less common): Figma plugin workflows, design-to-code synchronization, AI’s role in system governance.

Example questions or scenarios:

• "Describe a time you contributed to a design system. What adoption challenges did you solve?"
• "How would you handle a token update that risks visual regressions across products?"
• "Walk through your accessibility QA process for a new component."

Collaboration, Influence, and Execution

Design at Intuit is a team sport. We assess how you align with PM/engineering, communicate trade-offs, and drive outcomes through ambiguity. Bring examples showing constructive conflict, thoughtful compromises, and steady delivery.

Be ready to go over:

• Cross-functional rituals: How you design with engineering and PM in agile.
• Stakeholder management: Handling feedback, building consensus.
• Roadmapping and scoping: Sequencing MVP, V1, and iteration plans.
• Advanced concepts (less common): Running design office hours, community-building for system adoption, design quality gates.

Example questions or scenarios:

• "Tell us about a time you disagreed with engineering. How did you resolve it?"
• "How do you ensure design quality doesn’t degrade under tight timelines?"
• "Describe how you socialize a risky design decision to leadership."

Research, Validation, and Continuous Learning

We look for designers who close the loop with customers and data. You don’t need to be a full-time researcher, but you should know how to leverage research partners and run lightweight validation independently.

Be ready to go over:

• Methods: Usability testing, concept testing, surveys, analytics reviews.
• Insight to action: Turning findings into decisions and backlog changes.
• Post-launch iteration: Monitoring metrics, addressing regressions.
• Advanced concepts (less common): Triangulating qualitative and quantitative signals, inclusive research practices at scale.

Example questions or scenarios:

• "Share a study that directly changed your design. What did you ship afterward?"
• "How do you decide between building a quick prototype vs. running a deeper study?"
• "What post-launch metrics do you monitor and why?"