Give me an example of a time when you asked for customer feedback.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to assess whether you actively close the loop with the people affected by your work rather than relying on assumptions. They want to see judgment about when feedback is worth seeking, how you gather it, and whether you turn what you hear into concrete changes. At higher levels, this also tests whether you build repeatable mechanisms for learning from customers, not just one-off conversations.
Key Insights
- You should explain why you sought feedback at that moment. The strongest answers show a clear decision point, risk, or uncertainty that made direct customer input necessary.
- Don't treat customer feedback as a ceremonial step. Strong answers show how you asked good questions, separated signal from noise, and changed something meaningful based on what you learned.
- If you're senior or above, one customer conversation is usually not enough. Show how you translated individual feedback into a broader product, team, or organizational improvement.
What interviewers probe atlevel
Top Priority
You do not need to run perfect research, but you should show that you asked useful questions and listened for the underlying problem.
Good examples
🟢Instead of asking whether the screen looked good, I asked them to complete a real task and talk through where they got stuck.
🟢I asked what they were trying to do before using the feature so I could tell whether the issue was the interface or the overall workflow.
Bad examples
🔴I showed them the feature and asked if they liked it, and they said yes, so that gave us confidence.
🔴I mostly walked the customer through what we built and noted the parts where they hesitated.
Weak answers ask leading or superficial questions; strong answers are structured to reveal actual behavior, confusion, or unmet needs.
Valuable
Example answers atlevel
Great answers
On my last team, I worked on a small change to our account setup flow for internal customers in operations. After we released it, I noticed a few people were still asking the same questions in chat, so I asked my lead if I could talk directly with two of the users. I had them walk through the setup while I watched, and I realized the problem was not the backend logic I had changed but that the first step used terms they didn't recognize. I updated the labels and added a short explanation, then asked the same users to try it again. They finished without help, and the number of questions in chat dropped the next week. That experience taught me not to assume a feature is clear just because it works technically.
In my first job after college I owned a small feature to nudge new users to enable push notifications, and I noticed the opt-in rate stalled at about 8%. I recruited ten recent sign-ups and did five short phone interviews asking why they'd declined notifications and what would change their mind. Most said they didn't know what types of messages they'd get and were worried about spam or losing control. I rewrote the prompt to include two concrete examples of useful notifications and a direct link to manage settings, then rolled it to a small test group. Opt-ins jumped to around 20% the next week, and I learned that transparency and giving users control mattered more than persuasive copy.
Poor answers
I asked for customer feedback after I shipped a settings page update. I sent a message asking whether people liked the new page, and a few said it looked good, so I took that as a positive result. There were some other comments too, but they were mostly preferences, so I didn't think they were important. Overall, I think it was useful because we confirmed the release was fine.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early April, 2026
Early November, 2025
Late September, 2025
Hello Interview Premium
Your account is free and you can post anonymously if you choose.