Receiving and Responding to Feedback Questions

Candidates should be prepared to give concrete, specific anecdotes about receiving critical feedback or constructive criticism on their work. A complete answer explains the context, who provided the feedback, the precise nature of the critique, the candidate's initial emotional reaction, and how the candidate processed and prioritized the feedback. Interviewers seek evidence of humility, a growth mindset, the ability to separate personal ego from the work, and nondefensive communication. Strong responses describe the concrete changes made, the tradeoffs considered, how alternatives were evaluated, who was consulted or mentored, and how the revised solution was validated. Candidates should cite measurable outcomes or demonstrable improvements that resulted and articulate lessons learned and changes to their process to prevent recurrence. Emphasize continuous improvement, follow up actions, and examples of mentorship or coaching that supported development.

EasyBehavioral

25 practiced

What techniques do you use to separate personal attachment from your design before and during critiques, so you can respond non-defensively to feedback? Provide at least three practical strategies you apply routinely and an example of one in practice.

EasyTechnical

20 practiced

How do you solicit actionable feedback from users during a moderated usability test or prototype session? Provide a short script or list of prompts you use to avoid leading questions and to surface specific issues about UI clarity, interaction flow, and visual affordances.

MediumTechnical

20 practiced

Describe a time you received feedback that your detailed visual specification slowed developer implementation. What changes did you make to your handoff process (e.g., fidelity, componentization, documentation) and what trade-offs did you consider between design fidelity and engineering speed?

MediumTechnical

24 practiced

Imagine two senior stakeholders give contradictory visual direction: one requests an aggressive, brand-forward look while the other asks for conservative, enterprise styling. As the UI designer, outline a step-by-step process to reconcile both perspectives, create a recommendation with prototypes, and obtain stakeholder buy-in.

HardTechnical

20 practiced

Describe a time you received harsh public critique in a channel that undermined a junior teammate's confidence (for example, an assertive Slack message or a critical comment in a design review). Explain how you handled the immediate situation, how you supported the teammate afterward, and what process changes you led or recommended to keep critique culture constructive and safe.

Sample Answer

**Situation (brief)** During a cross-functional design review in Slack, a senior engineer posted a blunt, public critique of a junior designer’s high-fidelity screens—calling them “broken” and “not thought through.” The message came during a product sprint and visibly shook the junior designer’s confidence.

**Task** Protect the teammate, preserve psychological safety, and keep the design iteration productive.

**Immediate actions** - I replied privately to the engineer within minutes: thanked them for the technical notes, asked to move detailed implementation concerns to a follow-up thread or meeting, and reminded them that public tone matters. - I messaged the junior designer one-on-one: acknowledged the experience, validated their feelings, and offered to discuss the critique together so they wouldn’t have to face it alone.

**Support after** - We held a 30-minute pairing session where I coached on separating actionable feedback (e.g., accessibility constraints, breakpoints) from tone, and modeled how to ask clarifying questions. - I encouraged the junior designer to document decisions and rationale in Figma comments so future feedback could be more specific.

**Process changes I led/recommended** - Introduced a “public-first, specification-second” guideline: high-level observations okay in public; implementation critiques should include concrete steps or be moved to a private thread. - Rolled out a short rubric for critiques in design reviews (what, why, impact, suggested fix) and a lightweight moderator role for reviews to keep tone constructive. - Ran a micro-workshop on feedback etiquette and gave templates for actionable comments in Figma/Slack.

**Result & learning** The junior designer regained confidence, produced an improved set of screens with fewer defensive iterations, and the team adopted the rubric—reducing public harsh messages and improving cross-discipline collaboration. I learned the importance of swift private intervention, coaching in the moment, and systemic changes to sustain psychological safety.

Unlock Full Question Bank

Get access to hundreds of Receiving and Responding to Feedback interview questions and detailed answers.

Join thousands of developers preparing for their dream job.