Tell me about a change you made that was customer-focused.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to see whether you can recognize customer pain, translate it into an actionable change, and follow through to improve the user experience. They are also testing whether your idea of "customer-focused" is real and evidence-based, rather than just a feature you happened to build. At higher levels, they want to hear how broadly you influenced the product, team, or organization around customer needs.
Key Insights
- You should make the customer problem concrete. "We improved onboarding" is much weaker than explaining what customers were struggling with, how you knew, and why it mattered.
- Customer focus is not the same as saying yes to every request. Strong answers show judgment: you understood the underlying need, weighed tradeoffs, and chose a change that meaningfully improved the customer experience.
- Don't stop at shipping. You should explain how you validated that the change actually helped customers, even if the signal was qualitative or imperfect.
What interviewers probe atlevel
Top Priority
At junior level, the strongest answers show that you understood a specific user pain point instead of just implementing a task someone handed you.
Good examples
🟢I was working on a support workflow and noticed several tickets from users who couldn't tell whether their upload had finished. I traced that to the UI not showing progress clearly, so I proposed adding a status indicator.
🟢While testing a small feature, I sat in on a few support reviews and saw customers repeatedly misinterpret an error message. That made it clear the issue wasn't just technical correctness; the message itself was causing confusion.
Bad examples
🔴My manager asked me to add a new filter to the dashboard, so I built it. Customers like having more options, so it was definitely customer-focused.
🔴We got a request to change the button color because users were confused, and I updated it. I assumed that would help because the old one didn't look great.
Weak answers label work as customer-focused without showing how the customer problem was known; strong answers tie the change to observed pain, feedback, or clear user friction.
Valuable
Example answers atlevel
Great answers
In my last role, I was working on a file upload page and noticed support tickets from users who thought uploads were failing when they were actually still processing. I dug into a few of the tickets and saw that the page gave almost no feedback after you clicked submit, so I suggested adding a visible progress state and a clearer success message. I checked the idea with my mentor, implemented it, and made sure it worked well on slower connections too. After we released it, support told us they were seeing fewer questions about "missing" uploads, which was a good sign we had fixed the confusion rather than just changed the UI. I liked that project because it taught me that a small engineering change can matter a lot when it's tied to a real user problem.
While I was at a small ed-tech startup I spent a week answering support chats and realized many teachers were stuck on our "create class" flow because terms like "CSV export" and "synchronization" confused them. I proposed simplifying the labels, adding plain-language helper text, and putting a short example CSV file directly on the page. I implemented the text changes and the example file myself, then tested the flow with two teachers from our pilot program and adjusted the wording based on their feedback. After we shipped the changes, activation for new classes rose noticeably and support saw far fewer roster-related questions. It felt great to make a small change that lowered the barrier for people who aren't technical and let them use the product right away.
Poor answers
One customer-focused change I made was updating the labels on a settings page because I felt the old wording was too technical. I changed several terms to simpler ones and sent it out in the next release. People didn't raise any issues afterward, so I consider that a success. It also showed I can think from the customer's perspective instead of just coding.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Early July, 2026
Mid March, 2026
Mid January, 2026
Hello Interview Premium
Your account is free and you can post anonymously if you choose.