Why This Competency Matters

Feedback questions are one of the highest-signal growth probes in the behavioural loop. The interviewer is not asking whether you have ever received feedback (everyone has). They are asking whether you can hear feedback without defensiveness, evaluate it honestly, and translate it into observable behavioural change. The single phrase that best captures what graders want is: 'evidence of change'. The candidate said the feedback landed; what changed in how they actually work?

Three signals dominate strong feedback answers:

[ Low defensiveness ]       Did you hear the feedback without flinching or rationalising?
[ Calibrated evaluation ]   Did you separate signal from noise (and disagree where warranted)?
[ Behavioural evidence ]    Did anything observable change in how you operate now?

The failure mode that dominates weak answers is performative acceptance. The candidate says all the right words about being open to feedback, naming the feedback received, naming how grateful they were for it, even naming a small behavioural tweak they made. But the answer is missing the durable evidence: there is no second story showing the new behaviour at work, no metric or observation that confirms the change held, no cost the candidate paid to make the change. The interviewer hears compliance, not growth.

The other failure mode is over-agreement. The candidate accepts every piece of feedback they have ever received as obviously correct, with no judgement applied. This reads as either lacking self-awareness (they cannot evaluate feedback critically) or as people-pleasing (they will absorb any criticism without pushback, which becomes a problem at senior levels where the right move is sometimes to disagree with feedback after honest consideration).

The strong feedback answer is built on a four-step loop: receive, process, evaluate, act. Each step is a distinct move with distinct grading criteria. The lesson below covers each step, the calibrated-agreement vs calibrated-disagreement frame, and the proactive-solicitation pattern that separates senior candidates from mid-level ones.

What Great Looks Like

Strong feedback answers tend to score on five named rubric signals.

1. The feedback was actually substantial.

The feedback hit something real about how you operate, not a one-off tactical note. Stories where the 'feedback' was 'use a different framework for this one document' fail this signal. The feedback should name a behavioural pattern, a blind spot, or a systemic gap, because that is the kind of feedback that produces durable change.

2. The receiving moment is told without defensiveness.

The candidate describes hearing the feedback in a way that makes it credible they actually heard it. Stories where the candidate immediately explains why the feedback was wrong, or where the candidate reframes the feedback in their own favour, fail this signal. The strong move is to name the feedback in the words the giver used (or close to it), without sanitising or softening, before describing what the candidate did with it.

3. The evaluation is calibrated.

The candidate did not just accept the feedback; they evaluated it. Strong evaluation language: 'I sat with it for a few days', 'I asked two trusted peers whether they had observed the same pattern', 'I checked the feedback against specific recent examples'. The candidate may have ended up agreeing fully, agreeing partially, or disagreeing with honest reasoning, but the evaluation step is visible in the telling.

4. The action is behavioural, not symbolic.

The candidate changed something observable about how they work, not just their attitude. Strong action language names a specific practice, a recurring habit, or a structural change (a checklist, a calendar block, a template). Symbolic actions ('I committed to being more mindful of this') fail this signal because they cannot be graded.

5. There is durable evidence.

The new behaviour held over time, with at least one observation that confirms it. Strong durable evidence: a second story where the new behaviour applied, a metric that changed and stayed changed, a peer or manager observation, the candidate's own reflection that the change is now reflexive. Without durable evidence, the rubric reads compliance, not growth.

At senior levels (staff and above), a sixth signal often shows up: proactive solicitation. The candidate not only acts on feedback when it arrives; they actively solicit feedback on a recurring cadence, especially on areas where they suspect they have a blind spot. This is the highest-graded variant of the competency.

The Four-Step Receive-Process-Evaluate-Act Loop

The spine of every strong feedback answer is a four-step loop. The labels matter because graders specifically listen for these moves.

1. Receive.

Hear the feedback without flinching or rationalising. The receiving move is sentence-level: ask one or two clarifying questions, name back what you heard to confirm, thank the giver. The receiving move is NOT to immediately evaluate, push back, or explain. Strong candidates separate receiving from evaluating in time: the giver says it, the candidate hears it, the evaluation happens later.

Language that signals this: 'I asked them to give me a specific recent example so I knew exactly what they meant', 'I named back what I heard to make sure I had it right', 'I thanked them and said I would think about it before responding'.

2. Process.

Sit with the feedback before acting on it. The processing move is to give yourself enough time to move past the initial emotional reaction and look at the feedback honestly. For minor feedback this can be a few hours; for substantial feedback it can be days.

Language that signals this: 'I sat with it for the weekend before I did anything with it', 'I noticed I was defensive about it on day one and curious about it on day three, so I waited', 'I wrote down my initial reaction in a notebook, then came back to it later'.

3. Evaluate.

Evaluate the feedback against evidence. The evaluation move is to check the feedback against specific recent examples, against perspectives from other trusted observers, and against your own honest assessment. The candidate may end up agreeing fully, agreeing partially, or disagreeing.

Language that signals this: 'I checked the feedback against three recent specific examples', 'I asked two trusted peers whether they had observed the same pattern', 'I distinguished between the parts of the feedback I agreed with and the parts I did not'.

4. Act.

Translate the evaluation into a specific behavioural change, with a way of knowing it worked. The action move is to pick a concrete practice, ship it, and track whether it held. The candidate's job is not just to start the change but to verify it is durable.

Language that signals this: 'I picked one specific practice and committed to it for the next quarter', 'I set up a recurring check with my manager so I would notice if I drifted', 'Six months later, three different teammates had separately noticed the change', 'The metric I cared about moved from X to Y and stayed there'.

The four-step loop is what graders listen for. Stories that compress receive, process, and evaluate into a single 'I took the feedback to heart' lose the self-awareness signal. Stories that linger on receive without ever reaching act read as introspection without behavioural change.

Calibrated Agreement vs Calibrated Disagreement

The single most common misconception about feedback questions is that the right answer is always to agree with the feedback. It is not. You are allowed to disagree with feedback after honest consideration. The rubric does not grade agreement; it grades the quality of the evaluation and the integrity of the response.

[ Over-agreement ]            'They were right; I changed my approach immediately.'
[ Reflexive disagreement ]    'I did not really agree, so I did not change anything.'
[ Calibrated agreement ]      'I agreed with the substance, disagreed on one specific framing, and changed the substance.'
[ Calibrated disagreement ]   'I considered it carefully, talked to two peers, and concluded the feedback was not right for my role; here is what I did instead.'

Calibrated agreement names which parts of the feedback you accepted and which parts you set aside, with reasoning. Calibrated disagreement names that you considered the feedback seriously, names what you checked, and names what you concluded and why.

The key sentence-level move in calibrated disagreement is to show that you took the feedback seriously before concluding you disagreed. Disagreement that comes before consideration reads as defensiveness; disagreement that comes after evidence reads as judgement. The phrasing that signals the difference: 'After thinking about it for a week and checking it against three specific examples, I concluded that the feedback applied to one situation but not as a general pattern.'

Disagreement also requires that you respect the giver of the feedback. The strong move is to acknowledge the giver's perspective, name what you understood about why they saw it that way, and then explain your conclusion. The weak move is to dismiss the feedback or characterise the giver as wrong.

Behavioural Evidence: What Change Actually Looks Like

The highest-graded signal in this competency is behavioural evidence. The interviewer wants to know that the feedback produced durable change, not just acceptance of the feedback. Behavioural evidence comes in five forms.

1. A second story. The candidate tells the feedback story, then tells a second story where the new behaviour was applied. The second story does not need to be long; it just needs to show the new behaviour at work in a different situation.

2. A measurable shift. A metric the candidate cares about moved and stayed moved. The metric should be observable to others (response time on PRs, number of one-on-ones with directs, time-to-first-design-review-comment), not just internal to the candidate.

3. A structural change. The candidate built a structural artefact that institutionalises the new behaviour: a checklist before sending design documents, a recurring calendar block for the new practice, a template that prompts the new behaviour automatically.

4. An external observation. A peer, manager, or report has observed the change and named it. Strong language: 'My manager mentioned the shift at the next quarterly review without prompting', 'A teammate told me they had noticed the change'.

5. The candidate's own reflexive use. The candidate describes the new behaviour as something they now do automatically. The change has moved from deliberate to reflexive, which is the deepest form of durable change.

