BQ-027 · Failure, feedback, and growth
Tell me about difficult feedback you received.
Illustrative fictional example · Editorial draft, version 1. Use the structure and reasoning to prepare your own experience. Do not present this sample as your personal history.
What the interviewer may evaluate
These are general coaching criteria; interviewers and roles differ.
- Describe the behavior identified by feedback, its effect on others, and how you checked whether your change was useful.
- Can you explain the evidence behind a concern fully discussed and incorporated into a later test plan?
- Can you describe checking the effect of a behavior rather than relying on good intentions without overstating the outcome?
Before you start
- Describe the behavior identified by feedback, its effect on others, and how you checked whether your change was useful.
- Separate personal actions from team outcomes.
Choose an experience that answers the prompt
Suitable examples
- Feedback about a behavior others could observe.
- An uncomfortable critique that led to a tested change.
Examples to avoid
- A compliment repackaged as difficult feedback.
- A story about proving that the feedback giver was wrong.
Gather your evidence
- Describe the behavior identified by feedback, its effect on others, and how you checked whether your change was useful.
- Your decision, the alternative of defending helpful intent without changing meeting behavior, and the reason for the choice.
- The observations that support a concern fully discussed and incorporated into a later test plan and their limitations.
Build the answer
- Situation and responsibility. Describe the behavior identified by feedback, its effect on others, and how you checked whether your change was useful.
- Actions and reasoning. Explain what you personally changed, who helped, and why you considered defending helpful intent without changing meeting behavior.
- Outcome and evidence. Report a concern fully discussed and incorporated into a later test plan. Distinguish observation from an assumption or future goal.
- Reflection and follow-through. Explain checking the effect of a behavior rather than relying on good intentions. Name one limitation or remaining follow-up.
Full sample answer and paragraph explanations
Read aloud to check pacing. Expand the annotations to see why each paragraph matters and which detail belongs in a follow-up.
Reveal the full illustrative answer
Situation and responsibility
After a design review, a teammate told me I often interrupted questions with a solution before they had finished explaining the concern. I thought I was helping the meeting move quickly, but they felt that disagreement was being closed down. I was leading the review for my project, so my behavior affected whether other engineers could contribute. The feedback was uncomfortable because my intent and its effect were different.
Why this paragraph works
Evidence: A specific behavior and its effect on participation.
Why it matters: Makes the feedback consequential without exaggerating it.
Prepare for a follow-up: Prepare who gave feedback and your review role.
Actions and reasoning
I asked for a specific example and listened without immediately explaining why I had interrupted. The teammate pointed to a discussion about a retry path where I had answered a simpler question than the one they were trying to ask. I apologized for cutting them off and asked whether a new review structure would help. In subsequent reviews, I let the speaker finish, summarized the concern before responding, and maintained a visible list of unresolved questions. I also asked the facilitator to stop me if I skipped that step.
Why this paragraph works
Evidence: An example, acknowledgment, and a new practice.
Why it matters: Shows listening in the response itself.
Prepare for a follow-up: Explain why the visible question list supported the change.
Outcome and evidence
In the next review, the teammate raised the retry concern fully, and it revealed an assumption in my design that needed testing. We changed the test plan as a result. Later, they told me it had been easier to get the concern discussed. That is evidence of one improved interaction and a better review outcome, not proof that I became an excellent listener in every setting. I continued asking for feedback after important meetings.
Why this paragraph works
Evidence: A changed test plan and later feedback.
Why it matters: Provides concrete progress with evidence limits.
Prepare for a follow-up: Prepare the assumption found and whether the issue was resolved.
Reflection and follow-through
I learned that receiving feedback means changing a behavior people can observe rather than defending my intention. I still sometimes feel pressure to answer quickly, especially under a deadline. The habit I use is to confirm the actual concern before offering a solution. It also makes the technical work better, because I am less likely to solve the question I expected instead of the one a colleague is asking.
Why this paragraph works
Evidence: An ongoing habit and remaining trigger.
Why it matters: Avoids a claim of permanent personality change.
Prepare for a follow-up: Explain how time pressure can bring back the old behavior.
Reveal the concise version — roughly 60–90 seconds
A teammate told me I interrupted concerns in design reviews by offering solutions before they had finished. I intended to help, but the effect was to shut down discussion, particularly because I was leading the review. I asked for an example and learned that I had answered a simpler version of a retry concern. I apologized and changed the review process: let the speaker finish, summarize the concern, and track unanswered questions visibly. In the next review, the full concern exposed an assumption we added to the test plan. The teammate later said it was easier to raise issues. I still work on this under time pressure, and I ask for feedback rather than assuming one better meeting solved the pattern.
Improve a weak answer
Weak excerpt
They said I interrupted, but they did not understand that I was trying to save time.
Improved excerpt
I asked for a specific example and listened without immediately explaining why I had interrupted. The teammate pointed to a discussion about a retry path where I had answered a simpler question than the one they were trying to ask. I apologized for cutting them off and asked whether a new review structure would help. In subsequent reviews, I let the speaker finish, summarized the concern before responding, and maintained a visible list of unresolved questions. I also asked the facilitator to stop me if I skipped that step.
Moves from defending intent to understanding the effect and changing an observable meeting behavior. The improved excerpt still needs the observed result and its limits to become a complete answer.
Prepare for probing questions
Attempt each response before opening the guidance. Replace fictional details with your own evidence.
What was your first reaction?
I felt defensive because I believed I was helping. I chose to ask for an example before explaining my intent. A credible answer can admit that reaction while showing that it did not determine the eventual behavior.
Did you agree with every part of the feedback?
I agreed that the impact mattered even if my intention was different. If part of feedback is unclear, I ask for observable examples rather than accepting or rejecting a broad label. In this case the retry discussion made the behavior concrete.
How did you check improvement?
I asked the teammate after later reviews and observed whether concerns were fully discussed and tracked. One review produced a changed test plan. I would not claim a measurable team-culture transformation from that limited evidence.
Why did you change the meeting process?
The visible question list made it harder to skip unresolved concerns, and a facilitator could interrupt my old pattern. A process change supported the personal habit. It was not intended to make every discussion rigid or require consensus on every detail.
What would you do if the feedback came from a junior engineer?
I would take the behavior and impact seriously regardless of seniority. A person with less formal influence may find it harder to raise concerns, so my response should make future feedback easier rather than turn their example into a debate about status.
Adjust the evidence to your level
Early-career
Use a bounded project, internship, or volunteer example that demonstrates receiving feedback. Explain guidance you received rather than claiming senior authority.
Mid-level
Show independent responsibility for a defined outcome, including a concern fully discussed and incorporated into a later test plan. Name dependencies and when you sought help.
Senior
Explain trade-offs with affected colleagues, the verification plan, and checking the effect of a behavior rather than relying on good intentions. Broader scope needs evidence rather than a larger job title.
Staff
Show a mechanism that changed decisions or capability across teams, including who adopted it and what remained outside your authority. Do not describe a local change as organization-wide influence.
Common mistakes
- Listing tasks without explaining why you considered defending helpful intent without changing meeting behavior.
- Claiming a concern fully discussed and incorporated into a later test plan without describing how you observed it.
- Claiming sole credit for decisions or work owned by collaborators.
- Treating a proposed follow-up as already completed.
Build your own answer
This worksheet stays in this page’s memory. It is not saved to your account or this device. Copy or download it before leaving or refreshing. Remove confidential details and use only experiences you can defend.
Self-review against observable evidence
This is a coaching checklist, not a company hiring score. Choose one rating per dimension.
Review each dimension to choose one concrete improvement for your next attempt.
Next exercise
Rehearse your own example, then ask a listener to identify a concern fully discussed and incorporated into a later test plan and the decision that led to it.
Prepare a follow-up on defending helpful intent without changing meeting behavior. Replace every fictional detail with your own facts and identify one claim that needs more evidence.