Interview Questions / UX/UI Designer
30+ UX/UI Designer Interview Questions for Agency Hiring
A practical bank of questions, what to listen for, and red flags to help you hire an agency UX/UI designer who can handle research, systems, and high-craft visual work across multiple clients without cutting corners.
Why these questions?
Agency UX/UI designers carry more clients, more verticals, and more handoffs per quarter than their in-house counterparts. They need range across research, systems, interaction, and visual craft, and the discipline to ship great work within commercial constraints. The questions below test for process, craft, and the collaboration skills that separate strong agency designers from talented individual contributors who struggle with the agency rhythm. Use the bank as a library and pick 8 to 12 questions that fit the seniority and project mix you're hiring for.
General & background (5)
Walk me through your career and how you ended up doing UX/UI design at an agency.
What to listen for
Coherent narrative: training (formal or self-taught), early product work, deliberate moves toward agency life. They should explain why agency over in-house product teams.
Red flags
- Cannot articulate why they chose agency over product
- Story is purely a list of clients with no growth arc
- Treats UX/UI as a fallback after a different career
How do you describe the difference between UX and UI in your own work?
What to listen for
Honest about where they spend more time, comfortable with the overlap, and able to articulate the tradeoffs at each end. Avoids the false dichotomy that one is "thinking" and the other is "decorating".
Red flags
- Strict separation that suggests they only do one well
- Dismisses UI as "just visuals"
- Cannot explain how research informs interface decisions
What kind of projects and team sizes have you worked on?
What to listen for
Specific project types (marketing sites, SaaS products, mobile apps, design systems), team compositions, and clarity on what they owned end-to-end vs collaborated on.
Red flags
- Vague descriptions with no specifics
- Inflates scope (claims solo ownership of clear team work)
- Cannot describe a single project end-to-end
Why are you leaving your current agency or studio?
What to listen for
Honest, growth-oriented reasons. Even when frustrated, they speak about previous employers with fairness.
Red flags
- Trash-talks every previous employer
- Blames clients or PMs for design quality
- Leaving after less than a year with no clear narrative
Whose work do you study and why?
What to listen for
Specific designers, studios, or products with concrete reasons. Goes beyond Awwwards-of-the-day taste and can articulate craft, systems thinking, or research approaches.
Red flags
- Cannot name anyone
- Only names trendy studios with no analysis
- Vague "I just like clean design" answers
Role-specific skills (10)
Walk me through your end-to-end process on a recent project from kickoff to handoff.
What to listen for
Discovery, research synthesis, IA and flows, low-fi to high-fi iteration, prototyping, usability validation, design system contribution, dev handoff, and post-launch review.
Red flags
- Skips research entirely
- Goes straight to high-fi without exploration
- No usability validation or post-launch review
How do you decide what fidelity to work at for a given problem?
What to listen for
Matches fidelity to the question being answered: sketches for divergence, wireframes for structure, high-fi only when interactions or visual decisions need testing. Avoids high-fi too early.
Red flags
- Always works in high-fi from the start
- Refuses to use anything but Figma
- Cannot articulate why fidelity matters
Walk me through how you build or extend a design system for a client.
What to listen for
Audit existing patterns, token-first approach, component composition, documentation alongside design, governance plan, and partnership with engineering on naming and structure.
Red flags
- Builds components in isolation with no tokens
- No documentation or governance plan
- Treats the design system as a one-time deliverable
How do you incorporate user research into your design decisions when you only have a small budget for it?
What to listen for
Lightweight methods (5-user usability tests, guerilla research, analytics review, support ticket mining), focused research questions, and synthesis that ties to specific design decisions.
Red flags
- Refuses to design without large research studies
- Skips research entirely when budget is small
- Conducts research but cannot tie findings to design changes
How do you approach accessibility in your work?
What to listen for
WCAG awareness baked into the process, color and contrast checks, keyboard navigation, screen reader considerations, focus states, and partnership with engineering on semantic markup.
Red flags
- Treats accessibility as a final check or afterthought
- Cannot name a specific WCAG criterion they apply
- Says "the developers will handle it"
How do you handle dev handoff so engineering can build the design accurately?
What to listen for
Tokens and components organized for engineers, annotation only where needed, prototypes for interactions, attendance at standups during build, and a feedback loop on what shipped.
Red flags
- Throws Figma over the wall and disengages
- Annotates everything, treating engineers as unable to read the design
- Has never reviewed shipped work against the design
Walk me through how you would redesign a checkout flow for a client.
What to listen for
Starts with the business and user goals, audits current funnel data, maps the existing flow, identifies friction points, designs and tests alternatives, plans the rollout (AB test, phased), and defines success metrics.
Red flags
- Skips the data audit
- Designs from personal preference rather than evidence
- No measurement plan
How do you handle visual design when you inherit a brand you find limiting?
What to listen for
Respects the brand as a constraint, finds creative space within it, proposes evolution where appropriate with rationale, and avoids trying to redesign the brand under the radar.
Red flags
- Tries to redesign the brand without permission
- Refuses to work within the constraints
- Cannot articulate where the brand is and isn't flexible
What is your approach to motion and micro-interactions?
What to listen for
Functional first (orientation, feedback, continuity), restrained, considers performance and accessibility (prefers-reduced-motion), and prototypes before handoff.
Red flags
- Adds motion as decoration without purpose
- Ignores prefers-reduced-motion
- Cannot prototype motion they design
How do you collaborate with copywriters or content strategists on UI work?
What to listen for
Treats copy as a first-class design element, designs with real content not lorem ipsum, partners on microcopy decisions, and adapts layouts to copy length variability.
Red flags
- Designs with lorem ipsum and hands off to copy later
- Sees copy as someone else's problem
- Ignores empty states and error messaging
Agency-specific scenarios (6)
You're juggling three active client projects and one is suddenly a fire. How do you decide where your hours go?
What to listen for
Triages on commitment, commercial impact, and what is actually moveable. Communicates proactively with the deferred clients via the PM, and protects the other deliverables' deadlines.
Red flags
- Quietly tries to do everything and misses deadlines
- Drops the other projects without communication
- Has no triage framework
A client keeps requesting "small visual tweaks" round after round. How do you handle scope creep?
What to listen for
Logs revisions, distinguishes refinement from new direction, raises the pattern with the account or project manager, and proposes a change order or process change.
Red flags
- Absorbs every revision silently
- Confronts the client directly without account management
- Has no view on what counts as in-scope vs out-of-scope
A client says "make it pop" without specifics. How do you respond?
What to listen for
Asks structured questions (which element, what reaction, examples they like), offers two contrasting directions to calibrate, and translates the vague request into a testable design hypothesis.
Red flags
- Adds gradients and shadows randomly
- Gets defensive about the original design
- Cannot extract specifics from vague clients
Your client wants to skip user research because "we already know what users want." How do you handle it?
What to listen for
Acknowledges the constraint, proposes lightweight alternatives (analytics review, support ticket mining, 5-user tests), shows the cost of skipping research with examples, and adapts to the client's actual budget.
Red flags
- Refuses to start without full research
- Caves and skips research entirely
- Cannot make the business case for any research
A client's in-house team disagrees with your design direction in a presentation. How do you handle it in the room?
What to listen for
Stays calm, asks clarifying questions to understand the objection, distinguishes taste from strategic concerns, offers to take the feedback away and respond, and avoids defending in real time.
Red flags
- Argues the design in the moment
- Caves to the loudest voice
- Takes the disagreement personally
You discover that the previous designer's work for this client has accessibility violations. How do you communicate this?
What to listen for
Documents the issues factually, raises with the account manager and client diplomatically, proposes remediation as a separate workstream, and avoids public callouts of the previous designer.
Red flags
- Uses it as a sales weapon against the previous designer
- Hides the finding to avoid hard conversations
- No remediation plan
Behavioral / STAR (5)
Tell me about a project that was a real success. What made it work?
What to listen for
STAR format with specifics: the problem, the design decisions, the constraints, and a measurable outcome (conversion lift, task completion, satisfaction). Self-aware about luck vs craft.
Red flags
- Vague narrative with no metrics
- Cannot explain why the project worked
- Credit goes entirely to the team or luck
Describe a time a client or stakeholder rejected your direction. What did you do?
What to listen for
Took the feedback seriously, asked good questions, distinguished taste from strategic concerns, revised, and reflected on what to change in their process going forward.
Red flags
- Took it personally and disengaged
- Refused to revise
- No reflection on what they would do differently
Tell me about a disagreement with an engineer or PM where you were wrong.
What to listen for
Genuine reflection, can name what they changed in their work afterward, credits the colleague.
Red flags
- Cannot name a time they were wrong
- Frames the disagreement as miscommunication
- Still blames the colleague
Describe a project where your design did not perform as expected after launch. What did you learn?
What to listen for
Honest about the miss, dug into the data to understand why, partnered with engineering and analytics to fix, and applied the learning to future work.
Red flags
- Claims their work always performs
- Blames implementation entirely
- No follow-up on shipped work
Tell me about a time you made a costly design mistake.
What to listen for
Honest about the mistake (regression in the design system, accessibility miss, dark pattern), names the cause, and the systemic change made afterward.
Red flags
- Claims no mistakes
- Blames teammates or the brief
- No process change to prevent recurrence
Technical & portfolio review (4)
Walk me through three projects from your portfolio and explain the decisions behind them.
What to listen for
Range across project types, articulation of brief and constraints, awareness of what worked and what they would change, and ownership of the result.
Red flags
- Submits only one project type
- Cannot explain decisions in any project
- Takes credit for team work without distinguishing their contribution
Show me a Figma file you built. Walk me through the structure (pages, components, tokens, naming).
What to listen for
Organized pages, named layers and components, token usage, auto layout fluency, variants used appropriately, and clear handoff frames.
Red flags
- File is a chaotic mess of layers
- No tokens or components
- Cannot navigate their own file
Walk me through a design system component you built from scratch. Why those variants?
What to listen for
Started from real product needs, considered states (default, hover, focus, disabled, loading, error), accessibility, content variability, and worked with engineering on naming.
Red flags
- Built variants for every conceivable state without justification
- Missed key states (focus, error, loading)
- Built in isolation from engineering
Which research, prototyping, and handoff tools do you actually use day-to-day?
What to listen for
Names specific tools (Figma, Maze, Dovetail, Notion, Loom, Storybook for handoff context) and describes how they fit into the workflow.
Red flags
- Lives in Figma alone with no other tools
- Names tools but cannot describe a real workflow
- Has never used a research or prototyping tool
Culture fit (3)
What kind of projects or clients do you not enjoy, and how do you handle them anyway?
What to listen for
Self-awareness paired with professionalism. They name the archetype (eg vague briefs, aesthetic-driven clients) and the workaround.
Red flags
- Says they love every project
- Describes clients with contempt
- No workaround, just complaint
When you disagree with a creative director or strategist on direction, what do you do?
What to listen for
Direct, private disagreement first, brings examples and rationale, commits publicly once decided, and revisits with results later.
Red flags
- Complains to peers
- Never disagrees
- Lets disagreement fester into disengagement
What does a great first 90 days look like for you in this role?
What to listen for
Concrete plan: shadowing client calls, learning the design system and tooling, calibration projects with feedback, and one or two early wins shipped.
Red flags
- Arrives with a prescriptive overhaul before listening
- No milestones or deliverables
- Focused only on internal process, ignoring client work
Portfolio evaluation
Strong UX/UI candidates can walk you through real work and the decisions behind it:
- Three projects across different fidelities and project types (marketing site, product UI, design system).
- Sketches, wireframes, or research artifacts (not just polished final screens).
- One project they would design differently today and why.
- A project with a measurable post-launch outcome.
- A short narrative of one engagement from kickoff to dev handoff and beyond.
Refusal to share anything at all (even disguised) is itself a signal.
Frequently asked questions
How long should a UX/UI designer interview process be?
Most agencies run three to four stages over two to three weeks: a recruiter screen, a portfolio walkthrough, a design exercise, and a panel with engineering and a creative or design lead. Anything longer than four weeks tends to lose strong candidates.
Should we use a take-home design exercise or an in-person whiteboarding session?
Most strong agencies use a short, paid take-home (four to six hours) with a follow-up walkthrough. Live whiteboarding favors performative thinkers and disadvantages introverts. Always pay for take-home work.
What is the biggest predictor of success in an agency UX/UI designer?
Range across fidelity and craft, plus the discipline to ship within constraints. Candidates who can move from sketches to dev handoff without losing rigor tend to outperform pure visual designers in agency settings.
Should we hire generalists or product specialists?
Most agencies need designers comfortable across marketing sites, product UI, and design systems. Hire for systems thinking and craft first, vertical expertise second. Pure product specialists may struggle with the breadth of agency work.
How do we evaluate a portfolio with mostly NDA-protected work?
Ask for verbal walkthroughs of the process, sketches, and decisions even if final visuals can't be shared. A candidate who can't talk through any project is a red flag, regardless of NDAs.
Run your agency like it's 2026
AgencyPro gives design teams the project planning, client reporting, and operational tooling they need to ship great work without the chaos.
Book a demo