Weak feedback answers omit all five and rely on the candidate's claim that they took the feedback seriously. Strong answers include at least two of the five.

Proactive Solicitation: The Senior-Level Variant

At senior levels, the highest-graded variant of this competency is proactive solicitation. The candidate not only acts on feedback when it arrives; they have built a practice of actively soliciting feedback, especially on areas where they suspect they have a blind spot.

Proactive solicitation patterns that score:

• Recurring one-on-one ask: 'I close every monthly one-on-one with my manager by asking what they would change about how I am operating.'
• Project retrospective ask: 'After every major project, I ask three people I worked with closely for one specific thing I should change next time.'
• Blind-spot specific ask: 'I know my historical blind spot is over-engineering; once a quarter I ask a peer to review a recent design and tell me where I overshot.'
• Calibrated trust circle: 'I have three peers I trust to give me unfiltered feedback; I check in with them every six months.'

The distinguishing feature of proactive solicitation is that the candidate is not waiting for feedback to surface; they are creating the conditions for it to surface. This is the senior-level move because it shows the candidate has internalised that feedback is a tool they own, not an event that happens to them.

For a staff-level candidate, having at least one proactive-solicitation example in the answer (even briefly, after the main story) is a meaningful rubric uplift. For a senior candidate, it is increasingly expected.

Common Questions & Model Answers

The six prompts below cover roughly 95% of how this competency is probed. Each model answer is a two-to-three-minute STAR answer that scores on the rubric above.

Prompt 1: 'Tell me about a time you received tough feedback.'

Model answer (strong, peer feedback on writing-then-asking pattern)

'In Q2 2023 I was a senior engineer on our payments-platform team. I had been at the company for about 18 months and had built a reputation for shipping reliably on technical work. In a peer-feedback round my closest collaborator on the team gave me a piece of feedback that genuinely surprised me: she said that when I had questions about scope or direction, I tended to write a long document with my proposed answer, share it with the team, and then ask for input, rather than asking the team for input first and then writing the document. She said the pattern made the team feel like the document was a fait accompli, not a real invitation, and that two recent design discussions had landed worse because of it.

The receiving moment was uncomfortable. My initial reaction was to explain that I wrote the document because that was how I thought through the problem, and that the document was meant as a starting point, not a final answer. I noticed the defensiveness and held it. I asked her for two specific recent examples so I was sure I understood exactly what she meant. She named two recent design documents where she had felt that even though I had asked for input, the document was already so detailed that the input space was narrow. I thanked her and told her I would think about it before responding.

I sat with it for about a week. The first three days I was mostly defensive about it. By day four I was curious about it: I went back and looked at the two documents she had named, and I could see what she meant. The documents had been about 70% formed when I shared them; the input space was effectively the remaining 30%. I asked one other peer whether he had observed the same pattern. He had, on a different document. The evidence was clear; my evaluation was that the feedback was substantively right, even though I had not been intending the pattern.

What I changed. I picked one specific practice and committed to it: for any design document where I had multiple plausible directions, I would write a one-page problem framing first (no proposed solution), share it for input, wait at least 48 hours, and then write the longer document with proposed direction. The one-page framing made the input space wide, and the 48-hour wait made it real (not 'I will write the document tomorrow regardless'). I tracked whether the pattern held: every design document for the next two quarters started with the one-page framing.

The durable evidence came about six months later. In a later peer feedback round the same colleague said the documents had felt much more collaborative, and named one specific recent design where her input early in the framing had shifted the direction in a way she thought was important. My manager also mentioned the shift in a quarterly review without prompting. The new practice has become reflexive; I have not consciously thought about the change in the past six months, but the one-page framing is still how I start design work.

What I learned. The feedback was about a pattern I had not been able to see in myself, because each individual document had felt collaborative to me. I needed an outside observer to name the pattern, and I needed to check it against specific recent examples before I could see it. I have since added a quarterly ask to my one-on-ones with two trusted peers: 'name one pattern you have seen in my work in the last quarter that I might not be seeing.' Two of the three subsequent quarters have produced useful patterns; one has produced 'no, you are tracking well right now', which is also useful.'

What lands: substantial feedback (a behavioural pattern, not a tactical note), receiving moment told with the defensiveness named honestly and held, processing time visible (a week), evaluation against specific examples and a second observer, behavioural action that is concrete (one-page framing, 48-hour wait), durable evidence in three forms (a second peer observation, manager observation, candidate reflexive use), and a proactive-solicitation practice that came out of the experience.

Prompt 2: 'Walk me through a piece of feedback that changed how you work.'

Model answer (strong, manager feedback on PR review depth)

'About two years ago I was a mid-senior engineer on an infrastructure team. My manager pulled me aside after a quarterly review and said something I have thought about often since. He said that I was reviewing PRs fast (I was usually the first reviewer to respond, often within an hour), but my reviews were shallow: I was catching syntax and obvious bugs, but I was not catching architectural drift, and the team had merged three changes in the previous quarter that had ended up costing us refactoring work because no reviewer had pushed back at review time. He named me as the most-frequent first-reviewer who had let those changes through.

The receiving moment was hard because I had taken pride in being a fast reviewer. My initial reaction was to think that fast reviews were a service to the team, and that the architectural drift was a separate problem. I let that reaction sit for a day before responding. The next morning I asked him to walk me through the three specific changes he had in mind. He pulled them up; I read each one and the subsequent refactoring it had caused. In all three, with hindsight, the architectural drift was visible in the PR diff. I had been reviewing the syntax and the obvious correctness, not the architectural shape.

I sat with the feedback for about a week. I checked it against my last 30 reviews; in roughly 8 of them, I could see places where I should have pushed back on architectural choices and had not. The pattern was real. My evaluation was that the feedback was substantively right, but with one nuance I wanted to name: my fast-review pattern had been net-positive for the team in some ways (unblocking changes quickly), and the right move was not to slow down all reviews to architectural depth but to differentiate.

What I changed. I introduced a two-mode review practice. Mode 1 was fast tactical review for routine changes (small fixes, dependency bumps, mechanical refactors); these I could still do in under an hour. Mode 2 was deep architectural review for changes that touched core abstractions, introduced new patterns, or crossed component boundaries; these I would explicitly take longer on (often a half-day) and would push back on architectural choices when I had concerns. I built a small mental checklist for which mode a PR was in, looking at the file paths and the diff size as the first signal.

The shift took about two months to feel natural. By month three, I was catching architectural concerns at review time on roughly 20% of substantial PRs. Over the following two quarters, the team had no incidents of architectural drift attributable to a missed review. My manager mentioned the shift in the next two quarterly reviews; he had specifically noticed two PRs where I had pushed back on architectural choices and the original author had taken the feedback and improved the design.

What I learned. Speed and depth are different review qualities, and I had been optimising for speed without recognising the cost. The discipline of differentiating between tactical and architectural review modes is something I have applied on every team since; I now teach it to engineers I mentor, framed as 'know which kind of review the PR needs and adjust your time budget'. The original feedback also taught me to evaluate my own work patterns against the team-level outcomes they produced, not just against my own perception of the patterns.'

What lands: substantial feedback (a pattern in review behaviour with team-level cost), receiving moment without defensiveness despite the candidate's pride, processing time visible (a week, with the cross-check against 30 recent reviews), calibrated evaluation that agreed with substance but added a nuance about differentiating, behavioural action that is concrete and structural (two-mode review with a checklist), durable evidence on multiple fronts (a metric on architectural concerns caught, manager observation across two reviews, candidate continuing to apply the pattern on subsequent teams).

Prompt 3: 'Describe a piece of feedback you disagreed with and how you handled it.'

Model answer (strong, calibrated disagreement on communication style)

'About three years ago I received feedback from a senior leader, two levels above me, in a skip-level review. He said I should be 'more decisive' in meetings; specifically, he had observed that in a few cross-team meetings I had said 'I think the right move is X, but I want to hear other perspectives' rather than 'the right move is X', and he thought the hedging undermined my authority.

The receiving moment was uncomfortable, but for a different reason: I had a strong gut sense that the feedback was wrong, and I wanted to be careful not to dismiss it because of that gut sense. I thanked him for the feedback, asked him for one specific recent example so I knew what he meant, and told him I would think about it.

I sat with it for about two weeks; this was a longer processing window than usual, because I wanted to make sure I was not just being defensive. I asked three trusted peers (one on my team, one cross-team, one in a previous role) whether they had observed the pattern, and what they thought of it. All three said they had observed the pattern. Two of the three said they thought it was a strength: in cross-team meetings the explicit invitation for other perspectives often surfaced concerns that mattered. One of the three said he thought the senior leader had a point in some specific contexts (when speaking to executives who wanted directional clarity), but that the pattern was net-positive in the engineering and cross-team contexts where I spent most of my time.

My evaluation was that the feedback was partially right but largely wrong. In the specific context the senior leader had observed (an exec-level meeting on strategy), the hedging probably had cost me, because exec-level audiences are looking for directional clarity. In the broader pattern (cross-team and engineering meetings), the explicit invitation for other perspectives was load-bearing for the kind of work I did, and removing it would change the actual outcomes of the meetings, not just the perception.

What I did. I went back to the senior leader and named my conclusion. I told him I had taken the feedback seriously, asked three peers about the pattern, and concluded that I would adjust my approach in exec-level meetings (where I would lead with the recommendation and then surface alternatives if asked) but would keep the explicit invitation pattern in cross-team and engineering meetings, because it was producing better decisions in those contexts. I named the specific contexts and the specific reasoning. He pushed back briefly, then said he could see the distinction, and that he was glad I had thought about it carefully rather than just deferring.

The exec-level adjustment was real and durable. I tracked it for about six months and the new pattern was consistent. The cross-team pattern stayed the same; that pattern was the right tool for the work, and changing it would have produced worse decisions.

What I learned. Senior people are not always right, and the strong move with feedback you suspect is wrong is to take it seriously enough to check rigorously, then commit to your conclusion if the evidence supports disagreement. The disagreement has to be earned by the rigour of the evaluation; reflexive disagreement is just defensiveness. I have used this approach twice more since: once where I ended up agreeing more than I had initially expected, and once where I disagreed and went back to the giver with the same kind of named reasoning. Both produced better outcomes than reflexive responses would have.'

What lands: real disagreement that is earned, not reflexive (the candidate explicitly names the gut reaction and the discipline of not dismissing the feedback because of it), evaluation rigour visible (three peers, two-week processing, partial agreement on one context with disagreement on another), respectful return to the feedback giver with named reasoning, the candidate's calibrated authority in disagreeing with someone two levels above, and a durable practice the candidate continues to apply.

Prompt 4: 'Tell me about feedback you gave that was hard for someone to hear.'

Model answer (strong, giving feedback to a peer with seniority sensitivity)

'About a year ago I was a senior engineer working closely with a peer who had recently been promoted to staff. He was a strong engineer, but I had observed a pattern in design reviews where he would push back hard on more-junior engineers' proposals, often with strong language, and the more-junior engineers had started to avoid bringing their designs to him. Two engineers had separately mentioned to me that they were routing around him on design feedback, which meant he was not seeing their work and they were missing his perspective. The pattern was costing him and them.

The receiving question is the inverse here: how did I deliver feedback that I knew would be hard for him to hear, given that he was newly promoted and I was a peer?

I planned the conversation carefully. I asked him for a 30-minute coffee, framed it as 'I have something I would like to share with you about a pattern I have noticed; it is hard feedback and I want you to know I am sharing it because I think it matters'. He agreed.

In the conversation, I started by naming the specific pattern I had observed, with two recent examples (anonymised, but specific enough that he would recognise them). I named the two engineers who had separately mentioned routing around him (with their permission). I told him my hypothesis about the pattern: that his pushback was substantively often correct, but the strength of the language was deterring people from bringing him their work, which meant the substantive correctness was not landing because the work was not arriving. I was explicit that I did not want him to soften his standards; I wanted him to deliver the same standards in language that did not cost him the access.

He was visibly uncomfortable at first; this was hard feedback to receive from a peer, soon after a promotion that was supposed to validate his approach. He thanked me for raising it and asked for time to think about it. I told him I was happy to talk further whenever he wanted.

