Feedback Given and Received

Topics Covered

What Feedback Questions Test

Two sides of one skill

Why feedback matters to teams

What the rubric looks for when giving

What the rubric looks for when receiving

What interviewers are worried about

Feedback at different levels

Why soft stories fail

Why harsh stories fail

Why defensive stories fail

Why superficial stories fail

Feedback and the story bank

How feedback links to other signals

What a strong answer sounds like

The word feedback itself

Common candidate fears

Preparing the details

Listening for the words

Tell me about a time you gave difficult feedback. Describe feedback you received that changed how you work. How do you give feedback to someone more senior? Feedback questions appear in most loops for mid-level engineers and above, and they become central for senior, staff and management roles. They test two sides of the same skill: whether you can tell people hard things in a way that helps them, and whether you can hear hard things without becoming defensive. This lesson covers both sides, plus feedback to managers and peers, and how strong candidates build a culture where feedback flows.

Two sides of one skill

Giving and receiving feedback are often asked about separately, but interviewers see them as connected. People who receive feedback well tend to give it well, because they know how it feels and what makes it useful. People who become defensive when criticised often give feedback that is either too soft to land or too harsh to accept. A strong set of stories shows both sides, ideally with a link between them.

Why feedback matters to teams

Engineering teams improve through feedback: code reviews, design reviews, incident reviews, one to ones and performance conversations. A team where feedback is avoided accumulates problems that nobody names until they become crises. A team where feedback is harsh loses people. Interviewers want engineers who keep feedback flowing in a healthy way, because that predicts better code, better designs and better retention.

What the rubric looks for when giving

When scoring stories about giving feedback, interviewers look for several behaviors. Did the candidate raise the issue promptly rather than letting it build? Did they prepare, with specific examples? Did they deliver it privately and respectfully? Did they focus on behavior and impact rather than character? Did they listen to the other person view? Did they agree on a next step and follow up? And did the behavior change?

What the rubric looks for when receiving

When scoring stories about receiving feedback, interviewers look for different behaviors. Did the candidate listen without arguing? Did they ask questions to understand? Did they take time to reflect rather than reacting? Did they accept the valid parts, even if they disagreed with some? Did they change something specific? And did they go back to the person or show the change? These mirror the lesson structure of a failure story.

What interviewers are worried about

Feedback questions screen for several risks. For giving: avoiding hard conversations, being harsh or personal, giving feedback in public, or giving vague feedback that changes nothing. For receiving: defensiveness, dismissing feedback, superficial acceptance with no change, or excessive distress. Senior candidates are also screened for whether they can give feedback upward and across, not just down.

Feedback at different levels

Junior candidates are expected to receive feedback well and give useful code review comments. Mid-level candidates should give constructive feedback to peers and seek feedback actively. Senior candidates should give difficult feedback to peers and junior engineers, give upward feedback to managers, and help others improve through feedback. Staff candidates should shape how feedback works on teams, give feedback to leaders and handle feedback that affects many people.

Giving and receiving were scored on mirrored behaviors, and both ended with a change someone could see.

Why soft stories fail

A common mistake when telling a giving feedback story is choosing one where the feedback was easy: I told a teammate their pull request description could be clearer, and they agreed. This shows little. Interviewers want feedback that was hard to give: about a colleague missing commitments, behaving badly in reviews, underperforming or creating friction. The difficulty is what makes the story informative.

Why harsh stories fail

The opposite mistake is a story where the feedback was delivered harshly, and the candidate presents this as admirable directness. I told him his code was a mess in front of the team, because someone had to say it. Interviewers score this badly, because it suggests the candidate damages relationships and does not understand how to make feedback land. Directness is valued, but it must come with respect.

Why defensive stories fail

When telling a receiving feedback story, some candidates choose feedback they disagreed with and spend the story explaining why it was wrong. Even if they were right, this fails the receiving check, because the interviewer hears defensiveness. Choose feedback you ultimately accepted, at least in part, and focus on what you changed. If you disagreed with some of it, say so briefly and focus on the part you accepted.

Why superficial stories fail

Another mistake is feedback received and accepted with no real change: my manager said I should speak up more in meetings, and I agreed. Without a specific change and evidence of it, the story is empty. Interviewers want to know what you did differently: I started preparing one point for each design review and sharing it in the first ten minutes, and my manager mentioned it in my next review.

Feedback and the story bank

Most candidates should have at least two feedback stories: one where they gave difficult feedback and one where they received it. Senior candidates should add a story about giving feedback upward, to a manager or leader, and possibly one about building a feedback culture on a team. Many failure stories can also serve as receiving feedback stories, if the failure was pointed out by someone else.

Feedback stories often provide evidence for other signals. Giving hard feedback shows courage and leadership. Receiving it well shows humility and growth. Giving upward feedback shows influence. Building a feedback culture shows team leadership. This is why strong feedback stories are valuable: they can be reused for questions about leadership, growth and collaboration, with the emphasis adjusted.

What a strong answer sounds like

A strong feedback answer is calm, specific and balanced. For giving: the situation and why the feedback mattered, how you prepared, what you said with a specific example, how the other person responded, what you agreed and what changed. For receiving: what you heard, how you reacted, what you asked, what you changed and how you showed it. Each takes about two minutes and ends with a visible result.

The word feedback itself

Interviewers do not always use the word feedback. They may ask about a time you had to tell someone something they did not want to hear, a time you coached a struggling teammate, or a time your manager criticised your work. Recognise these as feedback questions and use the same story structure. A prepared feedback story covers many differently worded questions.

Common candidate fears

Candidates often worry that a story about giving hard feedback will make them seem harsh, or that a story about receiving it will make them seem weak. In practice, interviewers value both. Giving hard feedback respectfully shows leadership. Receiving it well shows growth. The risk lies in the telling, not in the topic. Fair, specific and calm stories are almost always safe and strong.

Preparing the details

Feedback stories depend on specific details: the exact behavior, the example you used, the words you chose, the response and the change. Write these down before the interview. Vague memories lead to vague stories, which score poorly. If you cannot remember the specific example you used when giving feedback, the interviewer will doubt the story. Choose stories you remember clearly.

Listening for the words

Interviewers pay close attention to the exact words a candidate reports using. A story that says I told him his reviews needed work is weaker than one that quotes the framing: I said the last two reviews ended before the authors finished presenting, and asked how he saw it. Reporting your words shows preparation and lets the interviewer judge the delivery directly. Prepare the key sentence of each feedback story in advance.

Both sides, specific and followed up

Feedback questions test giving and receiving as two sides of one skill. Interviewers score prompt, prepared, private and specific delivery with a follow up, and listening, reflecting and changing when receiving. Soft, harsh, defensive and superficial stories all score poorly, so choose feedback that was hard and ended with a visible change.