Tell me about a situation when your work was criticized.
Tests psychological safety, non-defensiveness, coachability, and turning feedback into performance.
Why Interviewers Ask This (Recruiter Psychology)
Everyone receives critical feedback. Recruiters want to know if your ego gets bruised and defensive, or if you evaluate feedback objectively and adapt your engineering practice.
Winning Answer Formula: STAR-Feedback Loop
Never dismiss the critique or claim the person criticizing was wrong.
Curated Model Answers
"During my internship, I submitted a pull request for a caching service that worked functionally, but my tech lead commented that my code lacked unit tests for error boundary states and used poorly named variables. Initially, I felt a bit disappointed, but I quickly realized his critique was about production reliability, not personal capability. I scheduled a 15-minute sync, asked for guidance on their standard testing patterns, refactored the PR to 95% test coverage, and added clear docstrings. Since then, I always write tests alongside features and use PR reviews as a primary learning channel."
"A few years ago, I architected an internal analytics dashboard and received direct feedback from our Product Manager that while the backend was robust, the dashboard was too complex for business users to interpret easily. Rather than defending my engineering design, I arranged shadow sessions with the marketing team to watch how they used the tool. I realized they needed summary cards rather than raw log graphs. I redesigned the UI layer to highlight actionable KPIs. That critique taught me a vital lesson: technical brilliance is useless if it doesn't align with end-user ergonomics."
Alternative Candidate Perspectives
"Feedback is the cheapest debugging tool in existence. If a senior engineer spots a flaw in my PR, they just saved me from a 2 AM on-call alert."
💡 Key Takeaway: Viewing critique as on-call risk reduction proves high maturity.
"No one is born perfect. When my plant head critiqued my throughput efficiency and assigned tougher tasks, I didn't get disheartened—I treated his words as fuel to elevate my engineering precision and deliver 40% faster."
💡 Key Takeaway: Treating tough managerial criticism as a performance catalyst showcases high coachability.
"Whenever criticism arrives, I stay calm and separate emotions from the code. If it's a valid mistake, I fix it and document the edge case. If there's context missing, I politely clarify with data. Ego has no place in pull request reviews."
💡 Key Takeaway: Separating emotion from technical facts prevents interpersonal friction and elevates code quality.
✓ What to Do (Best Practices)
- Choose a real example where the criticism was valid.
- Emphasize emotional composure and gratitude for feedback.
- Highlight the permanent habit or process improvement that resulted.
✗ What NOT to Say (Red Flags)
- Never say "My work has never been criticized."
- Don’t blame the person who gave the feedback or claim they had an agenda.
🎯 Probable Follow-Up Questions from HR
Frequently Asked Questions
Should the criticism example involve a major failure?
Pick a manageable, professional feedback scenario (code readability, UX misalignment, test coverage) rather than an catastrophic negligence incident.