To answer “tell me about a time you earned someone's trust,” pick one specific person, such as a skeptical new team, a client after a failure, a reviewer who checked all your work or a stakeholder who'd been let down before, and explain in one sentence why they didn't trust you yet. Then show what you did over weeks: kept small promises exactly, told the truth when it cost you something, admitted your own mistakes and followed through. End with evidence that the trust was real, meaning something they let you do that they wouldn't have before.
Below: what the question tests, how it differs from similar questions, a STAR structure with timings, four sample answers for different levels and fields, the mistakes to avoid, the follow-up questions to expect and a ten-minute practice routine.
What “tell me about a time you earned someone's trust” really tests
Trust is earned through behavior over time, so this question needs a story with a before and an after. The interviewer listens for:
- A real gap. There was a reason for doubt, and you describe it fairly.
- Reliability. Small commitments kept, every time.
- Candor. You told them something unwelcome, or admitted an error, before they found it.
- Patience. You didn't expect trust after one good meeting.
- Evidence. A concrete change shows the trust was earned, not assumed.
Amazon's Earn Trust principle, as published on its careers site on November 16, 2026, begins: “Leaders listen attentively, speak candidly, and treat others respectfully. They are vocally self-critical, even when doing so is awkward or embarrassing.” The self-critical part is what most candidates leave out, and it's often the turning point in a strong answer. For Amazon interviews, see our Amazon Leadership Principles examples.
How it differs from other trust questions, and what counts as evidence
| Question | Center of the story |
|---|---|
| “Earned someone's trust” | One person, a reason for doubt, behaviors over time and evidence of the change |
| “How do you build trust with clients?” | Your habits across clients, often answered as a process |
| “How do you build relationships with new team members?” | Your routine for joining a team |
| “Tell me about a promise you couldn't keep” | Handling a broken commitment |
Evidence of trust you can cite:
- They delegated something they used to keep, or stopped double-checking your work.
- They gave you access, budget or a decision they'd previously kept for themselves.
- They came to you first with a problem.
- A client renewed, expanded or referred someone after a rough patch.
- They asked for you by name on the next project.
A STAR structure with timings
| Step | What to say | Time |
|---|---|---|
| Situation | Who, and why trust was low, described fairly. | About 15 seconds |
| Task | What depended on their trust. | About 10 seconds |
| Action: habits | Two or three behaviors you kept up over weeks. | About 25 seconds |
| Action: the moment | One time you were candid or admitted a mistake when it cost you. | About 20 seconds |
| Result | The evidence of trust, and what it made possible. | About 20 seconds |
Give the time span, such as “over about three months.” It signals that you understand trust is built, not won in one meeting.
Four sample answers to “tell me about a time you earned someone's trust”
These are example answers we wrote to show the structure at different levels and in different fields; they are not real candidates' stories. Swap in your own situation, and use only numbers you can back up if asked.
Entry-level (junior accountant): a reviewer who checked everything
“When I joined, my senior reviewer re-checked every reconciliation I did, line by line, because my predecessor's work had needed a lot of fixes. I started sending each reconciliation with a short note: what I'd checked, where the figures came from and anything I wasn't sure about. In my second month I found an error of my own after sending a file and told her before she found it. Over about three months she stopped re-checking routine reconciliations, and she handed me the month-end accruals, which she'd always done herself.”
Manager (engineering manager): an inherited team
“I took over a team that had had three managers in two years and assumed I'd be gone soon too. In my first one-to-ones I asked what had gone wrong before, and two things kept coming up: an unfair on-call schedule and unclear promotion criteria. I committed to fixing both within six weeks and posted progress every Friday. I fixed the schedule in three weeks and published the criteria in five. When I couldn't get a budget increase they'd hoped for, I told them directly instead of letting it drift. Six months later, our team's survey score on trust in their manager was the highest in the department.”
Technical (platform engineer): a team that had been let down
“A product team had stopped using our platform after we'd missed two delivery dates, and they were building their own workaround. I was assigned as their contact. I committed only to dates I was sure of, sent a short status every week whether or not there was news, and delivered a small API change they needed a week early. When I found a bug in our release that would hit them, I told them the same day with a workaround. The next quarter they chose our platform for a new feature instead of building their own.”
Customer-facing (account manager): a client after missed renewals
“I inherited a client whose previous account manager had missed two renewal dates, and their operations lead told me in our first meeting that she expected the same. I sent a written recap within 24 hours of every call, set renewal reminders 90 days out and told her about a price increase two months before it took effect, with options. When our team made a billing error, I called her before the invoice arrived. The next year she expanded the contract and introduced me to another department.”
Mistakes to avoid
- Charm instead of behavior. “I'm easy to get along with” isn't evidence.
- Instant trust. A story that resolves in one meeting doesn't sound real.
- Trust by agreeing to everything. Saying yes to every request isn't the same as being trusted.
- Criticizing whoever broke the trust before. Describe the history neutrally.
- No evidence. Without a before and an after, the interviewer has to take your word for it.
Follow-up questions to expect
- “How did you know you'd earned their trust?” Point to the evidence: what changed in how they worked with you.
- “Tell me about a time you lost someone's trust.” Own it, and show how you rebuilt it.
- “How do you build trust with someone who disagrees with you?” Candor and consistency, with an example.
- “What do you do when you can't keep a commitment?” Tell them early, with a new plan; see our answer to a promise you couldn't keep.
- “How long did it take?” Give a realistic time frame.
A ten-minute practice routine
- Minutes 0–2: name three people who trust you more now than when you started, and pick the one with the clearest reason for early doubt.
- Minutes 2–4: write the before and the after in one line each.
- Minutes 4–6: write the two habits and the one candid moment that changed things.
- Minutes 6–8: say it aloud in about 90 seconds, including the time span.
- Minutes 8–10: answer “tell me about a time you lost someone's trust” aloud, then run both questions in a mock interview.
Where CoPilot Interview fits
Trust stories need a clear before and after, which is easy to lose when you improvise. CoPilot Interview is an AI interview assistant whose free AI mock interview reads behavioral questions like this one aloud and scores each spoken answer out of 10, and whose browser demo has 145 practice questions in 10 tracks and scores typed answers out of 10, with no signup. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included; the desktop app runs on Windows 10 and 11 and macOS 12 or later. Practice is the use nobody objects to; if you ever consider live help in a real interview, follow your employer's rules.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
How long should the story span?
Usually weeks or months. Trust that appears in a single day is hard to believe, so give the time frame.
Can I use a client or customer?
Yes. Client stories are common for sales, account management and service roles; internal stories, with a reviewer, a team or another department, work for everyone.
What if I was the one who broke their trust first?
That can be a strong story if you own it plainly and show how you rebuilt it. It overlaps with a mistake story, so use different examples for the two questions.
How long should the answer be?
About 90 seconds.
Practice this interview before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview