How do you respond to critical feedback?

Question

Accepted Answer

The goal is to show you treat feedback as **information, not an attack**. Strong candidates listen, ask clarifying questions, and visibly act on it.

## How to approach it

```text
1. Listen fully before reacting — don't defend yet
2. Ask for a specific example so you understand it
3. Thank the person and take a beat if it stings
4. Act on it, then close the loop later
```

## Worked example

```text
S: In a code review, a senior said my PRs were hard to follow.
T: I needed to make my changes easier to review.
A: I asked for a concrete example, learned my commits mixed unrelated changes,
   and started splitting them into small, single-purpose PRs.
R: Review time on my work dropped noticeably and the senior mentioned the
   improvement a month later.
```

## Good vs weak

| Good | Weak |
|------|------|
| Listens, clarifies, acts | Gets defensive or argues |
| Closes the loop | Nods but changes nothing |
| Treats it as a gift | Takes it personally |

## Why it matters

How you take feedback predicts how fast you'll grow.

Defensive people stop getting honest input.

Acting on feedback and closing the loop builds trust — people invest more in those who use their advice.

Early-career, your ability to absorb correction matters more than what you already know.

Good	Weak
Listens, clarifies, acts	Gets defensive or argues
Closes the loop	Nods but changes nothing
Treats it as a gift	Takes it personally