About a week later he came back. He had thought about it, talked to one of the two engineers I had mentioned, and concluded that the feedback was substantively right. He named one piece of context he wanted to add: he had been pushing back hard partly because he was new to the staff role and was overcompensating to demonstrate the role's standards. We talked through what specific language patterns might land differently. Over the following two months, the pattern shifted noticeably; both engineers who had been routing around him started bringing him design work again, and one of them mentioned to me that the recent design feedback she had received from him had been the most useful she had had from anyone.

What I learned. Giving hard feedback to a peer requires the same care you would want as the receiver. The specific moves that mattered: ask for the right setting (a private coffee, not a chat channel), name that the feedback is hard so the receiver knows what is coming, ground the feedback in specific examples rather than impressions, separate substance from delivery (so the receiver does not feel the substance is being attacked), and end with a clear path forward rather than just the criticism. I have given hard feedback four or five times since with the same template; one of those conversations did not produce change, which I suspect was because I had not grounded the feedback in specific-enough examples.'

What lands: a feedback-giving story that demonstrates the candidate has internalised what makes feedback land, the specific moves of preparation visible (right setting, naming the difficulty, specific examples, separation of substance from delivery), the receiver's processing arc visible without claiming credit for the receiver's growth, calibrated honesty about a subsequent conversation that did not produce change.

Prompt 5: 'Walk me through how you solicit feedback proactively.'

Model answer (strong, senior-level proactive solicitation pattern)

'I have built a deliberate feedback practice over about the last four years, after a stretch where I realised I was only getting feedback when something had gone wrong, which meant the feedback signal was both lagging and biased toward problems. The practice has four components.

First, the recurring one-on-one ask. I close every monthly one-on-one with my manager with one question: 'what is one thing you would change about how I am operating right now?' The phrasing is deliberate. 'One thing' makes the question answerable; without it, managers tend to default to 'you are doing great, no notes', which is not useful. 'Change' (rather than 'improve') signals I am not asking for praise. I have done this with three managers over the four years; each has eventually given me substantive feedback they would not have given unprompted.

Second, the project retrospective ask. After every major project (anything over six weeks), I ask three people I worked with closely for one specific thing I should do differently next time. I ask in writing, not in a meeting, because the writing format produces more thoughtful answers. I ask three people because the patterns across three perspectives are more useful than a single perspective, and one of the three usually gives me something I did not get from the others.

Third, the blind-spot specific ask. I have a list of two or three areas where I suspect I have blind spots; once a quarter I ask a peer who has good visibility into one of those areas to look at recent work and give me one observation. The recent areas I have asked about: whether I am over-engineering, whether my one-on-one cadence with my directs is right, whether my technical writing is too dense for the audience.

Fourth, the calibrated trust circle. I have three peers I trust to give me unfiltered feedback. I check in with them every six months. Two of them have known me for more than five years; one is a more recent relationship. The check-in is informal, usually a 30-minute coffee, and the question I ask is 'has anything changed about how I am operating that I should know about'. The depth of the relationships means the answers are honest in ways that newer relationships are not.

The combined effect of the four practices is that feedback signal arrives steadily, not just in moments of crisis. I now have probably four to six substantive feedback inputs per quarter. Maybe one in three produces a behavioural change; the rest either confirm I am tracking well or produce smaller adjustments. The compounding effect over four years has been substantial: several of the patterns I have changed in that time would not have surfaced through any single feedback event.

The most recent change came from the project retrospective ask after a six-month platform-migration project. Two of the three respondents independently mentioned that I had been too cautious about reaching out to teams whose services we were migrating, and that the early phase of the project had been slower than it needed to be because of it. The pattern had not been visible to me; I had thought I was being careful. I changed my default on the next migration to reach out earlier and more directly; the early phase of that migration ran about three weeks faster.'

What lands: a senior-level proactive-solicitation practice with four named components, each with the specific phrasing and rationale, durable evidence (four years of practice, with a recent specific example of a behavioural change that came out of it), no claiming of credit for managers or peers giving the feedback, the candidate's framing positions feedback as a tool they own rather than an event that happens to them.

