Tell me about a time when you were able to make something simpler for customers.
Try This Question Yourself
Practice with feedback and follow-up questions
What is this question about
Interviewers use this question to see whether you notice customer friction and take ownership of reducing it, rather than just delivering features as requested. They are also looking for judgment: did you identify the real source of complexity, make a meaningful simplification, and verify that life actually got easier for customers? At higher levels, they want to hear whether you simplified not just a screen or workflow, but a broader product or operational experience across multiple people or teams.
Key Insights
- You should talk about customer simplicity, not just technical elegance. A cleaner implementation only scores if you connect it to a clearer, faster, safer, or less error-prone customer experience.
- Don't stop at 'I removed steps.' Explain how you figured out what was actually confusing or burdensome for customers; strong answers show curiosity about the root cause, not just enthusiasm for simplification.
- You do not need a dramatic redesign story. A strong answer can be a focused improvement, but you should make clear why it mattered, what tradeoffs you handled, and how you knew it worked.
What interviewers probe atlevel
Top Priority
At junior level, the bar is noticing a concrete customer pain point and showing that your work addressed that pain rather than just making the code or UI feel cleaner to you.
Good examples
🟢I noticed users kept abandoning the setup flow on the permissions page, so I reviewed the support notes and found the instructions were too technical. I rewrote that step in plain language and added a short example of what to click.
🟢During testing, new users repeatedly got stuck because they had to copy an ID from another screen. I suggested surfacing that ID automatically in the same place so they didn't have to context-switch.
Bad examples
🔴The form had a lot of fields, so I hid some of them to make it look less busy. It seemed simpler after that.
🔴I thought the flow was kind of annoying, so I changed the order of the steps. Customers didn't complain to me afterward, so I assumed it was better.
Weak answers center the candidate's taste; strong answers center observed customer confusion or effort.
Valuable
Example answers atlevel
Great answers
In my first year, I worked on a small improvement to our signup flow for a developer tool. I noticed from support notes and a few usability sessions that new users got stuck when we asked them to paste in an account ID from another page, because they didn't know where to find it. I suggested showing the ID inline during signup and adding a short plain-language explanation, then I implemented the change with help from my mentor. After we released it, support stopped getting that same question nearly as often, and more test users were able to finish signup without assistance. It was a small project, but it taught me that making things simpler starts with understanding exactly where customers are getting blocked.
At my first job as a junior engineer on a consumer banking app, I noticed through support logs and a couple of ride-alongs with the call center that customers were frequently panicking about “pending” transactions and calling to ask if money had actually left their account. I proposed a small change: visually separate pending and posted transactions and add a one-line explanation that says when pending charges typically clear or who to contact if the amount looks wrong. I built the UI change and the short copy myself, checked it with a designer for clarity, and shipped it with a quick A/B test. Afterward the number of support tickets about pending charges dropped noticeably, and agents reported fewer frustrated callers — it was a small feature but it reduced anxiety and saved the team time, which felt really meaningful to me.
Poor answers
I made one of our pages simpler by cleaning up the layout and shortening some labels. The screen looked a lot better afterward and felt more modern. I didn't need to make any major logic changes, so it was a quick win. My team was happy with it, and I think customers generally prefer cleaner screens.
Question Timeline
See when this question was last asked and where, including any notes left by other candidates.
Mid December, 2024
Hello Interview Premium
Your account is free and you can post anonymously if you choose.