User Flows interview questions
User Flows questions a UX / UI designer can be asked, from first job to senior. Open one to see the strongest answer and why it works.
The list is empty on day one. What do you design?
The strongest answer: A next step that starts the job — not a cute illustration and a shrug, and not fake rows for the screenshot
Why it works: Exactly. A next step. Fake rows and contact-grabs are how you teach distrust.
- Empty = a next step.
- Not only an illustration.
- Do not fake rows for the shot.
- Do not make a contact-grab the only button.
A form fails. What does a good error do?
The strongest answer: Say what happened, where, and how to continue — I do not only turn a border red
Why it works: Exactly. What, where, next. Red-only, blame, and vanishing toasts leave people stuck.
- What / where / how to continue.
- Not red-only.
- Do not blame the user.
- Do not vanish the only message.
A stakeholder loves one screen. What do you still show?
The strongest answer: The path in and the path out — one pretty frame is not the product
Why it works: Exactly. In and out. Bigger, posters, and invented completion % skip the journey.
- Show the path in and out.
- One frame ≠ the product.
- Do not only enlarge the favourite screen.
- No invented completion %.
What does a good loading state do?
The strongest answer: Show that we heard you and what is still coming — I do not block the whole page with a mystery spinner
Why it works: Exactly. Heard you, what is next. Mystery spinners, surprise, and lying 99% bars burn trust.
- Loading = we heard you + what is next.
- Do not mystery-spinner the page.
- Do not surprise-replace the UI.
- Do not lie with a 99% bar.
A flow makes unsubscribe take seven steps and one click to resubscribe. What do you call it?
The strongest answer: A dark pattern — I redesign to even the path, I do not “optimise friction for churn”
Why it works: Exactly. Name it and even it. Clever-war-A/B is how you join the hall of shame.
- Name the dark pattern.
- Even the path.
- Do not present it as clever.
- Do not add steps to “win” churn.
A list UI you will sign. Minimum states?
The strongest answer: Empty, populated, error, and loading — I do not sign happy-only
Why it works: Exactly. Four you can name. Happy-only, lorem-empty, and dead-end red are how QA writes your spec.
- Empty, populated, error, loading.
- Do not sign happy-only.
- Do not lorem the empty.
- Error needs a next step.
Onboarding asks for contacts, location, and notifications before the first job. What do you change?
The strongest answer: Ask at the moment the permission helps, with a why — I do not front-load a permission wall
Why it works: Exactly. Just-in-time, with a why. Walls, pre-ticks, and shame are dark patterns.
- Ask permissions when they help.
- Give a why.
- No front-loaded wall.
- No pre-tick or shame.
A journey map on the wall has five stages and a smiley curve. What is missing before it can change anything?
The strongest answer: Evidence under each stage — what people did and said — plus their goal at that moment, the pain, and who owns fixing it; otherwise it is the team’s guesses, drawn neatly
Why it works: Exactly — a map with sources and owners drives work; a map without them decorates a wall.
- Every stage needs evidence and an owner.
- Write what people did, not felt.
- Name the goal at each stage.
- Cite the source or mark it unknown.
How do you treat empty states across a suite?
The strongest answer: As the first-run product: one next step, honest data, no fake rows — I do not let each squad invent a shrug
Why it works: Exactly. First-run as a system. Illustration-only, walls, and fake rows fail the first minute.
- Empty = first-run next step.
- No fake rows.
- Do not make it a permission wall.
- Do not shrug per squad.
The UI is fine; people still fail the job because of email and a shop floor. What do you map?
The strongest answer: The service: channels, waits, and handoffs — I do not only restyle the form
Why it works: Exactly. The path across channels. Prettier, out-of-scope-shrug, and invented completion % skip the job.
- Map channels, waits, handoffs.
- Do not only restyle the form.
- Do not shrug “out of scope” without a map.
- No invented completion %.
What share of a flow file should be unhappy paths?
The strongest answer: Enough that eng cannot invent them — empty, deny, timeout, partial — I do not give a ratio I invented
Why it works: Exactly. Enough to implement. 0%, invented 80%, and later-pages are how QA writes your spec.
- File empty, deny, timeout, partial.
- Enough that eng does not invent them.
- Do not skip unhappy as “negative.”
- No invented 80% rule.
An assistant can invent policy. What do you design besides a chat box?
The strongest answer: Refuse, sources, and a human path — I do not make the model look like a confident clerk
Why it works: Exactly. Refuse, sources, human. Friendlier, fake meters, and hidden-wrong are how you scale a lie.
- Design refuse, sources, human path.
- Do not costume a clerk.
- No fake confidence meter.
- Do not hide that it can be wrong.
What staff bar do you set for empty states?
The strongest answer: A next step, honest data, and no permission wall — I do not let squads ship a shrug illustration
Why it works: Exactly. Next step and honesty. Packs-only, fake-data-mode, and invented 19% miss the first minute.
- Next step + honest data + no wall.
- No shrug illustrations as the bar.
- No fake-data mode for decks.
- No invented onboarding lift.