Prompt 6: 'Tell me about feedback that surprised you.'

Model answer (strong, blind-spot feedback with calibrated agreement)

'About 18 months ago I received feedback from a direct report (I was technically not their manager, but I was the senior engineer they did most of their work with) that genuinely caught me by surprise. In a one-on-one I had asked her for one piece of feedback on how I was supporting her work, and she said: 'I think you are too quick to give me solutions. When I bring you a problem, you usually have an answer in the first two minutes, and even when the answer is good, the speed makes me feel like there was no point in me thinking about it first.'

The feedback surprised me because I had thought my fast answers were a service. The direct reports I had worked with previously had often told me that the fast answers were what they liked. I had not considered that the same behaviour would land differently with different people, and I had not asked her how she preferred to work.

The receiving moment was specifically structured by the surprise. I noticed myself wanting to explain why I had been giving fast answers, and I held that. I asked her one clarifying question (whether the issue was the speed itself, or the lack of room for her to think first), and she said it was the lack of room. I thanked her and said I would think about it.

I sat with it for a few days. The first thing I noticed when I checked recent interactions was that she had stopped bringing me certain kinds of questions over the previous month; I had thought she had grown more confident, but I now suspected she had stopped because the interaction was not useful to her. The evaluation was unambiguous: she was right about the pattern, and I had been blind to it because the people I had previously worked with had different preferences.

What I changed. The change was specifically calibrated to her preferences (not to a universal new approach). When she brought me a problem, I would explicitly ask 'do you want me to give you my read, or do you want to think out loud first and have me push back?' before responding. The framing made the choice hers; the speed of my read was not the issue, the absence of her option was.

The shift took about a month to feel natural. Within two months she was bringing me a wider range of problems again, and the conversations were producing better outcomes for her work. About six months later she mentioned in a one-on-one that the change had been one of the things that had made our working relationship work; I had not realised the prior dynamic had been costing her that much.

The broader pattern I learned: I had been treating my support style as a single consistent thing, when actually different reports and peers worked best with different styles. I now ask new collaborators in the first two or three weeks how they prefer to think through problems together. The question itself is a small thing; the pattern of asking it has reshaped how I work with about a dozen people since.'

