Hiring for UX

What portfolios and interviews really tell you

Key Takeaways

Portfolios tell you how someone thinks, not just what they’ve shipped. Social skills and team fit matter more than technical ability. And the job description is already part of the hiring process – most teams just don’t treat it that way.

Hiring for UX is one of those things that looks straightforward until you’ve done it a few times.

You post a job. CVs arrive. You review portfolios. You run interviews. Someone gets an offer. And then three months later you realize the person you hired is technically capable but genuinely struggling to work with the rest of the team. Or the portfolio looked polished but the thinking behind it was shallow. Or the interview went brilliantly and the day-to-day is a different story entirely.

There’s a reason this keeps happening. Most processes screen for the wrong things.

Start Earlier Than You Think

The hiring process starts before the first CV lands. Specifically, it starts with the job description – and most JDs for UX roles are written by people who understand recruitment but not UX.

The result is usually a list of tools and years of experience and buzzwords that filters out good candidates and attracts candidates who are good at describing themselves in buzzwords. Not the same group.

Get involved early. Negotiate what’s truly essential. Push back on requirements that sound reasonable but aren’t – “5+ years Figma experience” for a mid-level role, for example, when Figma hasn’t been the industry standard for 5 years. The language you use in a JD already signals what kind of team you’re building and what kind of person would thrive in it.

The job description is the first design artefact in your hiring process. Treat it like one.

Before you write the JD, two questions are worth answering explicitly – because most teams skip them and hire reactively instead of strategically.

What is the missing puzzle piece? Look at who is already in the team – not just titles, but actual capabilities. Where is the depth thin? If everyone can do visual craft but nobody runs structured research, you don’t need another generalist. A simple competency map, even a rough one, shows what the team has against what the product actually needs. That gap is where the hire should land. Hiring a strong version of what you already have is the most common mistake in UX team building.

Where does the design org need to be in two to three years? A hire is a medium-term bet on capability, not a solution to this quarter’s backlog. If the product roadmap moves toward AI-integrated features, the next designer needs different fluencies than the last one. If the company is scaling internationally, accessibility and localisation expertise matter more than they did last year. If the organisation is trying to move up in UX maturity, a researcher who can influence product decisions is worth more than a fifth visual designer. Hiring toward tomorrow’s capability is how design orgs grow with intent. Hiring to fill today’s gap is how they stagnate.

The best hiring processes start with this question: not “who do we need right now?” but “what does this team need to become?”

What a Portfolio Actually Tells You

A portfolio is not a gallery. Or it shouldn’t be.

What matters isn’t how beautiful the final screens look – it’s what the work tells you about how someone thinks. Visual polish is easy to fake and hard to assess fairly. Process and problem-solving are harder to fake and much more predictive of what working with someone will actually be like.

When reviewing a portfolio, I’m looking at a few things specifically.

What was this person’s actual role? Did they shape the problem, or execute a brief? There’s nothing wrong with executing well, but those are different skills and different career stages.

Is there a clear line from research to insight to decision? Or does the thinking jump straight from “we did some user interviews” to “here’s the final design”?

What didn’t work, and what did they learn from it? Portfolios that show only successes are either not being honest or aren’t reflecting on their work. Both are worth knowing early.

One consistent red flag: portfolios where the candidate claims they did everything alone. UX is a team sport. Someone presenting their work as a solo achievement either isn’t being accurate or has been working in a way that should prompt a follow-up question.

Take-Home Assignments: Usually Not Worth It

Take-home tasks sound like a good idea. Give candidates a realistic brief. See what they produce. Assess the quality.

In practice, there are two problems.

First, they’re poor at predicting actual job performance. What someone does in a controlled assignment, with unlimited time and no team context, doesn’t correlate well with how they work under real conditions. Second, they filter out good candidates who have jobs and lives and can’t spend a weekend on an unpaid assessment for a role they’re not sure they want yet.

A better use of interview time: ask someone to walk you through a piece of their existing work in depth. You learn more from watching how they talk about past decisions than from evaluating a new artefact they produced under artificial conditions.

Ask them to pick two case studies. Not their best ones – the most interesting ones. The ones where something went wrong, or where the constraints were genuinely hard, or where they had to push back on a stakeholder. Those conversations reveal far more.

Social Skills First. Technical Skills Second.

This is the one that surprises people most when I say it out loud.

Technical ability matters. But UX design is fundamentally a collaborative practice. A designer who can’t present their work clearly, who shuts down in ambiguous situations, who struggles to give or receive feedback – that person will have a significant impact on the team around them, regardless of how good their designs are.

Team fit isn’t a soft consideration. It’s a concrete one, with real effects on team dynamics and productivity.

That means the interview itself is data. Not just what someone says, but how they communicate. How they handle a question they don’t know the answer to. Whether they show genuine curiosity about the role and the team, or are mostly there to perform.

And honestly – it goes both ways. The interview also tells you something about the organisation. How prepared you are. Whether the interviewers seem like people worth working with. Candidates are evaluating you too. The quality of the process signals the quality of the environment they’d be walking into.

What’s Changed in 2025/26

A few things have shifted in the last year that are worth understanding if you’re hiring now.

AI screening is the new first filter. According to research from UX Playbook and Maze, 78% of design managers are now using AI-assisted tools to screen portfolios before a human opens them. That changes what a portfolio needs to do in its first three seconds – impact has to be visible immediately, not buried in a case study narrative that rewards patient reading. If you’re reviewing portfolios, knowing you can then spot candidates who’ve adapted to the new picture versus those still building portfolios for 2019.

AI proficiency is an explicit hiring criterion. 78% of design managers consider AI tool proficiency when evaluating candidates. This doesn’t mean candidates need to be AI engineers. It means they should be able to speak to how AI tools fit into their research and design workflow – and ideally show evidence of it.

Niche expertise is outperforming generalist positioning. Hiring managers increasingly prefer candidates with demonstrated depth in a specific domain – health tech, fintech, design systems, developer tools – over candidates who claim to be good at everything. The jack-of-all-trades profile that worked in 2020 is less compelling in a market where AI can handle many of the generalist tasks. What’s genuinely hard to replace is domain expertise combined with strong UX judgment.

What to Do Next

1. Review your current job description with fresh eyes – or ask someone outside the team to read it. Does it describe the work you actually do, or a generic list of tools and years of experience?
2. Before your next interview, pick two case studies from the candidate’s portfolio and prepare specific questions about their process, constraints, and decisions. Go in curious, not evaluative.
3. Define your team fit criteria explicitly before the process starts. Write down what good collaboration looks like in your team. It makes gut feel into something you can actually discuss and defend.

Sources & Further Reading

• UX Hiring: Insights from a Design Recruiter – Nielsen Norman Group
• Hiring and Retaining UX Teams – Nielsen Norman Group
• Designing Case Studies: Showcasing A Human-Centered Design Process – Smashing Magazine
• Connected UX – A List Apart