They answer different questions, so they do not compete. Quantitative data tells you what is happening and how big it is; qualitative tells you why, and generates the hypothesis worth measuring. Use interviews to find the problem and the language, use the data to size it and decide, then go back to users whenever you see a number you cannot explain.
Why interviewers ask this
Interviewers are checking that you are neither a data fundamentalist nor someone who builds on the loudest customer. The best answers show a loop between the two, with a rule for when each one wins. They also listen for the classic trap: a metric that looks like friction but is actually a user leaving to do something else, which only a conversation reveals.
How to structure your answer
- Frame them as answering different questions, not competing.
- Use qualitative to generate, quantitative to size and decide.
- State your rule: an unexplained number becomes a research task.
- Give an example where the data alone would have misled you.
Example answer
I treat them as answering different questions rather than competing. The data tells me what is happening and how big it is. It cannot tell me why, and it definitely cannot tell me about the thing nobody is doing because it is not possible yet. So my loop is that interviews generate the hypothesis and the language, and the analytics size it and decide it. The rule I use is that any number I cannot explain becomes a research task. We once had a drop off on a settings step that looked like friction, so the obvious fix was to shorten the form. Five conversations later it turned out people were leaving to find an API key in another tool and coming back the next day. Shortening the form would have done nothing. We added a skip and remind option instead and completion moved properly. Neither source on its own would have got us there.
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 worksFollow-up questions to expect
- How do you stop one loud customer driving the roadmap?
- How many users do you need before you act on a qualitative finding?
- What do you do when the interviews and the data flatly contradict each other?
Related product manager 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