Wireframing interview questions
Wireframing questions a UX / UI designer can be asked, from first job to senior. Open one to see the strongest answer and why it works.
When are lo-fi wireframes the stronger artefact?
The strongest answer: When we are still arguing flow, states, and the job — polish is how you freeze the wrong path
Why it works: Exactly. Fidelity matches the argument. Motion reels freeze the wrong path with extra charm.
- Lo-fi while flow and states are open.
- Polish freezes a path.
- Polish ≠ senior.
- Do not start in a motion reel.
You are wireframing a nine-field form. Single column or two, and where do the labels go?
The strongest answer: One column, labels above the fields — the eye follows a single path, the label stays visible once the field is filled, and nothing is mistaken for a different row
Why it works: Right — one path down the page, and a label that survives typing and translation.
- One column, labels above.
- Keep a single vertical path.
- Never use placeholders as labels.
- Check it at phone width.
How do you take a desktop settings page to a phone?
The strongest answer: Re-choose the primary job and the tap targets — I do not pinch the desktop file to 390px
Why it works: Exactly. Re-choose. Pinch, unlabelled danger, and faint-for-trend fail thumbs and a11y.
- Re-choose the job and the targets.
- Do not pinch the desktop file.
- Do not hide danger in an unlabelled icon.
- Do not drop contrast for a trend.
In review someone says your wireframe “feels random”, even though every gap came from the spacing scale.
What is probably wrong?
The strongest answer: Equal gaps everywhere, so nothing reads as a group — I tighten the space inside a group and open it between groups, and let proximity work before borders do
Why it works: Exactly — relationships come from relative space first; boxes are the fallback, not the tool.
- Space carries grouping.
- Tighten inside, open between.
- Try proximity before borders.
- Squint at it to check.
When do you raise fidelity?
The strongest answer: When the argument has moved to hierarchy, type, or a system token — I do not polish to end a flow fight
Why it works: Exactly. Match the argument. Bored-polish and polish-to-trap are politics.
- Raise fidelity when the argument needs it.
- Do not polish to end a flow fight.
- Do not polish because someone is bored.
- Do not trap stakeholders with polish.
A five-step form with a file upload. Modal or its own page, and why?
The strongest answer: Its own page — it is long, it can fail part-way, and people will want a link back to it; a modal suits a short interrupting task you finish and dismiss
Why it works: Right — length, recoverability and a linkable address decide it; a modal has nowhere good to put a failed upload.
- Match the container to the task.
- Modal: short, interrupting, dismissable.
- Page: long, failable, linkable.
- Ask where the error goes.
A results list of several thousand items, mostly opened on a phone.
Infinite scroll, pagination or load-more, and what decides it?
The strongest answer: What people do with the list: browsing suits load-more, while hunting for one item, returning to it, or needing the footer suits pagination with a stable, linkable position
Why it works: Exactly — the deciding question is whether someone must return to a position, not which feels modern.
- The task picks the pattern.
- Browsing: load more.
- Finding and returning: pagination.
- Keep the position linkable.