Respond to Critical Feedback and Show the Change

Quick Overview

Prepare a behavioral interview story about receiving critical feedback, evaluating the underlying concern, and making a concrete change. Show how later evidence tested whether the adjustment helped while acknowledging any remaining area for improvement.

Respond to Critical Feedback and Show the Change

Company: Meta

Role: Software Engineer

Category: Behavioral & Leadership

Difficulty: hard

Interview Round: Onsite

## Question Tell me about a time you received critical feedback about your engineering work or working style. What was the feedback, how did you evaluate it, what did you change, and what evidence showed whether the change helped? Choose feedback that required a real adjustment rather than a one-line correction. It is acceptable to explain that part of the feedback was incomplete or that you ultimately chose a different remedy, but show that you investigated it before rejecting any part. ### Constraints & Assumptions - Describe the feedback accurately and without attacking the person who gave it. - Explain your initial reaction honestly, then focus on the actions taken after that reaction. - Separate understanding the feedback, deciding on a response, practicing the change, and measuring its effect. - Use evidence you can support, such as later review comments, observed team behavior, or a comparison with subsequent work. Do not invent a metric to make the story sound stronger. - Include one limitation or remaining area for improvement. ### Clarifying Questions to Ask - Would you prefer feedback about technical decisions, communication, execution, or collaboration? - May I use an example where I disagreed with part of the proposed fix but accepted the underlying concern? - How much detail should I give about the later work used to assess the change? ```hint Separate the signal from the suggested remedy The person giving feedback may correctly identify an impact even when their proposed fix is not the only answer. Restate the observed impact first, then evaluate possible changes. ``` ```hint Show the next repetition The story becomes credible when you describe a later design, review, incident, or collaboration where you deliberately practiced the new behavior and observed the result. ``` ### What a Strong Answer Covers - The setting, the exact behavior being criticized, and its impact on another person, the team, or the system. - A non-defensive effort to understand the feedback through examples and questions. - Thoughtful evaluation of the underlying signal, including any evidence that changed the candidate's view. - A concrete behavioral or process change rather than a promise to “communicate better.” - Deliberate practice on later work and evidence that the change improved the original impact. - Follow-up with the feedback giver or affected collaborators when appropriate. - A balanced reflection that neither dismisses the feedback nor turns one criticism into a claim of complete transformation. ### Follow-up Questions 1. What was your immediate reaction, and what kept it from controlling your response? 2. Which example from the feedback was hardest to accept? 3. How did you decide what to change rather than overcorrecting? 4. What evidence would have shown that your change was not working? 5. What feedback on the same topic would still be fair today?

Quick Answer: Prepare a behavioral interview story about receiving critical feedback, evaluating the underlying concern, and making a concrete change. Show how later evidence tested whether the adjustment helped while acknowledging any remaining area for improvement.

|Home/Behavioral & Leadership/Meta
Meta logo
Meta
Aug 3, 2026, 12:00 AM
hardSoftware EngineerOnsiteBehavioral & Leadership
0
0

Question

Tell me about a time you received critical feedback about your engineering work or working style. What was the feedback, how did you evaluate it, what did you change, and what evidence showed whether the change helped?

Choose feedback that required a real adjustment rather than a one-line correction. It is acceptable to explain that part of the feedback was incomplete or that you ultimately chose a different remedy, but show that you investigated it before rejecting any part.

Constraints & Assumptions

  • Describe the feedback accurately and without attacking the person who gave it.
  • Explain your initial reaction honestly, then focus on the actions taken after that reaction.
  • Separate understanding the feedback, deciding on a response, practicing the change, and measuring its effect.
  • Use evidence you can support, such as later review comments, observed team behavior, or a comparison with subsequent work. Do not invent a metric to make the story sound stronger.
  • Include one limitation or remaining area for improvement.

Clarifying Questions to Ask Guidance

  • Would you prefer feedback about technical decisions, communication, execution, or collaboration?
  • May I use an example where I disagreed with part of the proposed fix but accepted the underlying concern?
  • How much detail should I give about the later work used to assess the change?

What a Strong Answer Covers Guidance

  • The setting, the exact behavior being criticized, and its impact on another person, the team, or the system.
  • A non-defensive effort to understand the feedback through examples and questions.
  • Thoughtful evaluation of the underlying signal, including any evidence that changed the candidate's view.
  • A concrete behavioral or process change rather than a promise to “communicate better.”
  • Deliberate practice on later work and evidence that the change improved the original impact.
  • Follow-up with the feedback giver or affected collaborators when appropriate.
  • A balanced reflection that neither dismisses the feedback nor turns one criticism into a claim of complete transformation.

Follow-up Questions Guidance

  1. What was your immediate reaction, and what kept it from controlling your response?
  2. Which example from the feedback was hardest to accept?
  3. How did you decide what to change rather than overcorrecting?
  4. What evidence would have shown that your change was not working?
  5. What feedback on the same topic would still be fair today?
Loading comments...