Tell me about a time when you were able to make something simpler for customers.
Asked at:
Amazon
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.
“Describe a time you reduced friction for a customer or user.”
“Can you give me an example of simplifying a product experience for users?”
“Tell me about a situation where customers were struggling and you made the experience easier.”
“What's a time you removed unnecessary complexity from something customers had to do?”
“Have you ever taken a workflow that felt confusing for users and made it more straightforward? What happened?”
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
You do not need to be the sole driver, but you should clearly show what you personally did to move the simplification from observation to shipped improvement.
Good examples
🟢I raised the issue, mocked up a simpler version with my mentor's help, implemented the changes, and asked our support contact if the updated wording addressed the same questions users had been asking.
🟢After seeing where users got stuck, I wrote the change, tested it with two teammates who hadn't used the feature before, and followed the release to make sure new setup attempts completed successfully.
Bad examples
🔴I pointed out that the instructions were confusing, and the designer updated them later. That ended up making things simpler for users.
🔴I mentioned in our meeting that setup should be easier, and eventually we changed the page.
Weak answers stop at noticing or suggesting; strong answers show follow-through and some attempt to validate the result.
A junior story can be small, but it should still matter in a real way to users; avoid presenting a cosmetic cleanup as customer impact.
Good examples
🟢I simplified one confusing step in onboarding, and after release new users were able to finish setup without asking for the same clarification we had been getting repeatedly.
🟢My change was limited in scope, but it removed a common point of failure for first-time users and noticeably reduced retries during setup.
Bad examples
🔴I renamed a button to something shorter, which made the product simpler for customers.
🔴I updated spacing on a page so it looked cleaner, and that improved the overall experience.
Weak answers mistake polish for impact; strong answers show a modest but real reduction in customer effort.
Valuable
At staff level, the interviewer is listening for product and systems judgment: did your simplification strategy reduce customer burden without pushing hidden costs elsewhere?
Good examples
🟢I was careful that simplification for customers did not just become recurring toil for internal teams. We paired immediate experience improvements with backend changes that made the simpler path sustainable.
🟢We consolidated multiple paths into one guided journey, but only after defining where product-specific differences were actually important. The simplification removed arbitrary variation while preserving distinctions customers relied on.
Bad examples
🔴We unified the workflow by forcing all products into the same model, even though some teams had to add manual exceptions behind the scenes.
🔴I simplified the customer-facing experience by moving complex cases to operations. That was acceptable because customers no longer had to think about them.
Weak answers hide complexity by shifting it elsewhere; strong answers reduce needless complexity while managing downstream costs and constraints.
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
Amazon
Mid-level
Hello Interview Premium
Your account is free and you can post anonymously if you choose.