Technical screening questions
Ask for one example per question and listen for specifics.
- Walk me through a project from research to launch. A good answer: Problem, research, iterations, handoff and results.
- How do you test a design with users? A good answer: Tasks, participants and what changed afterward.
- How do you handle developer pushback? A good answer: Trade-offs and shared constraints.
- How do you make a design accessible? A good answer: Contrast, keyboard use, labels and screen readers.
- How do you maintain a design system? A good answer: Components, documentation and governance.
Quick screening questions
Use these when you have only a few minutes.
- Walk me through a project from research to handoff.
- How do you work with developers on edge cases?
- How do you test designs with users?
What separates the levels
Match the level to the requirement before you submit.
- Junior: produces screens with guidance.
- Mid: owns flows end to end.
- Senior: sets design strategy and systems.
Red flags
Any of these is a reason to probe further.
- Portfolio shows visuals but no process.
- No user research.
- Cannot discuss accessibility.
Tools you should hear mentioned
A UI/UX designer with real experience usually names several of these without prompting.
- Figma
- Prototyping tools
- User testing tools
- Design systems
- Accessibility checkers
- Analytics
Run the call well
Ask for the last project first, then dig into the second or third question. Take notes on versions, team size and outcomes, and record them with the submission so the vendor’s later technical interview does not surprise you.
Frequently asked questions
How long should a UI/UX designer screening call take?
Fifteen to twenty minutes is enough to cover the project, three technical questions and availability, rate and work authorization.
Do recruiters need to know the technology?
Working vocabulary is enough. Use the sourcing guide for the role and listen for specifics instead of judging technical depth yourself.