Question and when it applies
Describe a real mistake that made a teammate, customer, or partner question your judgment or reliability. Explain the impact, how you confirmed what they needed, the repair actions, and what changed in the relationship and work outcome.
Atlassian’s trust playbook recommends a clear apology and next steps when trust wobbles, with explicit expectations and ownership. Amazon’s Earn Trust principle emphasizes candor, self-criticism, and respect. The evidence is observable repair, not asking someone to “trust me again.”
What interviewers assess
Interviewers look for ownership without excuses, listening before proposing a fix, specific and testable commitments, willingness to pay short-term costs, consistent follow-through, and a process change tied to the root cause.
Questions to clarify before answering
- What happened and who was affected?
- Was the impact rework, delay, customer risk, or missing information?
- When did you learn of it, and did you disclose it proactively?
- What did the other person need first: facts, a remedy, choice, or time?
- Which actions stopped the damage and which rebuilt trust?
- What evidence shows that collaboration improved?
- Are you telling a technical failure story without relationship repair?
30-second answer framework
“I mistakenly [action], which caused [impact]. I told [person] on [time], accepted responsibility, and asked what they needed. I owned [repair] with [acceptance condition]. The short-term cost was [cost], and the result was [relationship and business outcome]. I then added [mechanism] and checked it at [follow-up point].”
Deep answer, step by step
Step 1: Choose a mistake that affected trust
The mistake should change how others view your reliability, judgment, or promises. A bug with no relationship impact is a different question.
Step 2: State facts and impact first
Say what happened, who was affected, and the current risk. Do not bury responsibility inside “we.”
Step 3: Let the affected person shape the repair
Ask what they observed, what is urgent, and which remedy is acceptable. An apology does not require immediate forgiveness.
Step 4: Make the repair concrete
Name an owner, time, acceptance condition, and escalation path: corrected report, customer update, permission reduction, or independent review.
Step 5: Absorb cost and stay transparent
Repair may require rework, a missed launch window, or extra review. Report progress and new risks rather than disappearing until everything looks perfect.
Step 6: Verify relationship and outcome
Use observable signals: the person entrusts you with key work again, customers resume use, rework closes, or quality metrics improve. One apology does not prove full recovery.
Step 7: Change the mechanism and follow up
Add a checklist, review, handoff rule, permission gate, or retrospective tied to the root cause. Schedule a later check to confirm it is used.
High-quality sample answer
“I sent an unverified billing summary to Customer Success before a customer update. They spent half a day reconciling it and became less confident in my numbers. I disclosed the mistake that morning, stated the impact, and asked what they needed first: a traceable corrected report and a communication timeline.
I reran the checks, attached sources to every figure, and asked Finance for an independent review. I delayed the automated notice until Customer Success approved the report. They completed the customer update the next day and continued assigning me similar summaries, with a source list attached. I added a rule that external reports require independent verification and checked adherence weekly for four weeks. The repair came from predictable evidence and follow-through, not from asking for reassurance.”
Common mistakes
- Explaining why you failed before stating impact.
- Treating an apology as the complete repair.
- Asking for immediate trust.
- Blaming the team instead of naming your controllable actions.
- Hiding rework, delay, or extra-review costs.
- Never checking whether collaboration actually improved.
- Fixing the technical defect while ignoring the relationship.
Follow-ups and how to answer
Follow-up 1: What if the person does not accept the apology?
Respect their timing, complete the promised repair, provide evidence, and let them choose verification and communication.
Follow-up 2: How do you know trust returned?
Use behavior: key work is delegated again, extra checking decreases, customers resume use, or collaboration feedback improves.
Follow-up 3: What if the harm cannot be fully repaired?
Reduce remaining impact, disclose limits, escalate decisions, and prevent further spread. Do not promise impossible perfection.
Follow-up 4: How do you keep an apology from becoming performance?
Keep it brief and specific about impact and next action; let consistent behavior carry the rest.
Follow-up 5: What changed in your working style?
Name a root-cause control such as peer review, source checklists, explicit handoffs, or an escalation threshold, and give follow-up evidence.
Follow-up 6: What if a teammate also contributed?
Own your part first, describe shared causes factually, and avoid using shared responsibility to evade your commitment.