BEHAVIORAL · CUSTOMER FOCUS
Tell me about a time you changed a plan because of what you learned about the user: sample answer
Whether you start from a real user problem rather than from the technology, and whether you are willing to change your own plan when the evidence about users points elsewhere. They want a decision that made a measurable difference for someone outside the team.
Also asked as
- Describe a time you changed a plan because of what you learned about the user.
- Tell me about a time you had to balance a customer need against a technical constraint.
The short version: Start from a real user problem and show how your decision changed something for them.
Sample STAR answer
An invented example from typical software engineering work, about 250 words, around two minutes spoken. Use the structure, not the story: yours should be real.
Situation I was on a team building the payments flow for a subscription app. Our plan for the quarter was a new saved-cards feature that product had asked for.
Task Before starting, I wanted to understand why payment-related support tickets had been rising, because they were the second biggest ticket category and nobody on the team had read them.
Action I spent an afternoon with the support team and read about a hundred recent tickets. Most were not about saved cards at all. When a bank declined a payment, we showed one generic "payment failed" message, so people retried the same card, got declined again and wrote in. I pulled our decline codes and found that about a third were recoverable: an expired card, a bank asking for extra verification, or a simple timeout. I wrote up the numbers and proposed pausing saved cards for two weeks to fix this first. Product agreed once they saw the ticket count. I mapped the common decline codes to plain messages that told people what to do next, added one automatic retry for timeouts, and added a prompt to update an expired card. We shipped it behind a flag to ten percent of users first and compared.
Result Payment-related tickets dropped by about forty percent and successful renewals rose by three percent, which was worth more than the saved-cards feature we had planned. We shipped saved cards three weeks later. Since then I read a sample of tickets before planning any feature in that area.
Weak answer vs strong answer
Weak
"Customers are always my top priority. On one project I made sure the payment page was really user-friendly and we got good feedback from users after launch."
Why it scores low: It is a claim, not a story. There is no specific user problem, no evidence, no decision that cost anything and no number. Saying the customer comes first without showing a trade-off sounds rehearsed.
Strong
A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Start from a real user problem and show how your decision changed something for them.
How the story changes with level
At SDE 1, reading tickets, spotting the pattern and fixing the error messages well is enough. Show curiosity about users and a clean, measured change.
At senior or staff level, show that you changed how the team plans: reading tickets as a standing step before planning, a shared dashboard of user pain, and a roadmap trade-off you argued for.
Follow-up questions interviewers ask
- How did you know the tickets represented most users and not just a vocal few?Back the anecdotes with data: decline codes, counts, a controlled rollout.
- What did delaying saved cards cost, and who pushed back?Admit the cost and explain how you won agreement with numbers.
- How do you balance what users ask for with what they need?Listen to the problem behind the request; the request itself is one possible solution.
- How did you measure the result?Name the metric you chose before shipping and how you compared against a control.
Amazon Leadership Principles that test this
Customer Obsession · Tell me about a time you went out of your way for a customer.
Start from what the customer needs and work backwards; keep their trust even when a competitor or an internal goal pulls you elsewhere.
Situation I worked on the sign-up flow of a mobile app. Our funnel showed that about 12 percent of new users never finished verifying their phone number, and the drop was much higher in regions with slower networks.
Task The team's goal that quarter was a new referral feature, but I believed these users were stuck at the very first step, so I asked for a week to understand why.
Action I tested the flow on a throttled network and on two older phones. The one-time code often arrived after our 30-second timer ran out, and the screen then told people to start over, which sent a second code and made the first one invalid. People were entering a code that had just stopped working. I worked backwards from what the user saw: I extended the timer to two minutes, kept the last two codes valid for a short window, added a "call me with the code" option after 45 seconds, and rewrote the error to say exactly what to do. I shipped it to a small share of users first and compared completion rates.
Result Verification completion rose from 88 to 96 percent, which meant thousands more new users each week actually got into the app, more than the referral feature was expected to bring in its first quarter. Support tickets about codes fell by more than half.
Tip: Show you looked at the problem from the user's screen, and that you chose their need over the planned roadmap with evidence.
Companies that test this
- AmazonCustomer Obsession
- LinkedInWe put members first
- StripeUsers first
- DatabricksWe are customer obsessed
- SnowflakePut Customers First
- DoorDashCustomer-obsessed, not competitor focused
- CoinbaseCustomer focus
- NutanixWe Obsess About Our Customers' Success
- AtlassianDon't #@!% the customer
- Goldman SachsClient Service
- SalesforceCustomer Success
- IntuitCustomer Obsession
- ServiceNowWow our customers
- JPMorgan ChaseExceptional client service
- Morgan StanleyPut Clients First
- VisaObsess about customers
- American ExpressWe Back Our Customers
- IntelCustomer first
- IBMDedication to every client's success
- Wells FargoWhat's right for customers
- VMware by BroadcomCustomer focus
- Walmart Global TechServe Our Customers and Members
- SwiggyConsumer Comes First
- RazorpayCustomer First
- CREDMake members win
- ZeptoCustomer obsession
- InfosysClient Value
- WiproBe passionate about clients' success
- FreshworksWe champion our customers
- OlaCustomer and driver focus
- AccentureClient Value Creation
- MakeMyTripCustomer Focus
- NykaaBe the customer's champion
- Jio PlatformsCustomer Value
Prepare your own
Write your story in the story bank and tag it "Customer focus"; it will show up against every company value that tests this theme.
Related: Ambiguity and judgment