What do interviewers evaluate in Critical Feedback questions?

Interviewers listen for signals like: Did you actually give the feedback, or did you complain to others / wait it out? Was the feedback specific with examples, or vague ('communication could be better')? Did you separate the behavior from the person?

gitGood.dev

GeneralAdvanced Premium

Giving Critical Feedback

Tested at every senior+ loop and every people-management interview. The signal is whether you deliver hard truths with care - or whether you avoid, soften beyond recognition, or wait for someone else to do it.

About this theme

Giving critical feedback is one of the highest-stakes interpersonal skills in engineering. The signal interviewers want: did you deliver the hard message clearly and specifically, or did you soften it past the point of usefulness? Did you do it directly to the person, or did you complain to others first? Did you separate the behavior from the person? Did you follow up? The two failure modes interviewers screen for are (1) avoidance - "I waited to see if it would resolve itself" or "I told my manager and let them handle it" without trying first, and (2) bluntness without care - "I told them they were wrong and they needed to fix it." Strong candidates land somewhere harder: they were direct about the substance, they asked permission to give the feedback, they separated the behavior from the person, they were specific with examples, they gave the recipient room to respond, and they followed up. This theme is tested at every senior+ engineering loop, every engineering manager interview, and increasingly at mid-level (L4 / E4 / IC3) loops where companies are screening for early leadership signal.

What interviewers are evaluating

→Did you actually give the feedback, or did you complain to others / wait it out?
→Was the feedback specific with examples, or vague ('communication could be better')?
→Did you separate the behavior from the person?
→Did you give the recipient room to respond, or did you deliver and leave?
→Did you follow up to see if anything changed, or was it a one-shot?
→Did the working relationship survive, or did you burn it?
→When the recipient pushed back, did you stand by the substance while engaging with their reaction?

Common prompts

Variations on these are asked at every level. Have a story pre-loaded for at least three of them.

?Tell me about a time you had to give difficult feedback to a peer.
?Describe a situation where you had to call out an underperforming colleague.
?Tell me about a time you pushed back hard on a code review or design.
?Walk me through a time you had to deliver feedback that you knew the recipient wouldn't want to hear.
?Describe a situation where you saw a peer or junior making a mistake repeatedly. What did you do?
?Tell me about a time you had to escalate a peer's behavior to their manager.
?Describe a time you gave feedback that didn't land. What did you do next?
?Tell me about a time you had to disagree with a senior engineer's technical direction in writing.

Sample STAR answers (preview)

The full library pairs strong and weak examples with notes on what makes each work (or fail). Here's how two of the strong stories open.

STRONG

Strong: Direct feedback to a peer about underperformance

Prompt: "Describe a situation where you had to call out an underperforming colleague."

