How to Hire a UI/UX Designer

Volume is the defining feature of this title. Expect a wide mix: career changers from bootcamps, agency generalists, freelancers moving in-house, and a smaller number of genuinely end-to-end designers who could hold either specialist title. Most portfolios in the pile lean visual, with research described in one line and no evidence it altered any screen. That is not disqualifying, but it means your filter has to look for the rarer combination rather than the prettier deck. Sourcing works best through portfolio-first applications, freelance-to-permanent conversions, and referrals from agencies that staff generalists. Syndicating the ad through [job posting software](/job-posting-software) widens reach, though the quality filter still has to happen at portfolio review.

Be blunt about the split. Writing "roughly seventy percent interface work, thirty percent talking to customers" saves everyone weeks, because specialists who want one or the other will opt out early. Say there is no researcher, no design manager and no existing component library if that is the truth. Name the first project concretely, such as rebuilding the signup flow and establishing the first component set. State how many engineers the person supports and who signs off on design decisions when opinions collide. Describe the constraints as facts, not apologies; generalists who thrive in small teams are usually attracted by exactly the messiness that specialists avoid. Adapt the responsibilities from the [UI/UX designer job description](/job-descriptions/ui-ux-designer), then cut anything you cannot honestly provide.

Make the portfolio link a required field and treat everything else as secondary. Then apply one decisive filter: does at least one project show research or user feedback visibly changing the interface? That single question separates the end-to-end designers from the visual designers using a broader title. Add one short scenario question at application, such as how they would decide what to build first with no research budget, because written answers expose reasoning cheaply at scale. Junior-heavy funnels reward structure, so use knockout questions and [recruitment automation](/recruitment-automation) to handle acknowledgements and stage movement while you spend human attention only on portfolio review. Reply to everyone, including rejections, because design communities are small and talk to each other.

Compress it to three stages, because this candidate pool moves quickly and drawn-out loops cost you the strongest people. Stage one is a portfolio conversation focused on the project where they did both halves. Stage two is a paid mini brief with a fixed three-hour cap: a real problem, ending in a user flow and one high-fidelity screen, presented back with the reasoning. Stage three is a working session with whoever they will report to, covering how they operate without a design team, how they prioritize when everything is urgent, and where they will ask for help. Pull discussion prompts from the [UI/UX designer interview questions](/interview-questions/ui-ux-designer) so the panel stays consistent.

Breadth costs depth, and that trade is worth making consciously. One designer covering research, interaction and visual work will be genuinely good at some of it and adequate at the rest, so decide in advance which half you can afford to have merely adequate. Plan to supplement: contract research before major bets, or a contract visual designer when brand work spikes. Expect a retention conversation within a couple of years, because many generalists eventually want to specialize somewhere. Budget for tooling and occasional contract support alongside salary rather than pretending one hire removes every design need. None of that makes the decision wrong. It makes it a deliberate staffing choice with a known expiry date, which is a far better position than discovering the gaps during a critical launch.