UX Designer Interview Question

How do you combine qualitative and quantitative data when they disagree?

What the interviewer is probing, how to structure your answer, and a spoken example you can adapt.

Quick answer

Treat them as answering different questions: analytics tells you what is happening and at what scale, qualitative work tells you why. When they disagree, first check the measurement (event definitions, segments, date ranges) because instrumentation is wrong more often than people expect. Then look for a segment effect, since an average can hide two groups behaving in opposite directions.

Why interviewers ask this

Product design in 2026 is a data-literate job, and teams need designers who can read a funnel without being intimidated or over-impressed by it. The interviewer wants to see that you do not dismiss numbers when they contradict your interviews, or dismiss interviews when a dashboard looks tidy. Mentioning instrumentation errors and segment effects signals you have worked with product analytics rather than just seen screenshots.

How to structure your answer

  • Assign each source the question it can actually answer.
  • Audit the measurement before you trust or reject the number.
  • Segment the data to check for opposite behaviors inside an average.
  • Use qualitative work to generate the hypothesis the data then tests.

Example answer

Spoken example, first person

My first move is not to pick a winner, it is to check whether we are even measuring what we think we are. I have lost count of the times a scary drop turned out to be an event that stopped firing after a release, or a funnel that counted a step twice. So I go and read the event definitions with an analyst or an engineer before I argue with anyone. If the measurement holds, I segment. Averages lie constantly. On one project the completion rate looked flat after a change, and when we split by device it turned out desktop had gone up meaningfully and mobile had gone down by almost exactly as much. Those are two different stories and the average had erased both. The interviews then explained the mobile side: the primary action sat below the fold on smaller screens with the keyboard open. That is the pattern generally. The numbers tell me where to point the camera, the sessions tell me what is happening in the frame, and neither one alone was enough to make the call.

Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.

See how it works

Follow-up questions to expect

  • How do you check whether an event is instrumented correctly?
  • How many users does a qualitative finding need before you act on it?
  • Tell me about a time the data proved you wrong.

Related ux designer questions

Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.

Predict my questions

Rehearse the hard questions before they are asked

Practise with a live copilot, then walk in ready. A $29 Session Pass gets you through the interview with no subscription and no lock-in.

Get GhostPilot