Tell me about a time you received a complaint and how you handled it
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to see how you respond when someone says your work, behavior, or decision created a problem for them. They are usually testing for ownership, emotional maturity, and whether you can turn criticism into a constructive resolution rather than becoming defensive. At higher levels, they also care about whether you resolved the underlying issue in a durable way and protected the working relationship.
Key Insights
- A complaint is not automatically a conflict or an attack. Strong answers show that you treated it as information first, then figured out whether the issue was misunderstanding, execution quality, unmet expectations, or a real mistake.
- You should name your own contribution clearly. Even if the complaint was partially unfair, seasoned interviewers look for whether you can separate 'what I disagree with' from 'what I could have handled better.'
- Don't stop at 'I fixed the immediate issue.' The best answers show you understood why the complaint happened and changed something meaningful in your behavior, communication, or operating approach.
What interviewers probe atlevel
Top Priority
A good junior answer doesn't just fix the task; it shows you repaired trust by communicating clearly and following through.
Good examples
🟢Once I understood the complaint, I fixed the issue, walked the teammate through what changed, and checked later that the updated approach worked for them.
🟢I corrected the problem quickly and also reset expectations with the person who raised it so they knew what to expect from me next time.
Bad examples
🔴I fixed the bug that prompted the complaint and considered the situation done, since the technical issue was the main thing.
🔴After a teammate complained, I sent them the corrected version but didn't really check back because I assumed they would reach out if anything else was wrong.
Weak answers close the ticket; strong answers close the loop with the person affected.
Valuable
Example answers atlevel
Great answers
In my first year, a QA engineer told me that a feature I had built was frustrating to test because I had made several assumptions that weren't documented and one edge case caused the screen to fail silently. I thanked them for flagging it and asked them to walk me through exactly where they got stuck, because at first I thought it was just one bug. That conversation showed me the bigger issue was that I had optimized for getting the feature working, but not for making the behavior clear to someone else. I fixed the bug, added clearer error handling, and updated the handoff notes with the assumptions and test cases I had missed. I also checked back with them the next day to confirm the updated flow was easier to test. After that, I started including a short list of edge cases whenever I handed off work, and reviews went much more smoothly.
At my last job, I was helping with support for a small e-commerce team, and a store owner called in upset because a discount code they had emailed customers was not working during a weekend promotion. I listened without interrupting, apologized for the inconvenience, and asked a few questions so I could understand exactly what they had tried and how many orders might have been affected. I found that the code had been entered correctly, but the expiration date had been set in the wrong time zone, so it had shut off a few hours early. I fixed it right away, helped them test a new code before sending anything else, and then wrote a simple checklist for our team so we would confirm time zones before scheduling future promotions. I also followed up later that day to let them know what had happened and what we had changed. After that, I became a lot more careful about how I handled customer-facing settings, because I saw how much trust even a small mistake can affect.
Poor answers
One time a teammate complained that my pull request was hard to review because it touched too many files. I explained that the files were related and that splitting it up would have taken longer, so I kept it mostly as-is and just added a summary comment. They were able to review it after that, so it worked out fine. I think sometimes people just have different preferences, and in that case I felt my approach was still reasonable.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid June, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.