Tell me about a time you uncovered what a customer really needed by listening carefully.
Break down this behavioral question with a model STAR answer, the pitfalls that cost candidates points, and the follow-up questions worth rehearsing next.
A strong STAR example answer
A mid-size client sent us a detailed spec for a custom reporting dashboard loaded with metrics, and the easy money was to quote it and build. Something felt off, though — the spec read like a compromise document written to please everyone at once. So before quoting, I booked a call, ostensibly to review the spec, and spent most of it asking open questions: who will actually open this dashboard, and what decision does it feed?
The answer rewrote the deal. One person, their operations director, would use it regularly, and she checked three numbers every Monday morning to set staffing for the week. Everything else was there because assorted managers had been asked what they might like to see. Instead of the big custom build, I proposed an automated Monday email carrying those three numbers plus a link to our standard dashboard — a fraction of the cost, delivered in days rather than months. She later told me it was the first vendor deliverable she used every single week, and the client expanded their contract the following quarter, largely on the trust that conversation built. Now I ask who will actually use a deliverable before I ever quote it.
How to structure your own answer
- Situation: Set up what the customer was asking for on the surface.
- Task: Explain your role and why the stated request did not add up.
- Action: Describe the questions and listening techniques you used to dig deeper.
- Result: Share what the real need was and the result of addressing it.
Common mistakes to avoid
- Name the surface request first, or the listener cannot see what you uncovered beneath it.
- "I listened actively" is empty without the specific questions you asked.
- The customer is not the fool of the story — implying it makes you look worse, not better.
- What changed after you found the real need? An answer with no outcome proves nothing.
Follow-up questions to prepare for
Expect the interviewer to dig past your first answer. Common follow-ups for this question include:
- What do you do when a customer insists on their original solution anyway?
- How do you distinguish what customers say they want from what they actually need?
- Tell me about a time you misread a customer need. What did you miss?
Related practice questions
Keep drilling with these, or browse the complete question bank.
Next up
Practice this question on the clock
Reading an answer and delivering one are different skills. Run a timed round and rate yourself.
Start a practice roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator