Intermediate everything in Design & UX, page 2
Client-side versus server-side A/B testing
Client-side flickers and is bypassable; server-side assigns before response, hides logic, suits backend changes.
Recruiting channels for a B2C usability study
Compare panels for speed versus in-product intercepts for authenticity, weigh cost, screening rigor, and bias.
Turning a vague onboarding goal into research questions
Define success metrics, decompose the funnel, pair quantitative drop-off with qualitative why.
Why A/B-only, no upfront research, costs engineers more
A/B testing optimizes within a chosen direction but cannot reveal the right problem; building wrong wastes engineering cycles and tech debt.
Generative versus evaluative research in sprints
Generative explores problems before building and feeds requirements; evaluative tests solutions during and after build and feeds fixes.
Confidence intervals versus p-values, explained simply
Define a CI as a plausible range for the true effect with its precision, contrast it with a binary p-value, and read [-1%, 7%] as inconclusive because it spans zero.
Diagnose and validate a failing usability task
Pinpoint the failure step from session and telemetry data, form a root-cause hypothesis, ship a targeted fix, and re-test to validate.
Build a compliant participant recruitment database
Capture granular, timestamped consent with lawful basis; minimize, encrypt, and retention-limit storage; and build self-service deletion that cascades.
Anonymization vs pseudonymization and key handling
Anonymization is irreversible and exits GDPR scope; pseudonymization is reversible via a separated key; secure that key in a KMS with strict access.
Exposure Hours
Exposure hours measure the time each team member spends directly observing real users. Research by UIE found teams that watch users at least two hours every six weeks make markedly better design decisions, because firsthand empathy beats secondhand reports.
Mental Model Diagram
A mental model diagram aligns what users think and do, gathered from research, against what a product actually offers, exposing gaps where features are missing or unused so teams build for real behavior rather than assumptions.
Refactor a legacy UI for accessible DOM flow
Align DOM order with reading order, use semantic landmarks and headings, and ensure a sensible tab order with managed focus.
Manage light and dark themes with Variables and Modes
Separate primitive and semantic variables, define light and dark modes in one collection, and bind UI fills to semantic tokens.
Make a complex component accessible by design
Define keyboard model and focus order, map to ARIA roles and states, and document interactions for engineers.
Diagnose a slow, laggy Figma prototype
Heavy raster images and effects, layer and node count, and excessive prototype interactions.
Prototype a draggable carousel with On Drag
Lay frames side by side, use On Drag with Smart Animate, and clamp ends.
SVG icons versus icon fonts: technical trade-offs
SVG is vector markup, crisp, multicolor, accessible, and tree-shakeable; icon fonts ship as glyphs, risk anti-aliasing blur, accessibility hacks, and load-failure boxes. Advocate SVG for modern apps.
Designing and documenting focus order in Figma
Focus order is the sequence keyboard and screen-reader users traverse interactive elements; it should follow meaning and reading order, documented in Figma via layer order, numbered annotations…
Profile card with nested Auto Layout sizing
Outer vertical frame set to fixed width and hug height, an inner horizontal frame for avatar and name, and a bio text set to fill width and auto-height so the card grows down.
Building a scalable icon system in Figma
Standardize a grid, size, and stroke; make each icon a component with consistent naming, use currentColor-friendly single-color paths, and export optimized SVGs.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles