Product designer domain knowledge interview questions

As asked

How do you explain the difference between UX and UI design to someone who is not a designer, and how do they interact in practice on a product team?

Sample answer outline

A strong answer goes beyond the cliche of 'UX is how it works, UI is how it looks' and describes UX as encompassing the entire user journey (research, information architecture, interaction flows, content strategy, usability) while UI covers the visual execution (color, typography, component design, visual hierarchy). On a product team, they interact constantly: good visual design reinforces UX intent (color draws attention to primary actions), and bad UI can undermine a well-structured UX (a confusing visual hierarchy makes a logical flow hard to parse). Bonus for noting that many product designers do both.

Expect these follow-ups

• When is it a mistake to separate UX and UI into different roles on a team?
• How does the UX role differ between a startup and a large company?

As asked

Explain Fitts's Law and give me two concrete examples of how it should influence the placement and sizing of interactive elements in a mobile navigation pattern.

Sample answer outline

A strong answer correctly states Fitts's Law: the time to reach a target is a function of the distance to the target and the size of the target. For mobile navigation: primary actions should be in the thumb zone (bottom of the screen, reachable without shifting grip), larger hit areas for frequent destinations reduce interaction time, and corner targets are effective because the screen edge acts as a hard boundary that stops the thumb. Bonus for distinguishing the law's implication for one-handed versus two-handed mobile use.

Expect these follow-ups

• How does Fitts's Law interact with the desire to make a design look minimal and clean?
• When is Fitts's Law less relevant or actively misleading as a design rule?

As asked

Explain Hick's Law, where it applies in interface design, and where it is misapplied or oversimplified.

Sample answer outline

A strong answer correctly states that decision time increases logarithmically with the number of options. Applications include limiting the number of visible navigation items, avoiding overloaded dropdowns, and prioritizing a single primary CTA per page. Misapplications include removing useful options in the name of simplicity when users are experienced and benefit from seeing all options, or applying Hick's Law to choices that are categorically different (it was derived from similar-looking stimuli, not complex decisions). Bonus for noting it is often cited to justify minimal design when the real problem is poor information architecture.

Expect these follow-ups

• If Hick's Law says fewer options is better, how do you design a product with a large feature set?
• What research would you do to find the right number of options for a specific interface?

As asked

Explain what a mental model is in the context of UX design and give me an example of a product that failed because it violated users' existing mental models.

Sample answer outline

A strong answer defines mental models as the internal representations users build about how a system works, often based on prior experience with analogous systems. A good example might be early file syncing apps that violated the folder mental model by introducing concepts like 'conflicts' that users had no prior frame for. The candidate should distinguish the designer's mental model (how the system actually works), the user's mental model (how they believe it works), and the system image (what the product communicates about itself). Good design aligns the system image with the user's expected mental model.

Expect these follow-ups

• How do you discover users' mental models before you start designing?
• When is it appropriate to break a user's existing mental model versus accommodating it?

As asked

Explain the difference between an affordance and a signifier as Don Norman defines them, and give me an example of a UI element that has a misleading signifier.

Sample answer outline

A strong answer correctly distinguishes: an affordance is a relationship between a property of an object and an agent that determines how the object could be used (a button can be pressed), while a signifier is a signal that communicates where the action should take place and what kind of action (the button's raised appearance and label signals it can be clicked). A misleading signifier example: underlined text that looks like a link but is just styling, or a card with a hover shadow that implies clickability but is not interactive. Bonus for citing Norman's The Design of Everyday Things.

Expect these follow-ups

• How has the web trained users to expect certain signifiers that differ from physical world affordances?
• Give me an example of a false affordance in a widely used product.

As asked

Explain what WCAG is, the difference between A, AA, and AAA conformance levels, and what the new or changed success criteria in WCAG 2.2 were most relevant for product designers.

Sample answer outline

A strong answer identifies WCAG as the Web Content Accessibility Guidelines from the W3C, organized around four principles: Perceivable, Operable, Understandable, Robust. AA is the legal standard in most jurisdictions. For WCAG 2.2, new criteria most relevant to designers include 2.4.11 and 2.4.12 (Focus Appearance, requiring visible focus indicators with minimum contrast and area), 2.5.7 (dragging movements must have pointer alternatives), and 2.5.8 (target size minimum 24x24 CSS pixels at AA). SC 3.3.8 (Accessible Authentication, Minimum, AA) reduces cognitive barriers in login flows by prohibiting memory or transcription tasks without an alternative. SC 4.1.3 (status messages) was added in WCAG 2.1 and is now more widely enforced. Bonus for noting that 2.5.3 (Label in Name) was also introduced in WCAG 2.1 at Level A, not in 2.2.

Expect these follow-ups

• Which WCAG 2.2 criteria are most commonly overlooked by design teams?
• What is ARIA and when should a designer specify ARIA attributes in their specs?

As asked

Explain user-centered design as a philosophy, name its core principles, and give me an honest critique of where it falls short as a design framework.

Sample answer outline

A strong answer covers the ISO 9241-210 definition: iterative design grounded in understanding context of use, specifying user and organizational requirements, producing designs that meet those requirements, and evaluating against requirements. Critiques include: UCD can be slow and resource-intensive in competitive environments, it privileges the majority user and can exclude edge cases, users cannot always articulate future needs (hence 'if I had asked people what they wanted they would have said faster horses'), and UCD scoped to current users can miss potential new user segments. Bonus for contrasting with participatory design and speculative design.

Expect these follow-ups

• How do you balance listening to existing users with designing for users who do not yet use your product?
• When does UCD create the wrong kind of conservatism in design?

As asked

Explain the double diamond model from the UK Design Council, name the four phases, and tell me where in practice teams most often skip or compress stages and what the consequences are.

Sample answer outline

A strong answer correctly names Discover, Define, Develop, Deliver and explains the two diamonds: the first diverges (broad research) then converges (defining the problem), the second diverges (ideating solutions) then converges (delivering a specific solution). The most commonly skipped phase is Define: teams rush from research data to solution without articulating a clear problem statement, resulting in designs that solve the wrong problem or solve multiple vague problems at once. Compressing Discover leads to solutions built on assumptions. Bonus for noting the model is iterative, not linear.

Expect these follow-ups

• How does the double diamond map to a modern agile sprint cycle?
• What artifacts come out of the Define phase and why do they matter?

As asked

What are the most common biases introduced by poorly written survey questions, and how do you avoid them when designing a user survey?

Sample answer outline

Strong answers name specific biases: leading questions ('How much did you enjoy X?' assumes enjoyment), double-barreled questions ('Was the checkout fast and easy?' conflates two dimensions), acquiescence bias (respondents agree with positively framed statements), social desirability bias (respondents give answers they think the researcher wants), and question order effects (earlier questions prime responses to later ones). Fixes include neutral framing, separating questions that cover two topics, using forced choice or slider scales for some questions, and randomizing question order. Bonus for discussing sample size and sampling strategy.

Expect these follow-ups

• When is a survey the right research method and when is it the wrong one?
• What Likert scale format do you prefer and why?

As asked

Jakob Nielsen defined five quality components of usability. Name them, explain what each means, and describe how you would measure each one in a study.

Sample answer outline

A strong answer names: learnability (how easy is it for users to accomplish basic tasks the first time?), efficiency (how quickly can experienced users accomplish tasks?), memorability (when users return after a break, how easily do they re-establish proficiency?), errors (how many errors do users make, how severe are they, and how easily can they recover?), and satisfaction (how pleasant is the design to use?). Each maps to a different measurement approach: task completion rate and time-on-task for learnability and efficiency, error rate and recovery time for errors, SUS or NPS for satisfaction, and longitudinal studies for memorability.

Expect these follow-ups

• Which dimension of usability is most commonly ignored by teams under time pressure?
• How does the relative importance of these dimensions change between a consumer app and a professional tool used eight hours a day?

As asked

Explain the Kano model and walk me through how you would use it to prioritize a backlog of potential features for a consumer app.

Sample answer outline

A strong answer names the three main categories: basic needs (must-haves that cause dissatisfaction when absent but do not delight when present), performance needs (more is better, linearly improving satisfaction), and delighters (unexpected features that create delight but are not missed when absent). Application: run a Kano survey asking both a functional form ('If this feature is present, how do you feel?') and a dysfunctional form ('If this feature is absent, how do you feel?'). Classify responses into categories and prioritize by ensuring all basic needs are met first, then investing in performance needs with the highest ROI, then adding selective delighters.

Expect these follow-ups

• What happens to a delighter feature over time as users come to expect it?
• How does Kano complement or conflict with MoSCoW prioritization?

As asked

Explain IDEO's three lenses of innovation and how you use them to evaluate a design concept before investing heavily in it.

Sample answer outline

A strong answer names desirability (do users actually want this?), feasibility (can we build it with current technology and resources?), and viability (does it make business sense?). The candidate should describe how they use these as an early filter: a desirable but not feasible idea needs a different technical approach, a feasible but not desirable idea needs more user research before investment, and a desirable and feasible but not viable idea needs a business model rethink. Bonus for noting that designers often over-index on desirability and skip viability.

Expect these follow-ups

• How do you assess viability without being a business analyst?
• What happens when a solution scores high on all three lenses but still fails in market?