Tell me about a time when you worked to improve the quality of a product / service / solution that was already getting good customer feedback.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers are testing whether you improve something that is already working, not just whether you can rescue something broken. They want to see standards, curiosity, and judgment: how you detected remaining quality gaps, decided they were worth addressing, and translated a good baseline into a measurably better customer experience. For senior candidates especially, this also reveals whether you can raise the bar proactively rather than waiting for obvious failures.
Key Insights
- You should explain why further improvement mattered even though customers were already happy. The strongest answers show discernment about hidden risk, uneven experience, scale effects, or missed upside rather than improvement for improvement's sake.
- Don't frame the story as 'I polished it because I like high standards.' Show how you found a real quality signal beneath positive feedback and how you validated that the improvement actually helped.
- If the product was already seen as successful, the bar for changing it is higher. You need to show thoughtful prioritization, not just perfectionism.
What interviewers probe atlevel
Top Priority
At junior level, interviewers want to see that you can notice that 'good enough' is not always the same as 'high quality,' and that your observation is grounded in something real.
Good examples
🟢The feature was getting positive feedback because it solved the main problem, but I noticed support questions kept coming in about one confusing step, so I treated that as a quality gap.
🟢Our release was considered successful, but while helping test a follow-up change I saw that the happy path was smooth and one common edge case was still frustrating, so I raised that as an improvement area.
Bad examples
🔴Users seemed happy overall, but I thought the screen looked outdated, so I spent time cleaning up styles because quality matters.
🔴The feature had good reviews, but I wanted to improve it anyway, so I picked a few things to tweak without really checking whether they affected users.
Weak answers confuse personal taste with product quality; strong answers spot a concrete gap that exists alongside overall positive feedback.
Valuable
Example answers atlevel
Great answers
On a recent internal tool project, users were actually pretty happy because it saved them time compared to the old process. But while helping test a follow-up change, I noticed people often got stuck on one form field and had to ask what format it expected. I pulled a few support messages, confirmed that confusion was recurring, and suggested a smaller improvement instead of redesigning the whole page. I updated the field guidance, added clearer validation text, and worked with my teammate to test it before release. After that, support questions on that step dropped a lot over the next couple of weeks. What I was proud of was noticing that positive overall feedback still left room to remove friction for users.
At my previous job on a consumer web app, our overall reviews were excellent but I noticed a small steady trickle of emails from users who rely on screen readers saying parts of the checkout felt unusable. I pulled the pages into a local build, walked through them with a screen reader to see where labels and focus order were failing, and sketched a minimal set of fixes that wouldn’t change the design, just how elements are announced and navigated. I paired with a more senior engineer to implement clearer element descriptions and correct tab order, added a couple of simple tests to prevent regressions, and we shipped the change in a small patch. After that release those accessibility complaints stopped and we saw a small but measurable increase in checkout completion for keyboard/screen-reader sessions. I felt proud because improving quality here aligned with my belief that good products should work well for everyone, not only the majority of users.
Poor answers
I worked on a dashboard that users already liked, and I wanted to improve the quality by cleaning up the interface. I changed some spacing, renamed a few labels, and reorganized a couple of sections because I thought it looked more professional. The team liked the changes and merged them pretty quickly. It was a good example of me caring about quality even when customers were already happy.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Late October, 2024
Hello Interview Premium
Your account is free and you can post anonymously if you choose.