Situation: About 18 months ago, I was a senior engineer on a 6-person backend team. A peer (let's call him M) had been on the team for a year. His PRs were slow to land, often required multiple review cycles for the same class of issue (test coverage, error handling), and he'd missed two recent commitments. The team was starting to assign work around him - I noticed our tech lead routing the higher-stakes work to other engineers. I'd built a working relationship with M.
Result: Over the next quarter, his PR velocity roughly doubled and the quality issues largely cleared. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

STRONG

Strong: Pushed back hard on a senior engineer's design

Prompt: "Tell me about a time you pushed back hard on a code review or design."

Situation: About two years ago, a staff engineer on a partner team published a design doc for a new internal authorization service. His proposal hardcoded role definitions in source code with deploy-required updates, citing security concerns about runtime configuration. I was a senior engineer on a team that would be a heavy consumer of the service. I disagreed strongly - I thought the deploy-required model would create exactly the security problem he was trying to avoid (teams would work around it with their own role caches, which would drift).
Result: The service shipped with the split design. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

What's in the full theme

3 full STAR answers (strong and weak, with interviewer notes) · 8 common pitfalls · 7 follow-up strategies

The full STAR library for this theme is part of Premium

Unlock it with a subscription.

Start Your 7-Day Trial

Try everything free for 7 days. Cancel anytime.

Every behavioral theme's strong and weak answers, pitfalls and follow-ups
Coach critiques on your own stories (40 a month)

View Plans

7-day trial, then $8/mo - or $48/yr ($4/mo, save 50%). Cancel anytime.

Related behavioral themes

Conflict

General

The most universal behavioral question. Tested everywhere. The signal is in how you investigate the disagreement, not in how you 'won.'

Influence

General

The senior+ signal. Can you drive cross-team work, mentor, and build consensus when nobody reports to you - or do you only execute when given a mandate?

Ownership

Amazon LP

Tested at every level, scored harder at senior. Did you take responsibility for outcomes - or just for tasks?

FREE

Companies that test this theme

Practice these stories live

Reading STAR answers is the floor. The interview signal is in delivering them out loud, with follow-ups, under pressure. Write your own Critical Feedback story first, then say it out loud in a behavioral mock - Alex reads your story bank.

Write your Critical Feedback story →Practice it in a behavioral mock →

GeneralAdvanced Premium

Giving Critical Feedback

About this theme

What interviewers are evaluating

→Did you actually give the feedback, or did you complain to others / wait it out?
→Was the feedback specific with examples, or vague ('communication could be better')?
→Did you separate the behavior from the person?
→Did you give the recipient room to respond, or did you deliver and leave?
→Did you follow up to see if anything changed, or was it a one-shot?
→Did the working relationship survive, or did you burn it?
→When the recipient pushed back, did you stand by the substance while engaging with their reaction?

Common prompts

Variations on these are asked at every level. Have a story pre-loaded for at least three of them.

?Tell me about a time you had to give difficult feedback to a peer.
?Describe a situation where you had to call out an underperforming colleague.
?Tell me about a time you pushed back hard on a code review or design.
?Walk me through a time you had to deliver feedback that you knew the recipient wouldn't want to hear.
?Describe a situation where you saw a peer or junior making a mistake repeatedly. What did you do?
?Tell me about a time you had to escalate a peer's behavior to their manager.
?Describe a time you gave feedback that didn't land. What did you do next?
?Tell me about a time you had to disagree with a senior engineer's technical direction in writing.

Sample STAR answers (preview)

The full library pairs strong and weak examples with notes on what makes each work (or fail). Here's how two of the strong stories open.

STRONG

Strong: Direct feedback to a peer about underperformance

Prompt: "Describe a situation where you had to call out an underperforming colleague."

Situation: About 18 months ago, I was a senior engineer on a 6-person backend team. A peer (let's call him M) had been on the team for a year. His PRs were slow to land, often required multiple review cycles for the same class of issue (test coverage, error handling), and he'd missed two recent commitments. The team was starting to assign work around him - I noticed our tech lead routing the higher-stakes work to other engineers. I'd built a working relationship with M.
Result: Over the next quarter, his PR velocity roughly doubled and the quality issues largely cleared. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

STRONG

Strong: Pushed back hard on a senior engineer's design

Prompt: "Tell me about a time you pushed back hard on a code review or design."

Situation: About two years ago, a staff engineer on a partner team published a design doc for a new internal authorization service. His proposal hardcoded role definitions in source code with deploy-required updates, citing security concerns about runtime configuration. I was a senior engineer on a team that would be a heavy consumer of the service. I disagreed strongly - I thought the deploy-required model would create exactly the security problem he was trying to avoid (teams would work around it with their own role caches, which would drift).
Result: The service shipped with the split design. - the full Task → Action → Result walkthrough and the "why this works" notes are in the member version.

What's in the full theme

3 full STAR answers (strong and weak, with interviewer notes) · 8 common pitfalls · 7 follow-up strategies

The full STAR library for this theme is part of Premium

Unlock it with a subscription.

Start Your 7-Day Trial

Try everything free for 7 days. Cancel anytime.

Every behavioral theme's strong and weak answers, pitfalls and follow-ups
Coach critiques on your own stories (40 a month)

View Plans

7-day trial, then $8/mo - or $48/yr ($4/mo, save 50%). Cancel anytime.

Related behavioral themes

Conflict

General

The most universal behavioral question. Tested everywhere. The signal is in how you investigate the disagreement, not in how you 'won.'

Influence

General

The senior+ signal. Can you drive cross-team work, mentor, and build consensus when nobody reports to you - or do you only execute when given a mandate?

Ownership

Amazon LP

Tested at every level, scored harder at senior. Did you take responsibility for outcomes - or just for tasks?

FREE

Companies that test this theme

Practice these stories live

Write your Critical Feedback story →Practice it in a behavioral mock →