Tell me about a time you gave critical feedback to someone more senior than you.
answer
- ask for the opening first
- one observed behavior, one cost
- no audience, no ambush
- say what you want instead
- where the relationship landed
basics
~20 sTests whether you can deliver an uncomfortable message upward without swallowing it or turning it into a challenge. Ask for the opening, stick to one observed behavior and its cost, propose what you want instead, and keep the relationship working.
how to answer
5 beats- the behavior and the cost you could seeStart with one instance you personally observed and the consequence for the work or the team, not a general complaint about how they operate. Keep it to roughly a fifth of your airtime.
- how you earned the openingExplain how you got permission to raise it — asking for time, flagging the topic first, choosing a private moment. This beat is what separates candour from ambush and interviewers listen hard for it.
- what you actually saidQuote the sentence. Observation, effect, then a question about intent, and the specific alternative you were proposing. Vagueness here is the commonest reason this story fails to land.
- their response and what you concededGive the real pushback and say what part of it you accepted. Showing that you updated on something they knew and you did not is stronger than a clean win.
- what changed and where you stood afterwardsClose with an observable change, however partial, and one sign the working relationship held. If only half of it changed, say so — partial outcomes told honestly beat tidy ones.
your answer
4 story prompts- Pick a case where you spoke to the person directly before mentioning it to anyone else.
- Choose one instance you personally witnessed, with a date and a cost.
- Name the specific alternative you asked for, not the behavior you wanted stopped.
- Be ready to say which part of their pushback you accepted.
draft and rehearse your own answer in a learn session
go deeper
This probes candour under a power differential — whether you can raise an uncomfortable observation with someone who has more authority, and do it in a way that can actually be heard. Strong answers show preparation, a single concrete instance, a proposed alternative, and a relationship that survived. Silence and confrontation are both failure modes here.
I was the senior of two engineers on an agency pod rebuilding a retailer's account area, and our principal engineer joined every client-facing demo. Whenever the client asked one of my engineers a question, he answered it. Over three demos the client stopped addressing them at all and started routing every bug straight to him, which meant our triage arrived days late and second-hand. I did not want to raise it in front of anyone, so I asked for twenty minutes and opened by saying I wanted to give him some feedback about the demos and asking whether that was okay. Then one instance: in the last session, the client asked about the address validation and he answered before the person who wrote it could; and here is what it has cost us, nine issues escalated through him in a month instead of landing in our channel. He pushed back that dead air in front of a client is expensive, and he was right about that, so we agreed on a signal rather than a rule: he would wait a beat and redirect by name, and I would prepare whoever owned the topic beforehand. The next demo my engineer took two questions herself. Escalations through him went from nine in a month to two. He asked me to keep telling him things like that.
The strength is the permission-asking opener, a single dated instance with a cost attached, and a concession that his objection was legitimate. The result is partial and specific rather than triumphant. Raising it in the demo itself, or complaining upward first, would sink the same story.
I led frontend delivery on a media client's site, and the technical director above me had a habit of promising same-day fixes directly in client workshops, then having someone patch it that evening. It usually worked. Twice it did not: two of those rushed releases went out without any error instrumentation, and we found out about the breakage from the client's own support inbox rather than from our dashboards. I took it to him privately, and I made the message about the pattern rather than either incident, because one incident is a mistake and three is a policy. I said I would keep taking the urgent work, and asked for one thing: nothing ships to that client outside our release window without the instrumentation, even if that means telling them tomorrow morning instead of tonight. I brought the two dates and what each one cost us in support hours. He did not accept all of it — he kept the right to promise same-day for anything customer-facing and severe — and I took that, because the ninety percent case was what mattered. We wrote the exception down so the pods knew which one they were in. Over the following quarter, error rates on out-of-window releases came down from 5.1% of sessions to 1.6%, and he started asking me before committing in the room.
This works because the speaker owns the delivery consequence, makes the feedback about a pattern with dates attached, and asks for one changeable thing rather than a broad behavioural change. Naming the accepted exception out loud is the senior move; a version where the director simply capitulates would read as invented.
Keeping the message to something you directly observed and framing it as a question is enough at this level. Nobody expects you to change a senior engineer's habits; they want to see you speak rather than quietly work around them.
Show the preparation: which instance you chose, how you asked for permission to raise it, and the specific alternative you offered. The interviewer is checking that you can be candid with power differentials without theatrics.
Raise the stakes to something that affected delivery or quality, and show you took responsibility for the outcome afterwards. Say what you did when part of the feedback was rejected — accepting a partial win is a senior move, not a defeat.
Talk about making upward feedback normal rather than heroic: forums where decisions can be challenged before they reach a client or a launch, and how you make it safe for people several levels down to tell you something you do not want to hear.
saying these in an interview costs you the question
- Framing it as winning an argument with someone above you
- Delivering it in front of the team or a client so they cannot decline it
- Only hinting, then claiming the message was received
- Reporting it upward or sideways before ever saying it to the person
- Vague grievance about their style with no instance and no cost
- Anything that reads as badmouthing a former manager to the interviewer
- What did they push back on?Name the specific objection and whether it had merit. Answers where the senior person simply agreed sound rehearsed. Show which part you conceded, which part you held, and how you decided the difference.
- How did that relationship look six months later?Interviewers are checking that candour did not cost you the working relationship. Point to something concrete afterwards — being asked for your read on a decision, being handed harder work — rather than asserting things were fine.
- What would you have done if nothing changed?Have a real next step: raising it a second time more directly, adjusting your own working pattern, or taking it to your manager while telling the person you were going to. Silently seething and quietly escalating both read badly.