What lands: feedback that genuinely surprised the candidate (not pre-known), the surprise itself examined honestly (the candidate's prior assumption, the failure to ask about preferences), an evaluation that uses recent specific evidence (the report had stopped bringing certain questions), behavioural action that is calibrated to the specific person rather than a universal change, durable evidence (six-month observation from the report), and a broader pattern the candidate has generalised since.

Prompt 7 (weak / contrast answer): 'Tell me about a time you received tough feedback.'

Weak answer (performative acceptance, no behavioural evidence)

'A few years ago my manager told me I needed to communicate better with the team. I took the feedback to heart and I became really focused on improving my communication. I started being more proactive about updates, and I really worked on being a better listener. I think feedback is a gift, and I try to be open to it whenever I can. I am always looking to grow as an engineer.'

Why this fails the rubric: the feedback is unsubstantial and unspecific (what was the actual communication problem?), there is no receiving moment told (just 'I took it to heart'), no processing or evaluation visible, the action is symbolic rather than behavioural ('focused on improving' is not a practice), and there is no durable evidence. The closing platitude ('feedback is a gift') is the kind of phrase candidates use when they have nothing concrete to report.

Weak answer (over-agreement, no evaluation)

'I once received feedback that I was being too aggressive in code review. I immediately recognised the giver was right and I changed my entire approach. I now make sure to be supportive in every code review, and I have not received that feedback again.'

Why this fails the rubric: the candidate did not evaluate the feedback at all (they 'immediately recognised the giver was right'), there is no processing time, no calibration about what aspects of the feedback were right or wrong, the action is described as a wholesale change ('changed my entire approach') rather than a calibrated practice, and the durable evidence ('have not received that feedback again') could just mean people stopped giving it. The over-agreement reads as people-pleasing or as low judgement.

Pitfalls Specific to This Competency

Five traps that show up most often in feedback stories.

1. Performative acceptance without behavioural evidence. The candidate says all the right words about being open to feedback, names the feedback, even names a small change, but the answer is missing the durable evidence. There is no second story showing the new behaviour, no metric, no observation. The interviewer hears compliance, not growth. The fix is to make sure every feedback story has at least two of the five behavioural-evidence forms (second story, measurable shift, structural change, external observation, candidate reflexive use).

2. Over-agreement with no evaluation. The candidate accepts every piece of feedback as obviously right, with no judgement applied. This reads as either lacking self-awareness (they cannot evaluate critically) or as people-pleasing. The fix is to show the evaluation step explicitly: 'I sat with it for X days', 'I asked two trusted peers whether they had observed the same pattern', 'I checked it against three specific recent examples'. The evaluation does not have to end in disagreement; it just has to be visible.

3. Reflexive disagreement that reads as defensiveness. The candidate disagrees with the feedback without showing they took it seriously first. Disagreement that comes before consideration reads as defensiveness; only disagreement that comes after evidence reads as judgement. The fix is to make the consideration visible: name the processing time, name what you checked, name the specific contexts where the feedback applied or did not apply.

4. Symbolic action instead of behavioural action. The candidate's response to the feedback is to commit to an attitude rather than a practice ('I committed to being more mindful', 'I became more focused on'). Symbolic actions cannot be graded. The fix is to name a specific practice (a checklist, a recurring time block, a phrasing template), name the trigger that activates it, and name the way you tracked whether it held.

5. Defensiveness in the receiving moment. The candidate describes hearing the feedback in a way that immediately frames it in their favour, or rationalises why the giver had it wrong, or sanitises what was actually said. The receiving moment should be the most uncomfortable part of the answer, not the easiest. Strong candidates name the giver's words closely, name their own initial reaction (often defensive or surprised), and show that they held the reaction rather than acted on it.

Practice Prompts & Exercises

For each prompt below, draft a 300 to 400 word STAR answer using the four-step receive-process-evaluate-act loop. For every story, mark explicitly: the receiving moment with the giver's words close to verbatim, the processing time and what was happening internally, the evaluation step with at least one external check, the behavioural action as a specific practice, and the durable evidence in at least two of the five forms.

1. Tell me about a time you received tough feedback.
2. Walk me through a piece of feedback that changed how you work.
3. Describe a piece of feedback you disagreed with and how you handled it.
4. Tell me about feedback you gave that was hard for someone to hear.
5. Walk me through how you solicit feedback proactively.
6. Tell me about feedback that surprised you.
7. Describe a time a piece of feedback turned out to be wrong.

For every story, also do the language audit. Read the answer out loud and ask: does the receiving moment include the giver's words honestly, or has it been sanitised? does the processing step include real time and a moment of held defensiveness, or has it been smoothed? does the evaluation include at least one external check, or is it just the candidate's own conclusion? is the action a specific practice, or is it symbolic? is the durable evidence in at least two of the five forms? Strong answers are uncomfortable in the receiving moment, calibrated in the evaluation, concrete in the action, and externally validated in the evidence.

Bridge / Cross-References

This lesson opens the Growth & Mentorship category. The most useful Foundations companions:

• strengths-and-weaknesses is a close prerequisite. The self-awareness signal there is the same one this lesson applies to feedback specifically. The calibrated language patterns transfer directly.
• post-interview-reflection shares the pattern of treating reflection as a structured practice rather than an ad-hoc activity. The four-step loop in this lesson and the post-interview-reflection structure use the same skeleton applied to different inputs.
• handling-failure (in the Resilience & Adaptability category) pairs naturally; both reward calibrated honesty about something the candidate did not get right and both reward visible behavioural change.
• crafting-compelling-stories is essential for the receiving-moment scene-setting; the moment where the giver delivers the feedback should be told with the same specificity as a failure or conflict scene in those stories.

The next two lessons in this category build directly on this one. mentoring-others is the inverse competency: where this lesson is about acting on feedback you receive, mentoring is about creating the conditions for someone else's growth (which often involves giving them feedback). continuous-learning extends the growth-mindset signal beyond feedback into deliberate skill development. Together the three lessons cover the growth axis of behavioural interviews: the candidate as a learner, the candidate as a teacher, and the candidate as a self-driven developer of capability.