0 day streak

BEHAVIORAL · INTEGRITY AND TRUST

Tell me about a time you had to tell someone something they did not want to hear: sample answer

Whether you are honest when it costs you something: raising a problem early, owning your part without spin, and rebuilding confidence through actions. They want to see that people could rely on what you said afterwards.

Also asked as

  • Describe a mistake you made that reached production. How did you handle it?
  • Tell me about a time you had to tell someone something they did not want to hear.
  • Describe how you built trust with a new team or stakeholder.
  • Describe a time you considered the wider effect of your work on users or society.

The short version: Show you were honest when it was uncomfortable, and how you earned trust back.

Sample STAR answer

An invented example from typical software engineering work, about 280 words, around two minutes spoken. Use the structure, not the story: yours should be real.

Situation I built a dashboard for our product team that showed weekly active users for a new feature. Three weeks after launch, the product lead used it in a planning meeting to argue for expanding the feature to more markets.

Task While adding a new chart, I noticed that users who switched between our app and website were counted twice. The real number was about 25 percent lower than the one in the planning slides. I had to tell the product lead, quickly and clearly, even though the mistake was mine and the decision was already in motion.

Action I spent an hour confirming the error with a second query so I would not raise a false alarm, then messaged the product lead the same afternoon instead of waiting for our next meeting. I wrote three things: what was wrong, the corrected number, and that it was my mistake in how I joined two data sources. I added that the trend was still upward, so they could judge whether the decision still held. I fixed the dashboard that day, put a visible note on it explaining the correction and its date, and checked my other two dashboards for the same join, finding one more small error. Then I added a test that compares our user counts against the source system each day.

Result The product lead re-ran the numbers; the expansion still made sense but went to two markets instead of four. They told me later that hearing it from me within hours, with the correct number ready, made them trust the dashboards more, not less. The daily check has since caught two data problems from other teams before anyone used them.

Weak answer vs strong answer

Weak

"I found a small bug in a dashboard I built, so I quietly fixed it. Nobody noticed, so there was no harm done."

Why it scores low: Quietly fixing a mistake that someone relied on is the opposite of integrity. There is no honesty, no thought about the decision that depended on it, and no step to prevent it happening again.

Strong

A specific situation, an action you took yourself, the reasoning behind it, and a result with a number. Show you were honest when it was uncomfortable, and how you earned trust back.

How the story changes with level

SDE 1

At SDE 1, admitting a bug you shipped or a missed estimate quickly and plainly is a solid answer. Show what you did to stop it happening again.

Senior and staff

At senior or staff level, the story should involve telling leaders something unwelcome about a project or a plan, protecting the team's credibility, and changing a process so the truth surfaces earlier.

SDE 1 interviews · Senior interviews · Staff interviews

Follow-up questions interviewers ask

  1. Why did you double-check before telling them?Show speed matters, but so does not raising a false alarm; one hour, not one week.
  2. How did the product lead react?Be honest about any frustration and how acting fast helped.
  3. Have you ever been asked to do something you thought was wrong?Prepare a short story where you pushed back calmly and offered an alternative.
  4. How do you build trust with a new team?Small promises kept, admitting what you do not know, and following up.

Amazon Leadership Principles that test this

Earn Trust · Tell me about a time you had to earn the trust of a team that doubted you.

Listen carefully, speak honestly, treat others with respect, and be willing to criticise yourself even when it is awkward.

Situation I moved to a platform team whose shared library was used by the mobile team. Two earlier releases had broken their app builds, and the mobile team had started copying our code instead of updating.

Task I was given ownership of the library. I needed the mobile team to trust our releases again, or they would keep falling behind on security fixes.

Action I asked their lead for a 30-minute meeting and mostly listened. They had three complaints: breaking changes without notice, release notes that hid what changed, and slow replies when things broke. I admitted we had got those wrong and did not argue the details. I made three small commitments I knew we could keep: a two-week notice for any breaking change, plain release notes written for app developers, and a reply within one working day. I added their build to our test pipeline so we would find breakages first. For two months I sent a short note after each release confirming their build had passed.

Result After three releases with no breakages, the mobile team moved back to our latest version and deleted their copied code. Their lead later asked us to review a design of theirs, which had not happened before.

Tip: Show listening, owning past mistakes without excuses, and small promises kept over time.

All 16 Amazon Leadership Principles with sample answers

Companies that test this

Prepare your own

Write your story in the story bank and tag it "Integrity and trust"; it will show up against every company value that tests this theme.

Related: Failure and learning · Ownership · Disagreement and candor · Collaboration and inclusion

All behavioral themes · How the behavioral round is scored