Behavioural interview
How to answer: Tell me about a time you received difficult feedback
“Tell me about a time you received difficult feedback.”
Reviewed by Saadan Naqvi
Direct answer
Acknowledge the feedback immediately without becoming defensive. Describe the situation clearly, explain your initial reaction, and detail the specific steps you took to implement the change. Focus on the positive outcome, such as improved code quality, better team collaboration, or a successful project delivery that resulted from your professional development.
Practising this one out loud? It comes up in the General track in Ranked Arena. Or check your own written answer ↓
What the interviewer is actually assessing
- Your ability to remain objective and professional when receiving critical input on your work.
- Evidence of your capacity for self-reflection and willingness to adjust your technical approach.
- How you translate constructive criticism into measurable improvements in your engineering output.
A typical answer, and what would sharpen it
The answer below lands the question. It is still not the one that gets remembered — here is the gap. Everything after it is real output from the same grader the tool on this page uses — the verdict, the diagnosis, and the rewrite were produced by running that answer through it.
Typical answer · Senior Software Engineer
I remember a performance review a few years back where my manager suggested that I needed to focus more on the big picture rather than just digging into the technical weeds of every ticket. At the time, I was very focused on refactoring legacy code because I felt that having a clean codebase was the most important thing for the team's long-term health. The feedback was a bit hard to hear because I pride myself on writing high-quality code. I think the challenge with feedback like that is that you want to maintain your standards while also trying to balance business requirements and delivery timelines. I generally try to take feedback by listening to what they have to say and then finding a middle ground where I can still keep the quality high while also being more responsive to the product roadmap.
What they answered instead
They described receiving feedback about focusing too much on technical weeds rather than the big picture, and how they balanced code quality with delivery timelines.
Missing piece
A specific, measurable change or resulting action they took after receiving the feedback to demonstrate growth.
Why
The candidate directly addressed the prompt by sharing a specific piece of difficult feedback regarding their focus on technical details over the big picture, and explained how they processed it.
Stronger rewrite
During a performance review, my manager told me I needed to focus more on the big picture instead of getting lost in the technical weeds of every ticket. At the time, I was heavily focused on refactoring legacy code because I believed pristine code was paramount, but it was slowing down our delivery. It was tough to hear since I pride myself on craftsmanship, but I realized I needed to align my work with business priorities. I adjusted my approach by time-boxing refactoring tasks and prioritizing code cleanup that directly impacted user-facing features or velocity. As a result, I improved my delivery speed without sacrificing the core health of the codebase.
Practise tip: Use the STAR method to ensure you clearly land the 'Result' phase with a concrete action you took and the outcome it produced.
Now check your own answer
Paste how you would answer this question. You get the same thing you just read — the verdict, what you answered instead, the missing piece, and a rewrite — on your own words. No account needed.
This grades what you wrote. Ranked Arena grades what you say, on a timer.
Ranked Arena
Typing it is easy. Saying it under a timer is the interview.
Ranked Arena puts questions like this one in front of you on a countdown, on camera and mic, and grades what you actually said — structure, specificity, and impact. Every match earns Interview Points and moves you up the ladder from Wood to Cracked. The General track carries purely behavioural prompts — leadership, conflict, ownership.
Three ranked battles a month on a free account, drawn from a bank of 500+ questions. No webcam needed — mic-only still gets graded and ranked.
Common questions
Should I choose feedback that was unfair?
Avoid choosing feedback you felt was unfair or incorrect. The interviewer wants to see how you handle legitimate criticism. If you present a situation where you disagreed with the feedback, you risk appearing difficult to manage or lacking the self-awareness required to learn from your peers and senior leadership.
Does the feedback have to be technical?
Not necessarily. While technical feedback regarding code architecture or system design is relevant, feedback on soft skills like communication, mentoring, or project estimation is equally valuable for a senior role. Choose an example that demonstrates a significant shift in your professional behaviour or a clear improvement in your overall performance.
How much detail should I provide about the person giving feedback?
Keep the focus on your reaction and your subsequent actions. You do not need to name the individual or describe them in detail. Simply refer to them by their role, such as a lead engineer or a product manager, to maintain a professional tone and keep the narrative centred on your growth.
More questions like this