What Interviewers Actually Look for in a Fresher UI UX Designer

Interview Insights · UI UX Designer

What Interviewers Actually Look for in a Fresher UI UX Designer

SECTION 01Checkpoint one: can you frame a problem before you draw it?

The first five minutes tell me a lot. I usually ask a fresher to pick one project and walk me through it. Most start with 'So this is the home screen.' That is the visual-first habit, and it worries me, because a screen is an answer and I have not heard the question yet.

The candidates who stand out start with the user and the problem. 'This was for first-year students who could not find their class timetable on the college app. They opened three menus and still gave up.' In one sentence I know who, what and why it mattered. Everything after that has a reason to exist.

Interviewer: Walk me through one project.

Candidate: Sure. This is a food delivery app.
Here is the splash screen, then the login,
then the home page with categories.
I used a purple gradient because it looks modern.
This card has a shadow of 8px.

(Three minutes later, still no user or problem.)

Interviewer: Walk me through one project.

Candidate: This was a college app redesign.
The problem: first-year students could not find
their timetable. I watched five classmates try,
and most gave up after the third menu.

My goal was one tap from the home screen.
Let me show the old flow first, then what I changed
and how I checked it worked.

Notice that the strong candidate uses tiny numbers they actually observed, five classmates and three menus. They do not claim a big study. Small, honest evidence is far more convincing than a big, vague claim.

SECTION 02Checkpoint two: evidence that you tested, not just designed

A fresher cannot show years of shipped work, and I do not expect it. What I do expect is evidence that you checked your ideas against real people. That evidence can be very small: a paper sketch, a five-person hallway test, a note that says 'users missed this button, so I moved it'.

What I cannot accept is a case study where every step is perfect. Real design is messy. If your research, wireframes and final screens all line up without a single change, I assume the process was written after the screens were finished. Show me the change you made and why.

USABILITY TEST SCRIPT (5 users, 15 minutes each)

Intro: 'We are testing the app, not you.
Please think out loud as you go.'

Task 1: Find your Monday timetable.
Task 2: Set a reminder for your first class.
Task 3: Check which room your lab is in.

For each task note:
  - completed? Y / N
  - time taken (rough)
  - where they hesitated or tapped wrong
  - exact words they said

Close: 'What was the most confusing part?'

FINDINGS (round 1, 5 users)

Task 1: 2 of 5 tapped 'Schedule' in the menu
        instead of the home widget.
  -> Widget label 'Today' was unclear.
  -> Change: rename to 'My Timetable'.

Task 2: All 5 completed. No change.

Task 3: 3 of 5 missed the room number.
  -> It was grey 12px text on white.
  -> Change: bold 14px, darker colour,
     moved next to the class name.

Round 2 planned with 5 new users.

These numbers are from your own small test, so you can say them honestly. 'Two of five users missed it' is a real finding. 'Users found it very intuitive' is not a finding at all.

SECTION 03Checkpoints three and four: craft basics and reacting to critique

Once I trust your thinking, I look at the screen itself. I am not judging taste. I am checking basics that any working designer handles without thinking: a consistent spacing scale, a clear type hierarchy, readable colour contrast, and all the states of a component, not just the happy one.

Then I deliberately push back on one decision. 'I think this button should be on the left.' I am not testing whether the button belongs on the left. I am testing whether you listen, ask why, and either adjust or explain with a reason. Defensive freshers and freshers who instantly agree with everything both worry me.

BUTTON COMPONENT (Figma variants)

Property: State
  - Default   : fill #1F4FD8, text white
  - Hover     : fill #1A43B8
  - Pressed   : fill #15379A
  - Disabled  : fill #C9D2E8, text #6B7280
  - Loading   : spinner + 'Saving...'

Property: Size
  - Small  : 32px height, 12px horizontal padding
  - Medium : 40px height, 16px padding

Auto layout: horizontal, gap 8, hug contents.
Text style: Label/Medium 14/20.

Interviewer: I think the Save button should be on the left.

Defensive: No, right is correct. Everyone does that.

Too agreeable: Oh yes, you are right, I will move it.

Strong:
'Interesting. I put it on the right because
users read the form top-left to bottom-right,
so the primary action sits where they finish.
Can I ask what makes you prefer left?
If it is for consistency with the rest of
your product, I would follow that pattern.'

The strong answer explains a reason, asks a question back and stays open to a better reason. That is exactly how design reviews work inside a team, and I am picturing you in those reviews.

SECTION 04Fresher interview prep worksheet for UI UX designers

Use these three sheets the week before your interview. Fill them for your strongest project only. Depth on one project beats a shallow tour of six.

PROJECT FRAMING SHEET

User (be specific): ______________________
Problem in one sentence: _________________
How I learned about it: __________________
Goal (ideally measurable): _______________

One thing I got wrong at first: __________
What made me change it: _________________
What I would test next: _________________

Say this aloud in under 60 seconds.
Time yourself.

CRAFT SELF-AUDIT (tick each)

[ ] Spacing values come from one scale
[ ] Max 3 text sizes per screen
[ ] Text styles named and reused
[ ] Body text contrast >= 4.5:1
[ ] Touch targets at least 44x44 px
[ ] Empty, error and loading states exist
[ ] Buttons built as components with variants
[ ] Frames use auto layout, not loose groups
[ ] Layer names are readable, not 'Rectangle 47'

Fix every unticked box before sharing.

CRITIQUE REHEARSAL (with a friend)

Friend picks 3 decisions in your design
and disagrees with each one.

For each, you must:
  1. Restate their concern
  2. Give your original reason
  3. Ask one question back
  4. Say what would change your mind

Score yourself:
  Defensive?        Y / N
  Gave a reason?    Y / N
  Asked a question? Y / N

SECTION 05Small habits that make a fresher look ready

None of these need experience. They need care, and care is exactly what I am trying to measure.

• Bring one deep project — Pick the project you understand best and know every decision in it, rather than rushing through five projects you only half remember.
• Keep your messy work — Save photos of sketches and early wireframes. They are the easiest proof that the process was real.
• Learn the vocabulary — Words like affordance, hierarchy, cognitive load and information architecture help you explain decisions quickly and precisely.
• Know one heuristic set — Being able to name a few of Nielsen's ten usability heuristics, such as visibility of system status, gives your critique a solid base.
• Ask about their users — End by asking who the company's users are and what they struggle with. It shows you think about people first, even at the last minute.

SECTION 06Interview Q&A — Fresher UI UX

SECTION 07Test yourself — Fresher UI UX quiz

SECTION 08Frequently asked questions

SECTION 09Related reads