Tell me about yourself for a UX interview

Start with the kind of product you design and one decision that shipped. The portfolio will carry the pictures. This minute carries the judgment.

Build your answer

Target role The job you are interviewing for. Years of experience Years in this kind of work. Use 0 for a first role or a career change. Current role or background A field, a path, or a short phrase.

Win 1 Include a number. Win 2 Optional. Win 3 Used in the long version.

Key strength One habit, not five adjectives. Why this company or role A reason that would be wrong for a different employer.

Runs in your browser. Nothing you type is uploaded.

30-second version

About 36 seconds · 89 words

A short cut for a recruiter screen.

Stop after one result. A short screen does not need the second story.

60-second version

About 61 seconds · 153 words

The default. Present, then past, then future.

If they lean in, drop the second result and spend the time on how the first one happened. Leave duties from the job description out.

90-second version

About 87 seconds · 217 words

A longer cut when they ask you to walk through it.

I'm looking for a product designer role. For the past 5 years I've worked as a product designer on a B2B onboarding flow. Before that, the results are specific. I cut setup time from 11 days to 4 by removing two screens research showed people feared. I also shipped an accessible form pattern that 4 squads adopted. A later result was killed a redesign that tested worse than the screen we already had. Each of those has a before and an after I can defend. The way I work, when it counts, is arguing from what users did, not from what the mock looked like. What I want next is this product designer seat, because this team designs a workflow people use every day, and I want that kind of constraint. On the job I'd stay this concrete about product designer, including what moved and what did not. The numbers in those results are ones I can defend, including what I owned. The decision under the first result is the part I know best. I checked the baseline before I called that result done. I would use the same judgment on the next product designer problem. The work I want next is still product designer work: a clear owner, a number, and a decision I can explain.

They can interrupt. Go present, then proof, then why this role. When they ask, go from the headline number to the decision you made.

When you can say the minute without the page, practice it live with Luna. It hears the question and helps you keep a line. 24 hours free.

How to answer it for this role

"I live in Figma" is not an identity. Name the surface: onboarding, clinical workflow, checkout, internal tools. Then one constraint you designed under: a regulated field, a legacy UI, a metric, an accessibility bar.

Outcomes beat process theater. You do not need to say double diamond. Say what users could not do, what you changed, and what happened. If you do not have a metric, use a research finding and what the team shipped because of it.

Why this company should mention the design problem you want, not the brand prestige. A design system role and a zero-to-one product role should sound different in sentence one.

What to emphasize

The product surface.
A constraint and what shipped.
How you worked with engineering or research, briefly.

What to leave out

A software shopping list.
Taking sole credit for a team's research.

Sample 60-second answer

This is the sample loaded into the builder above. About 61 seconds, 153 words. Replace every fact with yours before you practice it.

I'm looking for a product designer role. For the past 5 years I've worked as a product designer on a B2B onboarding flow. Before that, the results are specific. I cut setup time from 11 days to 4 by removing two screens research showed people feared. I also shipped an accessible form pattern that 4 squads adopted. The way I work, when it counts, is arguing from what users did, not from what the mock looked like. What I want next is this product designer seat, because this team designs a workflow people use every day, and I want that kind of constraint. In the job I'd bring that strength to the team's current goal, and I'd report what moved. Those results are the kind of work I want to keep doing as a product designer. I can explain the constraint behind the first result and the number I was willing to defend.

The 30-second cut is about 36 seconds. The longer cut is about 87 seconds. Both use the same facts in the same order. Read the longer structure guide if you want the timing rules in full: how long the answer should be.

Tips before you say it

Say the 60-second version out loud before you edit it. A sentence that looks fine on the page often runs long or sounds like a memo.
One number per win. “Improved the process” is a claim. “Cut hold time from 6 minutes to 2” is a result you can be questioned on.
Stay in order: present, past, future. If you start with where you grew up, the interviewer is waiting for you to arrive.
Leave a door open and then stop talking. The extra story you add in the silence is usually the one you did not prepare.
Keep your part separate from the team’s. “We launched” collapses the first follow-up. “I cut the scope, engineering shipped it” survives.

Other roles

Questions people ask

Should I walk through a case study in this answer?

No. Offer one. The case study is a later question. The opener is the frame.

What if I am a visual designer moving into UX?

Say that. Show one project where you changed the flow because of a user, not only the look.

Do I mention accessibility?

Yes if you have a real example. A single clause is enough. A lecture belongs in the portfolio review.