Define the work, required evidence, and interview criteria before sourcing UX Designer candidates. This guide turns the role into a consistent, auditable hiring process.
Settle whether your biggest gap is research, information architecture, or interaction design, then hire against it. Candidates should show how they found a user problem, what evidence shaped the structure they proposed, and how they checked it with real people. Artifacts such as research plans, journey maps, and test findings carry more weight than final screens.
UX designers can lean toward research, structure, or hands-on interface work, and a profile that fits a complex enterprise tool may not fit a consumer app. The notes below help you set the weighting for your team before you compare case studies.
What UX Designers do day to day
The core work of the role, before tools and titles. Check that your brief, your interviews, and your scorecard all cover it.
Research how users work and where they struggle
Design flows, information architecture, and wireframes
Test designs with users and iterate
Document UX decisions for teams
Skills to look for in UX Designers
Group requirements by area so the job post, the interview plan, and the scorecard test the same things.
01
Research
Interviews, usability tests, and synthesis.
02
Interaction design
Flows, information architecture, and wireframes.
03
Accessibility
Inclusive design and standards.
Which specialization do you need?
Most UX Designers lean toward one of these. Name the one you need in the brief instead of listing every tool.
UX research
Research-heavy roles.
Information architecture
Navigation and content structure.
Service design
End-to-end customer journeys.
UX Design role levels and evaluation evidence
Adjust the scope to the actual job. Seniority should reflect decision ownership and the complexity of the work, not years alone.
1
Junior
Typical scope
Entry-level profile with a strong foundation in usability testing, wireframing, and basic journey mapping.
Knowledge areas
FigmaOptimal WorkshopHotjarZoom
What to look for
Must conduct moderated user interviews and document findings. Requires capability to execute low-fidelity prototypes.
2
Mid
Typical scope
Mid-level profile with proven expertise in information architecture, complex interaction logic, and behavioral data synthesis.
Knowledge areas
FigmaDovetailAxureLookback
What to look for
Must design scalable navigation structures for dense information environments. Requires application of heuristic evaluations to existing products.
3
Senior
Typical scope
Senior profile with deep mastery of GenUI constraint systems, cross-platform experiential strategy, and neuro-inclusive accessibility.
Must define the semantic tokens used by AI-generated interfaces. Requires oversight of global accessibility compliance initiatives.
What should a UX Designer role brief include?
Describe the user groups, the complexity of the information they work with, and the research methods available to the team. Say who the designer partners with and whether they run studies themselves. Interviewing, structuring content, and synthesizing evidence are must-haves; your analytics stack and specific recruiting panels can be learned.
User groups and the main tasks they need to complete
Research methods expected, such as interviews, usability sessions, or surveys
Existing research repository and access to participants
Deliverables the team relies on, from flows to navigation maps
How should UX Designer candidates be compared?
Give each candidate the same scenario: a small product problem with a short user summary and a few raw interview notes. Ask for a research plan, a proposed structure, and the questions they would test first. Strong evidence shows clear reasoning from observation to design choice and honest acknowledgment of what the data cannot tell them.
Provide the same raw interview notes and ask for synthesized themes
Request a lightweight usability test plan with success criteria
Ask how findings would be reported to non-designers
Score evidence use, structure quality, and communication on one rubric
What to probe when interviewing UX Designer candidates
These are risks a weak hire in this role tends to bring. Turn each into a work-sample task or follow-up question that produces evidence for or against it, and score every candidate on the same set.
Can they architect information hierarchies for dense data environments, or do they just arrange elements aesthetically?
Have they designed constraint systems for AI-generated interfaces where spatial consistency no longer applies?
Is their accessibility expertise rigorous enough for WCAG compliance, or do they treat it as a checkbox exercise?
Job description template
A starting draft built from this guide. Replace the bracketed parts, cut anything that does not apply, and keep every requirement tied to the work.
Job description template
About the role
[Two or three sentences on the product, the team, and why this role is open now.]
What you will do
Research how users work and where they struggle
Design flows, information architecture, and wireframes
Test designs with users and iterate
Document UX decisions for teams
What you bring
Research: Interviews, usability tests, and synthesis.
Interaction design: Flows, information architecture, and wireframes.
Accessibility: Inclusive design and standards.
Nice to have
UX research
Information architecture
Service design
Level and scope
Junior: Entry-level profile with a strong foundation in usability testing, wireframing, and basic journey mapping.
Mid: Mid-level profile with proven expertise in information architecture, complex interaction logic, and behavioral data synthesis.
Senior: Senior profile with deep mastery of GenUI constraint systems, cross-platform experiential strategy, and neuro-inclusive accessibility.
How we hire
A structured interview and a short work sample, scored against the same criteria for every candidate.
Full-time, contract, or freelance?
Hire full-time when UX work is continuous across products. A contractor fits a usability study or a redesign. Ask how research changed a design decision.
FAQ
Frequently Asked Questions About Hiring UX Designers
Direct answers for role definition, evaluation, specialist depth, and compensation research.
What does a UX designer do?
A UX designer studies how people use a product and shapes its structure, flows, and interactions to make tasks easier. Typical work includes user interviews, journey mapping, wireframes, prototypes, usability tests, and heuristic reviews of existing screens. They translate findings into recommendations for product managers and visual designers, and they track whether changes actually reduced friction.
What should I look for in a UX designer's skills?
Look for research method selection, synthesis, information architecture, interaction design, and prototyping. Add facilitation skills, clear writing, and accessibility awareness. Familiarity with tools like Figma or a research repository is useful evidence, but ask how the candidate chose their methods and how they handled contradictory feedback. Strong candidates explain limits as well as findings.
How do I evaluate a UX designer candidate fairly?
Use the same case-study questions, the same scenario exercise, and the same scoring rubric for every candidate. Ask them to show process artifacts and explain their personal part in the project. Include a short role-play where they present findings to a skeptical stakeholder. Write down evidence for each competency before the panel discusses who impressed them most.
When should I hire a UX researcher instead of a UX designer?
A dedicated researcher fits when you need ongoing, rigorous studies and the design team cannot run them alongside delivery. A UX designer fits when research must feed directly into structure and flows. Seniority shows in choosing the right method for the question and influencing roadmaps. Small teams often want a designer who does both at lighter depth.
How is pay set for UX designers?
Pay moves with location, seniority, industry, and how much of the role is research versus interface work. Specialized domains such as healthcare or finance may command different ranges. Collect current local salary data and comparable postings, record the dates, and match the range to the responsibilities in your brief. Review it again whenever the scope of the role changes.
ConnectDevs can support discovery and structured interview workflows, but the hiring team remains responsible for the role definition, evidence standard, final decision, compensation validation, and applicable legal review.