Design UX interview prep.

An enterprise designer is judged on four pillars: portfolio depth (real cases with research + process + decisions + outcomes), design critique (honest, structured feedback that improves the work), enterprise UX problem-solving (multi-role, workflow-complex, admin / permissions), and craft +...

What interviewers look for

  • Can the candidate walk a real portfolio case end-to-end - problem, research, process, decisions, tradeoffs, outcome - not just polished screens?
  • Do they give structured design critique - heuristics + accessibility + outcome-anchored, not 'I'd change the color'?
  • Can they solve enterprise UX - multi-role workflows, admin / permissions, dense data, configurability - vs consumer-app simplicity?
  • Are they design-system fluent - tokens, components, governance, contribution model - and respect-the-system without being mechanical?
  • Do they design accessibility-first - WCAG AA, screen-reader, color contrast, keyboard - rather than retrofit?
  • Are they research-disciplined - know when to interview vs usability test vs analyse data, can quote specific findings that changed a decision?

Behavioural questions to expect

  1. Walk me through your CV.

    What it tests: Story coherence + genuine fit for the enterprise design seat. Teams want evidence of B2B / enterprise context (not just consumer / brand), real shipping outcomes, and IC progression (junior → senior → staff).

  2. Tell me about your most impactful design project.

    What it tests: Depth of ownership + craft + outcome. Tests whether the candidate frames problem → research → process → decisions → outcome, defends tradeoffs, and surfaces a real measurable impact.

  3. Tell me about a weakness, a failure, or feedback you've received and worked on.

    What it tests: Self-awareness + craft discipline. Cross-role canonical. Fake weaknesses downgrade immediately. Designer mistakes (shipped without research, missed accessibility, broke the design system, missed the admin / power user) carry real product + team cost.

  4. Why enterprise SaaS design - and why this vs consumer?

    What it tests: Authentic fit for the complex, multi-role, research-heavy enterprise design seat: workflow depth + admin / permissions + design-system rigor + measurable business impact, vs consumer's faster / shallower / brand-led work.

  5. Which design area would you want to own, and why?

    What it tests: Genuine fit + grasp of how enterprise design areas differ. Tests whether the candidate has a reasoned preference (workflow / data-viz / admin / mobile / design system / research) rather than 'wherever you put me'.

  6. Why this firm?

    What it tests: Whether the candidate has done the homework. Bar: firm-specific evidence from the product, design team, design system, customers, and people - not generic 'great product'.

  7. How would you describe this firm's design organisation + product in your own words?

    What it tests: Whether the candidate has internalized HOW the firm designs - team shape, system maturity, research practice, live debates - not just that it 'has designers'. Tests whether they've used / studied the product.

  8. How does design actually create value at an enterprise SaaS firm?

    What it tests: Whether the candidate understands enterprise design economics: faster activation + lower support volume + higher NPS + reduced churn risk + sales enablement (demo-ability) - design impact is real + measurable, not just aesthetic.

Technical concepts to master

Design process + the double diamond

Discover + define (first diamond)
Discover: open exploration of the problem space (research, interviews, data, ecosystem map). Define: synthesize to a clear problem statement + JTBD + success criteria.
Develop + deliver (second diamond)
Develop: diverge on solution ideas (sketches, wireframes, prototypes, alternatives). Deliver: converge on the design that ships, with engineering + accessibility + system constraints integrated.
Prototyping + fidelity progression
Low-fi (sketches, wireframes) for divergence + concept tests; mid-fi (clickable) for usability tests; hi-fi (production-ready) for stakeholder review + shipping.
Test + iterate
Usability tests with 5-8 users per cohort; analytics + support signal post-ship; iterate on data + qualitative; ship the next version.

Design system + tokens + components

Tokens
Atomic design values (color, type, spacing, radius, motion) defined once + referenced everywhere; the foundation of theme-ability + consistency.
Components
Reusable UI building blocks (button, input, modal, table) with defined variants + states + props; the design + engineering shared library.
Governance + contribution
Who owns the system, how new components / patterns get added, the RFC / review process for contribution; the system as a product with its own roadmap.
Documentation + adoption
Component docs (usage, do / don't, accessibility notes, code examples); adoption tracking (% of UI from system); designer + engineer onboarding to the system.

Multi-role + workflow complexity (enterprise B2B)

Role-distinct surfaces
Each role gets a surface designed for their job: admin needs configurability + observability; analyst needs depth + filters + export; end-user needs simplicity + speed; executive needs summary + status.
Workflow mapping
End-to-end flow across roles + steps + dependencies; identify handoffs, coordination points, decision moments; visualise complexity, don't hide it.
Admin + power-user design
Power users + admins need depth, keyboard shortcuts, bulk actions, configurability; design the happy path AND the depth.
Data-dense + analytics design
Tables, dashboards, filters, charts - data-heavy enterprise surfaces; the discipline is hierarchy + progressive disclosure + scannability.

Accessibility + inclusive design

WCAG 2.1 / 2.2 AA
The canonical accessibility standard: four principles (Perceivable, Operable, Understandable, Robust); AA is the enterprise bar (the higher top-tier conformance is rarely required, often impractical).
Screen reader + keyboard
Every interactive element must be keyboard-reachable + screen-reader-meaningful; tested with actual assistive tech (NVDA, JAWS, VoiceOver), not just automated tools.
Color + contrast + visual
4.5:1 contrast for normal text, 3:1 for large + UI components; don't rely on color alone for state; respect prefers-color-scheme + reduced-motion.
Inclusive design (beyond disability)
Designing for the full range of human diversity - cognitive load, situational impairments, low-bandwidth, language, locale, device; permanent + temporary + situational disability all matter.

Practical drills

  • Walk me through one of your strongest portfolio case studies - the design problem, the research, the process, the decisions, the outcome.
  • [Interviewer presents a screen or describes a flow.] Critique this design.
  • this firm has admin + analyst + end-user roles for a workflow product. Design the V1 multi-role admin surface. Sketch the dashboards, the permissions, and the key flows.

Smart-question anchors

  • Team + scope - the design team shape, what the role would specifically own in 6-12 months
  • Design system - the current state, governance, contribution model, design-engineering partnership
  • Research practice - dedicated researchers vs designer-led, cadence, customer advisory boards, how research influences decisions
  • Accessibility + craft posture - the firm's WCAG conformance, dedicated role, recent accessibility work
  • Critique + design culture - critique cadence, design reviews, how shipping decisions are made + how feedback flows

Related roles

Sourced from

Ready to Generate Your Own Prep?

Drop your CV and a job description on the home page. A couple of minutes later you get a report with everything you need to land the job.

Generate my first prep