What do interviewers evaluate in Earn Trust questions?

Interviewers listen for signals like: Are you vocally self-critical - do you name your own mistakes plainly, or shade them into 'lessons learned' that blame circumstances? Do you deliver bad news early and directly, or sit on risks hoping they resolve themselves? Can you take direct feedback without defensiveness and act on it visibly?

gitGood.dev

Amazon LPFoundational Premium

Earn Trust (Amazon Leadership Principle)

Amazon's bar for how leaders build credibility: listen, speak candidly, treat others respectfully, and be vocally self-critical even when it is awkward.

About this theme

Earn Trust is the principle that leaders listen attentively, speak candidly, and treat others respectfully, are vocally self-critical even when doing so is awkward or embarrassing, and do not believe their or their team's body odor smells of perfume. They benchmark themselves and their teams against the best. For an engineer it shows up as admitting your own mistakes plainly, giving and receiving direct feedback without defensiveness, being transparent about risks and bad news early, and following through on what you said you would do so people can rely on your word. In interviews this principle surfaces directly - tell me about a time you earned the trust of a skeptical team, or a time you had to deliver bad news - and as a quality threaded through almost every other story. Interviewers listen for whether you owned your part of a failure without deflecting, whether you were honest when honesty cost you something, and whether your behavior actually changed other people's willingness to depend on you. The strongest answers show trust being low, a specific action you took to rebuild it, and observable evidence that it worked.

What interviewers are evaluating

→Are you vocally self-critical - do you name your own mistakes plainly, or shade them into 'lessons learned' that blame circumstances?
→Do you deliver bad news early and directly, or sit on risks hoping they resolve themselves?
→Can you take direct feedback without defensiveness and act on it visibly?
→Do you follow through on commitments so colleagues can rely on your word?
→Did your action actually change someone's willingness to depend on you - is there observable evidence?
→Do you treat others with respect even during disagreement, conflict, or a postmortem?

Common prompts

Variations on these are asked at every level. Have a story pre-loaded for at least three of them.

?Tell me about a time you earned the trust of a skeptical stakeholder or team.
?Describe a time you had to deliver bad news to your manager or a customer.
?Tell me about a mistake you made and how you handled it.
?Give an example of when you received critical feedback - what did you do with it?
?Describe a time you had to rebuild a relationship after it broke down.
?Tell me about a time you were transparent about a risk even though it made you look bad.
?Describe a situation where you had to be candid with someone who outranked you.

Sample STAR answers (preview)

The full library pairs strong and weak examples with notes on what makes each work (or fail). Here's how two of the strong stories open.

STRONG

Strong: owning a data bug to a skeptical partner team

Prompt: "Tell me about a time you earned the trust of a skeptical stakeholder or team."

Situation: My service fed daily aggregated metrics to the analytics team, and they had stopped trusting our numbers after a previous engineer had quietly shipped a fix without telling them about a three-week window of bad data. They had started maintaining a shadow pipeline to double-check us, which cost them about a day a week.
Result: The backfill corrected 11 days of history and the reconciliation check stayed green for the next four months. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

STRONG

Strong: candid bad-news escalation on a slipping launch

Prompt: "Describe a time you were transparent about a risk even though it made you look bad."

Situation: I owned the backend for a feature launch that had been committed to a customer-facing date in an all-hands. Four weeks out, my load testing showed the new write path fell over at about 60 percent of the projected launch-day traffic because of lock contention I had underestimated when I scoped it.
Result: We did the staged rollout, hit zero contention incidents because we never exceeded safe load, and reached 100 percent two weeks later after I fixed the locking. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

What's in the full theme

3 full STAR answers (strong and weak, with interviewer notes) · 6 common pitfalls · 5 follow-up strategies

Subscribe to Continue

Get full access to gitGood.dev with a subscription.

Start Your 10-Day Trial

Try everything free for 10 days. Cancel anytime.

1000+ practice questions
AI mock interviews (3/day)
Coding challenges with real execution
Verified skill badges
105+ certification study guides

View Plans

10-day trial, then $5/mo - or $40/yr ($3.33/mo, save 33%). Cancel anytime.

