What Happens When Two UI UX Designer Candidates Have Identical Resumes

Interview Insights · UI UX Designer

What Happens When Two UI UX Designer Candidates Have Identical Resumes

SECTION 01Why so many UI UX resumes look exactly the same

Put two fresher UI UX resumes side by side and you will often see the same skill list: Figma, Adobe XD, wireframing, prototyping, user research. The same projects: a food delivery app, a travel booking app, a redesign of a famous brand's website. The same summary line about being 'passionate about user-centred design'.

This is not the candidates' fault. They learned from similar sources. But it means the resume carries almost no information for me. When two resumes say the same thing, I know the real difference must be found in the interview, so I change my questions to find it.

PROJECTS

Food Delivery App - UI/UX Design
- Designed a user-friendly food delivery app
- Conducted user research and created personas
- Made wireframes and high-fidelity prototypes
- Tools: Figma, Adobe XD

(Two candidates in the same week wrote
 almost exactly this.)

PROJECTS

Canteen Reorder Flow - mobile, solo
- Interviewed 6 hostel students; most reordered
  the same 2-3 items each week
- Designed a 'Repeat last order' card on home,
  cutting the reorder path to 2 taps
- Tested with 5 students; fixed confusing
  'Customise' label after 3 missed it
- Figma: components, variants, prototype

The distinct version does not need a bigger project. It needs a narrower one, described with real details from your own small research.

SECTION 02Tie-breaker one: the live app critique

When I have two equal candidates, I often give each the same short exercise: 'Open any app on your phone that you use daily. Show me one thing that works well and one thing you would improve.' No preparation, no portfolio, just reasoning in front of me.

This exercise separates people quickly. Weak critiques are opinions about taste: 'the colours are boring', 'it feels cluttered'. Strong critiques name the user's goal, the specific problem, a principle behind it and a concrete fix. Using a shared language, such as Nielsen's usability heuristics, makes your reasoning easy to follow.

LIVE CRITIQUE STRUCTURE (about 3 minutes)

1. Context  : 'I use this app to ___.'
2. Works    : 'This part works well because ___.'
3. Problem  : 'At step ___, I ___ (what happens).'
4. Principle: 'That breaks ___ (heuristic/rule).'
5. Impact   : 'Users might ___ (risk).'
6. Fix      : 'I would try ___.'
7. Test     : 'I'd check it by ___.'

'I use a ride app to book cabs to college.

Works well: the pickup pin on the map with the
address below it. Recognition over recall -
I don't have to type my address.

Problem: after I tap Cancel, a fee warning
appears only on the next screen. That breaks
error prevention; users learn the cost too late.

Fix: show the fee inside the cancel button area
before the tap, e.g. Cancel (fee applies).

Test: ask 5 users to cancel and see if any
are surprised by the charge.'

The sample uses two heuristics, recognition rather than recall and error prevention, without showing off. Each one is tied to a real moment on the screen. That is what makes it convincing.

SECTION 03Tie-breakers two and three: a design spike and clear writing

When two candidates are still close, I look for a spike: one area where you go clearly deeper than the basics. It can be accessibility, design systems, motion, data-heavy dashboards, or forms and onboarding. A spike gives me a reason to remember you and a reason to place you on a specific team.

The other quiet tie-breaker is writing. UI UX designers write all the time: button labels, error messages, empty states and case studies. Two equal designers often separate on whether their words are clear, short and helpful. Bad microcopy in a portfolio is something I notice every time.

ERROR MESSAGE
  Before: Error 403. Request failed.
  After : We couldn't save your address.
          Check your connection and try again.

EMPTY STATE
  Before: No data.
  After : No saved addresses yet.
          Add one to check out faster.
          [Add address]

BUTTON
  Before: Submit
  After : Place order

Rule: say what happened, why if useful,
and what the user can do next.

/* Semantic colour tokens (CSS variables) */
:root {
  --color-blue-600: #1F4FD8;
  --color-gray-900: #111827;
  --color-gray-600: #4B5563;
  --color-red-600:  #DC2626;

  --text-primary:   var(--color-gray-900);
  --text-secondary: var(--color-gray-600);
  --action-primary: var(--color-blue-600);
  --feedback-error: var(--color-red-600);
}

.button-primary {
  background: var(--action-primary);
  color: #FFFFFF;
}
.field-error { color: var(--feedback-error); }

You do not need every spike. Pick one that genuinely interests you, do one small project in it and be ready to discuss it in depth. One real spike is worth more than five buzzwords on a resume.

Writing is the cheapest spike to build. Rewrite the error messages and empty states in one of your projects this week, and add a before-and-after slide to your case study.

SECTION 04Tie-breaker prep kit for UI UX designers

These three tools prepare you for exactly the moments where identical candidates separate. Use them in the week before your interview.

RESUME DE-CLONING SHEET

For each project line, replace:
  'user-friendly'   -> the specific user
  'conducted research' -> how many, how, what found
  'designed an app' -> the specific flow
  'Figma'           -> the Figma features you used

Summary line:
  I design ___ (area) for ___ (users)
  and I focus on ___ (spike).

Read it aloud. Could a classmate send
the same line? If yes, rewrite it.

CRITIQUE PRACTICE LOG (3 apps, 1 per day)

App: ____________  Task I did: ____________
Works well: _______ because ______________
Problem at step: ______________________
Principle broken: _____________________
User impact: __________________________
Fix: _________________________________
How I'd test it: ______________________

Record yourself explaining it in 3 minutes.

SPIKE PLAN (pick one, 2 weeks)

Spike chosen: ________________________
Why it interests me: __________________
Small project to prove it: ____________
Three terms I must explain well:
  1. __________  2. __________  3. __________
One question I could be asked: ________
My answer in 4 sentences: _____________

Add the project to the portfolio's top 3.

SECTION 05Habits that keep you from blending in

Standing out does not mean being flashy. It means being specific in places where everyone else is generic.

• Narrow your projects — A specific flow for a specific user feels original even when the app category is common.
• Critique apps daily — Spend a few minutes each day noticing one good and one weak pattern in apps you use, and note the principle behind each.
• Choose one spike — Go deep in one area such as accessibility or forms, so you have something to discuss beyond the basics.
• Write like a designer — Treat every label, error and case study paragraph as part of the design, and cut every unnecessary word.
• Show your own findings — Small numbers from your own tests, like three of five users missing a label, are proof that a resume template cannot copy.

SECTION 06Interview Q&A — Identical UI UX resumes

SECTION 07Test yourself — Identical UI UX resumes quiz

SECTION 08Frequently asked questions

SECTION 09Related reads