UX Designer Resume Example

Must-have

Core skills & ATS keywords

• User Research
• Wireframing
• Prototyping
• Usability Testing
• Information Architecture
• Interaction Design
• Design Systems
• User Flows

Tools & tech

Tools and technologies to name

• Figma
• Sketch
• Adobe XD
• Miro
• InVision
• Maze

Soft skills

Soft skills recruiters look for

• Empathy
• Communication
• Collaboration
• Problem Solving

Strong verbs

Action verbs to start bullets

• Researched
• Designed
• Prototyped
• Tested
• Improved
• Redesigned

Credentials

Certifications that help

• Google UX Design Certificate
• Nielsen Norman UX Certification

Opening questions

1. Walk me through your background as a ux designer.

   Keep it to 90 seconds, newest first, and end on why this role. Name User Research and Wireframing early — if they're in the posting, they're on the interviewer's checklist, and this answer sets the agenda for the rest of the conversation.

2. Why are you interested in this ux designer position?

   Connect one specific thing about the company or team to your own track record — a product, a market, a way of working. Generic praise reads as a mass application; specificity reads as intent.

3. What does success look like in your first 90 days as a ux designer?

   Structure it as learn, contribute, own: understand the team's current User Research setup first, ship something small by week four, and name the area you'd want to own by month three. Asking what THEY consider success is a strong closing move.

4. Why are you leaving your current role?

   Keep it forward-looking and under 30 seconds — what you're moving toward, not what you're escaping. Any negativity about a current employer gets projected onto how you'd talk about this one.

Role-specific questions

1. Show me a design where research changed your original direction.

   The point is not that you ran research but that a finding overruled your instinct. Name the assumption, the evidence that killed it, and what shipped instead.

2. You have no budget and no time for research. What do you do?

   Guerrilla testing, support tickets, session recordings, sales call notes, analytics. Designers who stop at "we couldn't do research" are the ones this question screens out.

3. How have you used User Research in a recent project? Walk me through one example.

   Use STAR and end on a number — a percentage improved, hours saved, error rate cut. Mention the tools involved (Figma, Sketch) by name; concrete stacks are what separates practitioners from keyword-matchers.

4. Tell me about your experience with Figma.

   Go deeper than "I've used it for X years." Describe one thing you built or ran with Figma, one limitation you hit, and how you worked around it — knowing a tool's edges is stronger evidence than fluency claims.

5. How do you keep your Wireframing work accurate when you're under time pressure?

   Name your actual quality mechanism: checklists, peer review, a verification pass, automation. Then give one example where the mechanism caught something a rushed pass would have shipped.

6. How would you explain Prototyping to someone outside the field?

   This tests communication, not knowledge. Use one everyday analogy, keep it under a minute, and skip jargon entirely — the interviewer is imagining you in front of a stakeholder or a new teammate.

7. How do you stay current with design practices and tools?

   Name real sources — specific newsletters, communities, or practitioners — and finish with one thing you learned recently and actually applied. The applied half is what makes the answer credible.

Behavioural questions

1. Tell me about a time you disagreed with a colleague. How did you resolve it?

   Pick a real disagreement about the work, not a personality clash. Walk through how you understood their position, what evidence settled it, and — the part interviewers listen for — what the working relationship looked like afterward.

2. Tell me about a mistake you made at work. How did you catch and fix it?

   Structure it as detection, containment, prevention. The strongest answers end with the guardrail you added so the same mistake can't happen silently again — that turns an error story into a judgment story.

3. When have you changed your mind about something important at work?

   Name the position you held, the evidence that moved you, and what you did publicly about the reversal. Interviewers are testing whether new information updates your view or just gets argued with.

4. Tell me about someone difficult you had to work with successfully.

   Avoid character assassination; describe the specific friction and what you changed in your own approach. Interviewers listen for whether you adapted or simply waited them out.

5. Tell me about the last thing you taught someone.

   Concrete beats abstract — what they couldn't do before, how you taught it, and whether they can now do it without you. This question surfaces whether you scale knowledge or hoard it.