UX designer phone screen questions: a portfolio walkthrough recruiters can run

A UX designer phone screen works best as a structured walkthrough of one portfolio case study. Ask the candidate to pick the project they are proudest of, then take them through the problem, their own role, the research, the options they tried and dropped, what shipped and what changed afterwards. You are not judging how the screens look; the hiring team will do that. You are checking whether the designer can explain decisions with evidence. Strong designers talk about a usability test that changed their mind and a trade-off with engineering. Weak portfolios show polished final screens with no problem, no role and no outcome.

Design screens overlap with product manager phone screen questions, because both roles shape what gets built. The difference is the evidence: a product manager owns the outcome and the roadmap, and a designer owns how users experience the solution and the research behind it. This page gives you a walkthrough script, questions on research, accessibility and design systems, and the red flags specific to portfolios.

Product designer, UX researcher, UI designer or content designer: place the candidate

The portfolio walkthrough script

Ask the candidate to share their screen or send the case study link before the call. Then use these prompts in order, and let them talk. Twenty minutes on one project tells you more than five minutes on four.

1. "Pick the project you'd most like to be hired for. What was the problem,
    and who had it?"
2. "Who was on the team, and what was your part specifically?"
3. "What did you know about users before you started, and how did you find out?"
4. "Show me an early version. What was wrong with it, and how did you learn that?"
5. "What option did you reject, and why?"
6. "Where did you disagree with the PM or engineers? How was it settled?"
7. "What shipped? Was it different from your final design, and why?"
8. "What happened after launch? How do you know?"
9. "If you did it again, what would you change?"

Research methods: done, observed or read about

• "Tell me about the last usability test you ran. How many participants, what tasks, and what surprised you?" Strong: a number, the tasks and a finding that changed the design. Red flag: has never run one, for a role that expects it.
• "How did you recruit participants?" Strong: a method (customer lists, a panel tool, support contacts) and a bias they watched for. Red flag: only colleagues.
• "When did research tell you not to build something?" Strong: a specific example. Red flag: research only ever confirmed the plan.
• "How did you use analytics alongside interviews?" Strong: a funnel or event data pointing at a problem, then interviews explaining why. Red flag: never looked at product data.
• "How did you share findings so people acted on them?" Strong: a short readout, clips, a decision it drove. Red flag: long reports nobody read.

Accessibility, design systems and working with engineers

WCAG 2.2 became a W3C Recommendation on October 5, 2023, per the W3C Web Accessibility Initiative. Clients building public-sector, education, health or financial products often ask for it by name.

Portfolio red flags and how to check them

Certificates and design exercises

UX has no licensing, and certificates are optional. Nielsen Norman Group's UX Certification requires passing five courses and their exams, and NN/g publishes a list of certified people to verify against (as of September 2026). University and bootcamp certificates vary widely. For career changers, a certificate plus one case study with real users is a reasonable signal. For experienced designers, the walkthrough counts far more.

If the client uses an exercise, find out which kind and tell the candidate early:

• Portfolio presentation: the candidate presents one or two case studies to a panel. Your walkthrough is good preparation.
• Live whiteboard challenge: a short problem worked through with designers. Tests thinking out loud, not polish.
• Take-home exercise: keep it short and clearly unrelated to the client's live product. See how to evaluate a take-home assignment.

Logistics, knockout checklist and scorecard

Knock out, or flag to the client before submitting, if:

• The candidate cannot state their own role on any case study.
• The role needs research and they have never run a usability test or interview.
• No project in the portfolio shipped, for a mid-level or senior role.
• The client's product must meet an accessibility standard and the candidate has no accessibility practice.

Note what the candidate said at the key moments of the walkthrough, in their words: "five usability sessions; 'nobody found the bank connection step, so we moved it after the first invoice'" gives a design manager a reason to book the interview. Interview Signal can hold the walkthrough prompts as a checklist during the call and attach those quotes to each score.