UX DesignerInterview Answers

My process follows diverge-converge cycles: I start with discovery — user research, stakeholder interviews, analytics — to understand the problem deeply. I frame the problem with a clear problem statement and success criteria. I diverge with ideation — sketches, concepts, crazy-eights. I converge into wireframes and prototypes at increasing fidelity. I test with users early and often, incorporating feedback before handoff. Design isn't linear — I iterate based on evidence at every stage.

When time is short, I prioritise methods with the highest signal-to-noise ratio. Five guerrilla usability tests can reveal 85% of major usability issues. I recruit from internal pools (colleagues, existing customers) to reduce lead time. I use remote moderated testing with tools like Maze or UserZoom for quick turnaround. I synthesise findings in affinity maps within 24 hours so the team can act immediately. Good research doesn't have to be slow — it has to be purposeful.

I annotate designs clearly — explaining behaviour, edge cases, and the reasoning behind choices. I use tools like Figma with a well-organised component library that engineers can inspect. For stakeholders, I present in terms of user need and business impact, not aesthetics. I'm comfortable defending design decisions with evidence — user testing results, heuristic analysis, or analytics — rather than subjective preference. Good communication is the difference between a design that survives handoff and one that doesn't.

We were designing an onboarding flow based on assumptions about what new users needed. In testing, I discovered that users were overwhelmed by the volume of choices we presented upfront. They actually wanted to see the product working first, then configure it. We completely redesigned the flow — leading with a pre-configured demo state before personalisation — and onboarding completion improved by 35%. Without testing our assumptions, we'd have shipped the wrong thing.

Accessibility is a design requirement, not an afterthought. I design to WCAG 2.1 AA as a minimum: sufficient colour contrast (4.5:1 for normal text), clear focus states, touch targets of at least 44px, clear error messaging, and designs that work with screen readers and keyboard navigation. I use tools like the Stark plugin in Figma for contrast checking and involve accessibility review in every design critique. Accessible design is almost always better design for everyone.

I lead with curiosity, not defensiveness. I ask about the stakeholder's underlying concern — often "I don't like this" means "this doesn't solve my problem." I bring user data and heuristic principles to the conversation rather than opinion vs opinion. If I still disagree after hearing them out, I'm transparent: "Here's what the research tells us, and here's the risk I see in this direction." I'm willing to test competing approaches if the stakes are high enough. Design debates should be resolved with evidence.

Figma is my primary tool for everything from wireframing to high-fidelity design and prototyping. I use FigJam or Miro for collaborative workshops and journey mapping. For research, I use Dovetail for synthesis, Maze for unmoderated testing, and Lookback or UserZoom for moderated sessions. I use analytics tools (Mixpanel, FullStory, Hotjar) to inform design decisions with behavioural data. I'm also proficient enough in HTML/CSS to understand implementation constraints and communicate effectively with developers.

I define success metrics before I start designing: task completion rate, time on task, error rate, or user-reported satisfaction (using SUS or CSAT scores). I set baseline measurements before launch and track post-launch against those baselines. For business impact, I work with the PM to connect design outcomes to conversion, retention, or revenue metrics. Design that can't be measured can't be improved — and can't be valued by the business.