Related behavioral themes

Ownership

Amazon LP

Tested at every level, scored harder at senior. Did you take responsibility for outcomes - or just for tasks?

FREE

Critical Feedback

General

Tested at every senior+ loop and every people-management interview. The signal is whether you deliver hard truths with care - or whether you avoid, soften beyond recognition, or wait for someone else to do it.

Companies that test this theme

Amazon

SDE II

Amazon

Senior SDE (L6 / SDE III)

Practice these stories live

Reading STAR answers is the floor. The interview signal is in delivering them out loud, with follow-ups, under pressure. The AI mock interview probes your stories the way real interviewers do.

Start an AI mock interview →

Amazon LPFoundational Premium

Earn Trust (Amazon Leadership Principle)

Amazon's bar for how leaders build credibility: listen, speak candidly, treat others respectfully, and be vocally self-critical even when it is awkward.

About this theme

What interviewers are evaluating

→Are you vocally self-critical - do you name your own mistakes plainly, or shade them into 'lessons learned' that blame circumstances?
→Do you deliver bad news early and directly, or sit on risks hoping they resolve themselves?
→Can you take direct feedback without defensiveness and act on it visibly?
→Do you follow through on commitments so colleagues can rely on your word?
→Did your action actually change someone's willingness to depend on you - is there observable evidence?
→Do you treat others with respect even during disagreement, conflict, or a postmortem?

Common prompts

Variations on these are asked at every level. Have a story pre-loaded for at least three of them.

?Tell me about a time you earned the trust of a skeptical stakeholder or team.
?Describe a time you had to deliver bad news to your manager or a customer.
?Tell me about a mistake you made and how you handled it.
?Give an example of when you received critical feedback - what did you do with it?
?Describe a time you had to rebuild a relationship after it broke down.
?Tell me about a time you were transparent about a risk even though it made you look bad.
?Describe a situation where you had to be candid with someone who outranked you.

Sample STAR answers (preview)

The full library pairs strong and weak examples with notes on what makes each work (or fail). Here's how two of the strong stories open.

STRONG

Strong: owning a data bug to a skeptical partner team

Prompt: "Tell me about a time you earned the trust of a skeptical stakeholder or team."

Situation: My service fed daily aggregated metrics to the analytics team, and they had stopped trusting our numbers after a previous engineer had quietly shipped a fix without telling them about a three-week window of bad data. They had started maintaining a shadow pipeline to double-check us, which cost them about a day a week.
Result: The backfill corrected 11 days of history and the reconciliation check stayed green for the next four months. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

STRONG

Strong: candid bad-news escalation on a slipping launch

Prompt: "Describe a time you were transparent about a risk even though it made you look bad."

Situation: I owned the backend for a feature launch that had been committed to a customer-facing date in an all-hands. Four weeks out, my load testing showed the new write path fell over at about 60 percent of the projected launch-day traffic because of lock contention I had underestimated when I scoped it.
Result: We did the staged rollout, hit zero contention incidents because we never exceeded safe load, and reached 100 percent two weeks later after I fixed the locking. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

What's in the full theme

3 full STAR answers (strong and weak, with interviewer notes) · 6 common pitfalls · 5 follow-up strategies

Subscribe to Continue

Get full access to gitGood.dev with a subscription.

Start Your 10-Day Trial

Try everything free for 10 days. Cancel anytime.

1000+ practice questions
AI mock interviews (3/day)
Coding challenges with real execution
Verified skill badges
105+ certification study guides

View Plans

10-day trial, then $5/mo - or $40/yr ($3.33/mo, save 33%). Cancel anytime.

Related behavioral themes

Ownership

Amazon LP

Tested at every level, scored harder at senior. Did you take responsibility for outcomes - or just for tasks?

FREE

Critical Feedback

General

Companies that test this theme

Amazon

SDE II

Amazon

Senior SDE (L6 / SDE III)

Practice these stories live

Reading STAR answers is the floor. The interview signal is in delivering them out loud, with follow-ups, under pressure. The AI mock interview probes your stories the way real interviewers do.

Start an AI mock interview →