Behavioral questionMedium~8 minReal Project Scenarios / 15 of 18

Interview question

Tell me about a time you received difficult feedback. What did you do with it?

Receive hard feedback and improve

Builds a story about taking feedback seriously and changing behavior in a visible way.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I received feedback that my PRs were technically solid but too large and hard to review. My first reaction was to explain why the work was connected, but after looking at the review history I saw the pattern. Reviewers were taking longer, and comments mixed feature behavior with cleanup. I changed by splitting work into smaller PRs: one behavior change, one focused refactor, and clear notes about what to review.

Full answer below

Practice focus

Coachability, reflection, behavior change, humility, accountability, and measurable improvement.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
This question checks whether growth shows up in behavior, not only in a polished apology. The story needs a real change that other people could notice.
I received feedback that my PRs were technically solid but too large and hard to review. My first reaction was to explain why the work was connected, but after looking at the review history I saw the pattern. Reviewers were taking longer, and comments mixed feature behavior with cleanup. I changed by splitting work into smaller PRs: one behavior change, one focused refactor, and clear notes about what to review.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I also started adding a short PR description with the risk areas, test notes, and screenshots where relevant. That made it easier for reviewers to focus. The next few reviews were faster and had better feedback because people were not trying to understand a whole mini-release in one diff. I asked the teammate who gave the feedback whether the new shape was easier to review, and they said it was. I also watched my next few PRs for the same pattern, because one improved review does not prove the habit changed.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
The lesson was that good code is not enough if the collaboration cost is too high. Feedback about process can feel personal, but it often points to a real team bottleneck. Since then I pay attention to reviewability as part of delivery quality. I still do larger changes when needed, but I explain the structure and look for seams to make the review safer. I would also thank the person later after the change helped, because that makes future feedback easier to give and receive.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Turning feedback into a defense of intentions.
Describing feedback but no behavior change.
Choosing a harmless example with no real discomfort.
Claiming improvement without any evidence.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot name what changed afterward.
Blames the person who gave feedback.
No follow-up to see whether the change helped.
The same behavior continues in the story.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What made the feedback hard to hear?
What did you change specifically?
How did you know the change worked?

Continue the section

Next in Real Project Scenarios: Conflicting Priorities

Step 16 of 18

Handle conflicting priorities

Opening drill

Behavioral questionMedium~8 minReal Project Scenarios / 15 of 18

Interview question

Tell me about a time you received difficult feedback. What did you do with it?

Receive hard feedback and improve

Builds a story about taking feedback seriously and changing behavior in a visible way.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Coachability, reflection, behavior change, humility, accountability, and measurable improvement.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
This question checks whether growth shows up in behavior, not only in a polished apology. The story needs a real change that other people could notice.
I received feedback that my PRs were technically solid but too large and hard to review. My first reaction was to explain why the work was connected, but after looking at the review history I saw the pattern. Reviewers were taking longer, and comments mixed feature behavior with cleanup. I changed by splitting work into smaller PRs: one behavior change, one focused refactor, and clear notes about what to review.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I also started adding a short PR description with the risk areas, test notes, and screenshots where relevant. That made it easier for reviewers to focus. The next few reviews were faster and had better feedback because people were not trying to understand a whole mini-release in one diff. I asked the teammate who gave the feedback whether the new shape was easier to review, and they said it was. I also watched my next few PRs for the same pattern, because one improved review does not prove the habit changed.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
The lesson was that good code is not enough if the collaboration cost is too high. Feedback about process can feel personal, but it often points to a real team bottleneck. Since then I pay attention to reviewability as part of delivery quality. I still do larger changes when needed, but I explain the structure and look for seams to make the review safer. I would also thank the person later after the change helped, because that makes future feedback easier to give and receive.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Turning feedback into a defense of intentions.
Describing feedback but no behavior change.
Choosing a harmless example with no real discomfort.
Claiming improvement without any evidence.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Cannot name what changed afterward.
Blames the person who gave feedback.
No follow-up to see whether the change helped.
The same behavior continues in the story.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What made the feedback hard to hear?
What did you change specifically?
How did you know the change worked?

Continue the section

Next in Real Project Scenarios: Conflicting Priorities

Step 16 of 18

Handle conflicting priorities

Tell me about a time you received difficult feedback. What did you do with it?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Tell me about a time you received difficult feedback. What did you do with it?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section