How Long It Really Takes to Judge a UI UX Designer Candidate

Interview Insights · UI UX Designer

How Long It Really Takes to Judge a UI UX Designer Candidate

SECTION 01The portfolio skim: what forms before we ever speak

The first judgement does not happen in the interview at all. It happens when I open your portfolio link before the call, often between other tasks. I am not reading every word. I am scanning: Can I find the work quickly? Do the case study titles tell me what problem was solved? Does the first project open with a clear problem, or with a wall of mood boards?

This skim is short, so it rewards clarity, not volume. A portfolio with three clearly titled projects beats one with fifteen thumbnails and no labels. The skim does not decide the outcome, but it sets how hard the rest of the interview has to work.

BANKING APP REDESIGN

[Large mood board image]
[Colour palette swatches]
[Font specimen]

I have always been passionate about design.
This project was an amazing journey where I
explored the world of fintech and created
a modern, sleek experience...

(No role, no user, no problem in the first screen.)

HELPING NEW USERS FINISH KYC ON MOBILE

Role: Solo designer (student project)
Timeline: 3 weeks
User: First-time bank app users, 18-25
Problem: Users dropped off at the document
         upload step in my test of the old flow
Outcome: New flow with step progress and
         camera guides; 5 of 5 testers finished

[One before/after screen of the upload step]

The strong version gives me role, user, problem and outcome before I scroll. If the skim is all I get before the call, I already know what to ask you about.

SECTION 02The first minutes of the call: turning a guess into a hunch

When the call starts, I usually ask a warm-up question such as 'Tell me about yourself' or 'Which project are you proudest of?'. Your first answer adds a layer to my guess from the skim. I listen for structure: do you get to the point, do you talk about users or only about tools, and can you summarise your own work in about a minute?

This is not where the decision is made, but it shapes which questions I ask next. A clear opener lets me spend the round going deeper. A long, unfocused opener means I spend time just finding out what you did, and we have less time for the depth that would actually help you.

'I'm a UI UX designer focused on mobile flows,
especially forms and onboarding.

My strongest project is a KYC redesign for a
banking app. In my test of the old flow, users
stalled at document upload, so I added a step
progress bar and camera guides for the photo.

I work in Figma with components and auto layout,
and I test with real users early.

I'm interested in this role because your app
has a similar onboarding challenge.'

OPENER STRUCTURE (aim for about 60 seconds)

1. What I design   -> one line, specific area
2. Best project    -> one line: user + problem
3. Key decision    -> one line: what I changed
4. How I work      -> one line: tools + method
5. Why this role   -> one line: link to them

Avoid:
- school and family history
- a list of every tool
- words like 'passionate' with no example

A good opener is not about sounding polished. It hands the interviewer a clear thread to pull, so the rest of the round is spent on your strengths instead of on finding out what you do.

SECTION 03The deep dive: where the verdict is actually made

The middle of the interview is where my early guess is either confirmed or overturned. I pick one project and keep asking 'why'. Why this layout? Why not a bottom sheet? What did the test show? What would you change now? I may push back on a decision on purpose.

This is where a candidate with an average skim and a slow opener can climb, because their answers show real ownership. It is also where a polished candidate can fall, if every why gets a vague answer. By the end, I write my verdict from this evidence, not from my first impression, and I check whether my first guess was fair.

Q: Why a step progress bar for KYC?
A: Users didn't know how many steps were left,
   and some quit at upload thinking it was endless.

Q: Why not just fewer steps?
A: I tried merging steps, but compliance needs
   each document separately. So I made the length
   visible instead of shorter.

Q: What would you change now?
A: The selfie step. Two testers had poor light.
   I'd add a live brightness hint before capture.

INTERVIEWER NOTES (after the round)

First guess (skim): clear, problem-led
After opener:       focused, mobile forms
Deep dive:
  - why answers: deliberate, named trade-offs
  - testing: specific, honest small sample
  - pushback: asked a question, adapted
  - self-critique: named selfie-step flaw

Did evidence match first guess? YES
Verdict: Recommend for next round

(Fair interviewers write this check explicitly.)

That last line in the notes matters. A careful interviewer asks themselves whether the first guess was tested or simply believed. Your job in the deep dive is to give them enough evidence that the answer is obvious.

SECTION 04Stage-by-stage prep plan for the whole timeline

Prepare for each stage separately, because each one is judged on different things. Use these three sheets in the order the interviewer will meet you.

SKIM-PROOF PORTFOLIO CHECK

[ ] Max 3-4 projects on the home page
[ ] Each title states the problem, not the app name
[ ] Each cover shows one key screen clearly
[ ] Top of each case study: role, user,
    problem, outcome in under 6 lines
[ ] Images compressed; page loads fast on mobile
[ ] Contact and resume link visible

Test: show it to a friend for 30 seconds.
Ask: 'What problem did my first project solve?'

OPENER DRILL

Day 1: Write the 5-line opener.
Day 2: Say it aloud, record it, time it.
Day 3: Cut anything that is not about
       users, problems or decisions.
Day 4: Say it to a friend. Ask what they
       remember. That is your real message.
Day 5: Practise a 30-second version too,
       for interviewers who are short on time.

WHY CHAIN SHEET (main project)

Decision 1: ________________________
  Why?  _____________________________
  Why not the obvious alternative? ___
  What evidence supported it? ________

Decision 2: ________________________
  Why?  _____________________________
  Why not the obvious alternative? ___
  What evidence supported it? ________

One flaw I'd fix now: _______________

SECTION 05Habits that help at every stage of the judgement

These habits work whether the interviewer judges fast or slowly, because they make evidence easy to see.

• Label your work clearly — Problem-based titles and short summaries help any reader understand your portfolio in a skim.
• Don't panic over a slow start — If your opener goes badly, stay calm. The deep dive carries far more weight, and you can recover there.
• Give evidence early — Mention one specific test finding in your first few answers so the interviewer starts trusting your process sooner.
• Invite the deep dive — End your opener with a hook, such as a hard decision you made, so the interviewer digs where you are strongest.
• Close with a reflection — If you get a chance at the end, briefly name what you would improve in your project. It leaves a mature final impression.

SECTION 06Interview Q&A — Judging UI UX talent

SECTION 07Test yourself — Judging UI UX talent quiz

SECTION 08Frequently asked questions

SECTION 09Related reads