Beyond the Portfolio: What Designers Wish Interviewers Would Ask

Portfolio reviews remain the centerpiece of most design hiring processes, yet a growing number of practitioners argue that the format measures presentation polish more than problem-solving ability. Across industry forums, design communities, and internal hiring discussions, a consistent theme has emerged: the standard interview stack rarely surfaces the information that actually predicts success on the job.

Recent Trends: A Shift Toward Process Over Polish

Over the past several hiring cycles, studios and product teams have begun experimenting with alternatives to the traditional portfolio walkthrough. Some now ask candidates to annotate their case studies in advance, others run collaborative whiteboarding exercises, and a few have dropped portfolio reviews entirely in favor of simulated work sprints.

What these experiments share is an underlying critique: a finished case study reveals little about how a designer thinks under constraint, receives feedback, or navigates ambiguity. As hiring managers grow more skeptical of polished presentations, candidates are also recalibrating what they expect from the conversation on the other side of the table.

Background: Why the Current Format Falls Short

The portfolio has long served as a proxy for taste, craft, and experience. But as design has expanded into strategy, systems thinking, and cross-functional leadership, the artifact-based review has not kept pace. A well-documented case study can obscure how much of the work was shaped by other teammates, how many iterations were discarded, and how the designer actually behaved during moments of conflict or uncertainty.

Designers who have been through repeated interview loops often describe a common mismatch: interviewers ask about visual outcomes while the role demands judgment about trade-offs, user research, and stakeholder alignment. The result is a conversation that feels performative on both sides.

User Concerns: What Designers Want to Be Asked

When designers discuss their ideal interview, the requests rarely center on easier questions. Instead, they describe a desire to be evaluated on how they think, not just what they shipped. Common themes include:

• Failure and recovery: Questions about a project that went poorly, what the designer controlled, and how they changed course.
• Trade-offs under constraint: Scenarios involving tight timelines, conflicting stakeholder input, or limited research access.
• Collaboration dynamics: How the designer influenced engineers, product managers, or executives without formal authority.
• Unfamiliar problems: Interest in how a designer approaches a domain they know nothing about, rather than rehearsed projects.
• Growth and self-awareness: Direct questions about skills they are actively developing or perspectives they have changed on.
• Working style: Preferences around feedback, autonomy, and team rituals that affect daily collaboration.

Many designers also express a quieter concern: they want to evaluate the interviewer as much as the interviewer evaluates them. Thoughtful questions signal a mature design culture, while checklist-style queries often suggest rigid processes that may not support good work.

Likely Impact: A Slow but Real Shift in Hiring Practice

The pressure to redesign design interviews is unlikely to produce a single industry standard. Instead, expect a continued blending of formats. Portfolio reviews may persist, but as one input among several rather than the dominant filter.

More teams are likely to adopt structured behavioral questions that tie directly to the specifics of the role, such as how a designer handles research that contradicts a stakeholder's opinion or how they sequence work when scope is unclear. These questions are difficult to fake and produce richer signal than the retrospective case study alone.

There is also a practical dimension: hiring is expensive, and interviews that produce weak signal often lead to poor outcomes. As organizations track the performance of interviewees against their interview notes, evidence will likely push them toward methods that expose thinking under realistic pressure.

What to Watch Next

Several signals will indicate whether this conversation moves from discussion to default:

• Interview rubrics: Whether teams publish or share evaluation criteria that reward reasoning over visual polish.
• Take-home alternatives: Whether short, time-boxed exercises replace or complement portfolio presentations in more hiring pipelines.
• Candidate-side questions: Whether designers begin publishing lists of questions they ask employers, reversing the traditional power dynamic.
• Leadership buy-in: Whether design managers and directors model the behavior they ask candidates to demonstrate.
• Entry-level implications: How junior candidates, who may lack extensive case studies, are affected by any shift away from portfolio-heavy review.

The most meaningful change will be cultural rather than procedural. If designers begin to believe that interviews can reveal how they think, collaborate, and recover from setbacks, the entire conversation becomes more honest. For now, the message from practitioners is consistent: look past the artifact and engage with the judgment that produced it.