Portfolios don’t show how designers handle feedback

A founder and I had taken a candidate through a hiring process. The portfolio was strong, and the candidate had cleared the earlier conversations. Then our evaluators raised a concern about a repeated response to challenge: the person appeared to acknowledge feedback without meaningfully engaging with it.

When I described that concern, the founder recognized the pattern from a previous hire. That was the experience behind my original post. It does not prove that a single awkward interview response predicts someone's future performance. It does show why a polished portfolio cannot answer every question about how a person works with others.

The assessment I want is not whether a designer agrees with feedback. It is whether they can understand a challenge, reason about it, and make their response clear.

Separate receptiveness from compliance

A designer can listen carefully and still disagree. That may be exactly what the team needs when feedback overlooks a user problem or introduces a new risk. Equally, a quick agreement may reveal little about whether the person understood the concern.

Look for the process between hearing feedback and choosing an action. Did the designer clarify the issue? Did they distinguish a preference from a constraint? Could they explain what would change their view? If they chose to retain the design, did they make the reasoning understandable to the people involved?

Receptiveness is not a pleasant expression or a particular tone. It is a willingness to engage with information that could improve or challenge the work. A useful assessment gives independent judgment and genuine collaboration room to exist together.

Start with a real example from their work

Ask a candidate to describe a project where someone challenged an important decision. What was the concern? Who raised it? What did the designer initially think, and what happened after the conversation?

Follow the sequence. A story that jumps from disagreement to a successful outcome may leave the most useful part unexplained. Ask what the designer changed, what they kept, and how they communicated the choice. If new evidence arrived later, did they revisit the decision?

You do not need the candidate to produce a dramatic conflict. Ordinary feedback about a workflow, a technical limitation, or an unclear interaction can reveal how they work. A concrete account is more useful than asking whether they consider themselves open to feedback.

Make an interview challenge fair and relevant

If you discuss an alternative during a portfolio review, explain the concern and give the candidate enough context to respond. An unfamiliar interviewer offering a vague objection is not the same situation as a colleague raising an informed question during a project.

Avoid using hostility or surprise as a proxy for realistic pressure. You may end up assessing how someone handles your interview behavior rather than how they collaborate at work. Keep the discussion tied to the role and allow time to think.

A useful prompt might ask how a decision would change under a different constraint. The point is not to discover the one answer you privately prefer. It is to see how the candidate reasons, what they ask, and how they acknowledge uncertainty when the original solution may no longer fit.

Record behaviors rather than personality labels

After the conversation, write down what happened. “Asked which users were affected, proposed a way to test the concern, and explained a remaining trade-off” gives the team evidence. “Great attitude” does not explain much.

The same applies to a concern. If a candidate repeatedly returns to their preferred solution without addressing the question, describe the question and the response. Then consider other explanations: was the prompt unclear, was information missing, or did the interviewer interrupt the answer?

A single exchange should not carry more certainty than it can support. Look for patterns across relevant evidence, and give the person an opportunity to clarify an important ambiguity before treating it as a settled conclusion about how they work.

Ask how the decision reached the team

Feedback can fail even when the designer's reasoning is good. If stakeholders believe a concern was accepted and later discover that nothing changed, they may experience the outcome as being ignored. The missing step is often explicit closure.

Ask how the candidate communicated the final decision. Did they explain what would change, what would stay, and why? Did they confirm who owned the next action? When the decision belonged to someone else, how did they support implementation while keeping an unresolved risk visible?

This is practical collaboration. The team should not have to infer whether its input was heard by examining the next version of a design file. A clear response makes disagreement easier to manage because people understand the reasoning and the plan.

Examine the environment you are offering

A company cannot ask candidates to be receptive while delivering contradictory, unexplained feedback. If every stakeholder can issue a new direction and nobody resolves the conflict, even a thoughtful designer will struggle to make progress.

Describe how feedback works in your team. Who needs to review a decision? Which constraints are fixed? How are conflicting requests resolved? Is the designer expected to recommend an answer or obtain agreement from everyone involved?

If those questions have no answers, part of the hiring task is defining the role's decision environment. Otherwise the company may hire someone to absorb confusion and later criticize them for failing to make it disappear.

Use the portfolio to begin the conversation

The portfolio shows selected work and a story about how it happened. It can provide strong evidence of craft and decision-making, but it remains a starting point for understanding collaboration.

Ask how the work changed when it was challenged. Listen for judgment as well as flexibility. Give the candidate a fair chance to explain a disagreement, and hold the company's own process to the same standard of clarity.

The question is not whether this person will say yes when you dislike a design. It is whether the two of you can examine a concern, reach an explicit decision, and continue doing useful work together.