Negative feedback interview questions: how to answer both kinds

In a job interview, a negative feedback question usually comes in one of two forms: tell me about negative feedback you received, or tell me about a time you gave it. If you're asked about feedback you received, pick real feedback you could fix and say briefly how you took it. Spend most of the answer on what you changed and what happened next. If you're asked about feedback you gave, show that you named one specific behavior, its impact and a next step, in private and with respect.

Updated

Which negative feedback question you are facing

Find yours first, because each one calls for a different answer.

The question comes in many wordings. You might hear “Describe the most difficult feedback you've received,” “Tell me about constructive criticism you got,” “How do you respond to criticism?” or “Tell me about a time your manager was unhappy with your work.” They all ask the same thing, so one well-practiced story covers them all. It belongs with the other behavioral interview questions about conflict, failure and teamwork, and you can often reuse parts of the same stories.

Four meanings of a negative feedback interview

Four meanings of a negative feedback interview
SituationWhat you hearWhat your answer showsWhere to go on this page
You received feedbackTell me about a time you got negative feedback.You listened, changed something and can show the result.Sample answers, weak versus strong, follow-ups
You gave feedbackHow do you handle giving negative feedback?You were direct, specific and kind, and it worked.When they ask how you give negative feedback
The feedback is about you, nowThe interviewer corrects you, or you are turned down.You stay calm, ask one specific question and use the answer.When the interviewer gives you negative feedback
You are on the hiring team giving feedback to candidatesA candidate asks why they did not move forward.Your note is short, specific and tied to what you assessed.For hiring teams: giving candidates negative feedback

What a strong answer shows, and a structure to use

Can you name a real gap in your own work? Did you change after hearing about it? Can you talk about it without blaming anyone? Can you tell the story clearly in about 2 minutes?

Use STAR (Situation, Task, Action, Result), but shift the weight. Keep the setup to about 20 seconds. Spend most of your time on what you did after the feedback and what changed. A story that is mostly setup can sound like you are still explaining why the feedback was wrong.

Use these 6 steps, in order:

  • Context: one sentence on where you were and what you were working on.
  • The feedback: quote it the way you heard it, or close to it.
  • Your reaction: one honest line, then what you did to understand it, such as asking for an example.
  • What you changed: 2 or 3 concrete steps, said with I, not we.
  • The result: something another person could see, such as a faster decision or fewer errors. Use a number only if you know it is true.
  • What stuck: the habit you still have today.

How to pick feedback of the right size

The best feedback for this answer is real, specific and already fixed. If it's too small, it sounds made up. If it's too big, the interviewer starts to wonder whether you can do the job. Aim for a behavior, not a trait. “My updates weren't matched to my audience” is a behavior you can change. “I'm a poor communicator” is a trait, and it sticks to you.

Stay away from feedback about the main skill the job is built on unless your fix is clearly proven. Leave out anything that touches honesty or ethics. If you're interviewing for banking, practice this story next to your other banking fit questions. You can often reuse it for “Tell me about a mistake.”

Check your pick against this list before you practice it out loud:

Safer and riskier feedback to use, by role

Safer and riskier feedback to use, by role
RoleSafer feedback to useRiskier picks
ConsultingLeading with detail instead of the answer in updates. Working alone too long before checking in.Weak structured thinking. A clash with a client.
Investment bankingPolishing a deck when the team needed a rough draft first. Not flagging an assumption to the associate.Repeated errors in models that went out. A missed deadline that reached a client.
Product managementSpecs that left engineers guessing on edge cases. Bringing stakeholders in late.Not caring about users. Shipping with no data at all.
Student or no work experienceA professor's note that your report had data but no recommendation. A teammate's comment that you held updates until the deadline.An academic integrity issue. A grade dispute you argued.
Career changerFeedback from your old field that carries over, such as explaining things to a new audience.Feedback that suggests you left because you could not do the old job.

Sample answer: negative feedback you received

Example answer written by our team. The applicant is invented.

“In my first year as an analyst at a regional logistics company, I sent a weekly cost update to our operations director. After the third one, my manager pulled me aside and said, ‘Your updates are thorough, but she has to read to page 2 to find out if we're on budget.’ My first reaction was to defend the detail, because I'd worked hard on it. Instead I asked her to show me one update rewritten the way she'd want it. She moved my last paragraph to the top. So I changed 3 things. I opened every update with one line saying whether we were on budget and by how much. I cut the body to the 3 drivers that moved the number. And I put the detail in an appendix for anyone who wanted it. 2 weeks later the director started replying to the first line with decisions instead of asking me to call her. I still write the answer first, and I now ask new managers early how they like updates sent.”

Here is what each line does:

  • “In my first year as an analyst...” sets the scene in one sentence, then moves on.
  • “...she has to read to page 2...” quotes the feedback, so it sounds real and specific.
  • “My first reaction was to defend the detail...” is honest about the reaction, which makes the control that follows believable.
  • “I asked her to show me one update rewritten...” turns criticism into a request for an example.
  • “So I changed 3 things.” starts the longest part of the answer, the action, in the candidate's own steps.
  • “...the director started replying to the first line with decisions...” is a result someone else could see, with no invented percentage.
  • “I now ask new managers early...” shows the change stuck and became a habit.

Answers for students and career changers

You don't need a job to answer this well. Feedback from a professor, a coach, a group project or volunteer work counts, as long as it describes how you work.

Example answer written by our team. The applicant is invented. “In my junior year I led a 4-person market research project for a marketing class. At the midpoint review, our professor said our draft had lots of data but no recommendation, and that as the lead I hadn't pushed the group to decide. That stung, because I thought my job was to keep everyone happy. I asked her what a recommendation should look like at the midpoint, and she said one sentence we could defend. So I set a rule for our meetings. We ended each one by writing our current answer in one line, even if we changed it later. Our final report opened with a clear recommendation, and she used it as the example for the class. I still end meetings by writing down what we decided.”

If you're changing careers, pick feedback from your old field that shows you can adapt. The story also helps explain why you're moving.

Example answer written by our team. The applicant is invented. “After 5 years teaching high school math, I joined a tutoring startup as an operations associate. My first manager told me my emails to engineers read like lesson plans, with a long setup and the request at the end. In teaching, building up to the point worked. Here it slowed people down. I asked her for 2 emails that had worked well, and both put the request in the subject line. I rewrote my template that week: request first, context second, and a date for the reply. A month later the engineering lead told my manager my tickets were the easiest to act on. Learning to change how I explain things for a new audience is part of why I'm moving into product.”

Weak answers and stronger fixes

Most weak answers fail in one of a few ways. They have no real feedback, they blame someone, they hide behind the team, or they never show a change. Here is what each one looks like and what to say instead.

Weak lines and what to say instead

Weak lines and what to say instead
What you might sayWhy it hurtsSay this instead
I can't think of any negative feedback I've gotten.It sounds like you don't ask for feedback or don't hear it.Name a small, real point from a review, a professor or a teammate.
My manager just didn't like my style.It blames the person and skips your part.Say what the manager saw, then what you changed.
People tell me I work too hard.It reads as a strength in disguise.Pick a behavior that had a cost, such as late updates.
We fixed it as a team.It hides what you did.Say I, and list your own steps.
I learned a lot from it.It gives no proof that anything changed.Give one thing someone could see afterward.
I disagreed, so I kept doing it my way.It suggests you push back on coaching.Say you disagreed, how you raised it and what you agreed to try.
A story about a breakup or a family argumentIt tells the interviewer nothing about how you work.Use school, a job, a team or volunteer work.
Feedback that ended with you being let goIt raises a bigger question than it answers.Choose feedback you acted on while still in the role.

Follow-up questions to prepare for

A good first answer usually earns a follow-up. Prepare a short reply to each of these.

“Did you agree with it?” Answer honestly. If you only partly agreed, say which part you accepted and how you tested the rest. Partial agreement handled calmly is a strong answer.

“How did it feel?” Name the feeling in a few words, such as frustrated or embarrassed, then move straight to what you did about it.

“What would you do differently?” Give one change you would make earlier, such as asking for feedback before the third update instead of after it.

“Can you give me another example?” Have a second, smaller story from a different setting ready, so it's clear the first one wasn't a one-off.

“How do you ask for feedback now?” Describe a real habit, such as asking one specific question at the end of each project.

“What did your manager say afterward?” Quote only what actually happened. If nothing was said, describe what you saw change instead.

When they ask how you give negative feedback

The sandwich method wraps criticism in praise: something good, then the problem, then something good. Our verdict is to skip it in your answer. The praise can bury the point, and an interviewer who is listening for directness may hear you avoiding it.

Use SBI instead: Situation, Behavior, Impact, then a request. Name when and where it happened, the specific behavior you saw and what it caused. Then ask for the other person's side and agree on a next step. Praise still has a place, but give it on its own and make it specific.

Example answer written by our team. The applicant is invented. “Last spring I was the senior analyst on a pricing project with a newer teammate, Jordan. In our Tuesday client meeting, 2 numbers on Jordan's slide came from an old data pull, and the client's finance lead caught it. We spent 10 minutes of a 45-minute meeting on it. That afternoon I asked Jordan to grab a coffee. I said, ‘In this morning's meeting, the volume numbers on slide 6 came from last quarter's file. The client noticed, and we lost time we needed for the pricing options. What happened on your end?’ Jordan explained that he'd pulled from a shared folder that hadn't been updated. That was partly a process gap, so we agreed on 2 changes. He would note the source file on every chart, and I would do a 5-minute check before anything went to the client. The next 3 decks had no data errors, and Jordan started doing the same check for our intern.”

Why it works: the feedback is private and quick, it names one behavior and its cost, it asks for Jordan's side before deciding anything, and the candidate takes on part of the fix. If you have never managed anyone, use feedback you gave a peer, or feedback you gave upward, such as telling a group project lead that the plan would miss the deadline.

Here are the exact words for each step, using the same story:

  • Set it up: “Do you have 15 minutes today? I want to talk about this morning's client meeting.”
  • Situation: “In the meeting, on slide 6...”
  • Behavior: “...the volume numbers came from last quarter's file.”
  • Impact: “The client caught it, and we lost time we needed for the pricing options.”
  • Ask: “What happened on your end?”
  • Next step: “Can we agree that every chart notes its source file, and I check the deck before it goes out?”
  • Follow up: “Let's look at the next deck together on Thursday.”

When the interviewer gives you negative feedback

Sometimes the feedback happens during the interview itself. The interviewer says your math is off or your answer missed the question. Pause, restate what they said in your own words, ask one clarifying question if you need to, fix it and keep going. If you're preparing for a case round, practicing a McKinsey-style case out loud gives you practice at taking a correction in the middle of an answer.

Restating matters more than it seems, because saying you understood doesn't prove you did. In its April 2016 Career Outlook guide on employment interviewing, the Bureau of Labor Statistics advises jobseekers to stop to consider an answer before responding to difficult or unexpected questions, and to ask for clarification if a question is confusing.

After a rejection, you can ask for feedback.

A short email you can adapt. Subject: Thank you, and one question.

“Hi Maya, thank you for your time on Tuesday and for letting me know about the decision. I enjoyed learning about how the pricing team works with regional leads. If you have 2 minutes, I'd value one piece of feedback. What is the one thing I could have done better in the case round? Either way, thank you, and I hope our paths cross again. Alex”

If you get a reply, thank them within a day. Then turn the point into one practice goal for your next interview, and don't argue with what they said.

For hiring teams: giving candidates negative feedback

If you're on the hiring side and a candidate asks why they didn't move forward, keep the note short, specific and based on the criteria you assessed. Written evaluation standards are normal governance practice even at the board level, where Securities and Exchange Commission rules approved on November 19, 2003 (Release No. 33-8340) require public companies to disclose in proxy statements their process for identifying and evaluating director candidates and the minimum qualifications and standards they seek.

A template you can adapt: “Hi Sam, thank you for asking. The panel was impressed by how clearly you structured the opening prompt. The main gap was case math accuracy, for example when working through the margin table in the second exhibit. Before your next interview, I'd suggest practicing multi-step percentage math out loud. Jordan”

  • Send it soon after the decision, while the interview is fresh for both of you.
  • Give one gap and one action they can take before their next interview.
  • Leave out anything about personality, age, family or background, and stick to job-related criteria consistent with equal employment opportunity tracking such as the U.S. Census Bureau's Equal Employment Opportunity Tabulation, which uses American Community Survey data to highlight the gender, racial and ethnic diversity of the American labor force.

From U.S. Bureau of Labor Statistics, Employment interviewing: Seizing the opportunity and the job (Career Outlook, April 2016), U.S. Securities and Exchange Commission, Current Accounting and Disclosure Issues in the Division of Corporation Finance (March 4, 2005) and U.S. Census Bureau, Labor Force Statistics.

1 practice question and sample answer

Say your answer out loud first, then read the sample answer.

Practice question

  1. Tell me about a time you received feedback you didn't agree with at first.

    Sample answer. Example answer written by our team. The applicant is invented. “During my internship on a mid-size bank's credit team, I built a comparables table for a loan review. My associate told me the table was ‘too clever,’ because I'd used nested formulas nobody else on the team could check quickly. I disagreed at first. The formulas were correct, and they saved me time. I said so, and asked what problem they caused. She explained that if she couldn't trace a number in a minute, she couldn't sign off on it before the credit meeting. That changed how I saw it. The model wasn't just mine. I rebuilt the table with simple steps across columns, labeled every input and added a notes tab with sources. The next review went to the credit meeting a day early, and she asked me to build the template the team used for the rest of the summer. I still build for the person who has to check my work.”

    It admits a real disagreement without blaming anyone and shows the candidate asked why before changing anything. Most of the time goes to specific changes, and it ends with a result someone else could see and a habit that lasted.

Practice your interview answers out loud

Soreno's AI interviewer asks behavioral and case questions out loud, follows up like a real interviewer, and scores every answer, quoting your own words.

Questions people ask

What is a negative feedback interview question?

It's a behavioral question that asks about criticism, usually feedback you received or feedback you gave someone else. The interviewer wants to see how you handle criticism, so pick a real example and focus on what you did next.

What if I have never received negative feedback?

Look smaller and wider. A comment in a review, a professor's note on a paper or a teammate's point in a group project all count, as long as you changed something because of it.

Should I use the sandwich method when I describe giving feedback?

We suggest SBI instead: Situation, Behavior, Impact, then a request and a next step. Wrapping criticism in praise can bury the point, and plain wording is easier to understand.

How long should my answer be?

Keep the setup to about 20 seconds, and spend most of the time on what you changed and what happened next.

Can I ask for feedback after a rejection?

Yes. Send a short thank-you letter, preferably within 2 days as the Bureau of Labor Statistics recommends, and ask one specific question about what you could have done better in the case.

Can I use feedback from school or volunteer work?

Yes. It works well if you are early in your career, as long as the feedback is about how you work, such as making decisions or communicating, and you can show a change.

Keep going