Loading...
Loading...
Browse 5 real-world technical and behavioral interview questions about Feedback. Review scenarios, edge cases, and architectural best practices.
Describe feedback you delivered directly to the person, in words you can repeat, about behaviour that was affecting the work, and say what changed afterwards. The score turns on whether you said the hard sentence out loud or softened it until it disappeared. It also connects leadership to the point an interviewer is testing.
Diagnose the cause before acting — skill, will, unclear expectations, or an environment or health problem you can remove — then give specific behavioural feedback, write down one expectation with a date, and make sure a formal performance plan, if it becomes necessary, is never a surprise.
Deliver it as your own message tied to specific evidence, never as a committee's verdict you privately disagree with. If it is a surprise, treat that as your failure and say so, give one concrete thing that would change the next cycle, and refuse to trade a promise you cannot keep for their staying.
One-to-ones are the engineer's time for the things that do not fit anywhere else, not a status meeting. Feedback lands when it is specific, close to the event, about behaviour and its effect, and carries a request. Growth is owned by the engineer; the manager owns opportunity, honest signal and air cover.
Choose feedback about your effect on other people rather than a skills gap, quote it close to how it was said, describe the reaction you actually had before the acceptance, and show a specific behavioural change that the person who gave it could confirm.