How to hire a designer in 2026

Figure out why you're hiring before you look at a single portfolio

You have a real reason for hiring a designer right now, even if you haven't put it into words yet. That reason should decide who you start talking to. It doesn't work the other way around.

Match your situation to what matters most in the person you pick:

• Launch or first real customer call coming up: you need someone who can catch technical and UX flaws you've stopped being able to see.
• Raising money: you need restraint over cleverness. Investors read polish as a signal before they read the deck.
• Traffic exists, conversions don't: you need someone who asks for your analytics before they open Figma.
• A fixed date you can't move: you need someone who can hit a deadline, not someone still exploring "vibe."

Skip this step and you'll pick based on whichever portfolio you liked best, and end up with a skilled designer who's wrong for the problem you actually have.

Agency, freelancer, in-house, or a design partner

Once you know why you're hiring, the model follows. A freelancer is fast and cheap until they go quiet mid-project, because you're one of several clients competing for their week. An agency brings process and a full bench, but you're often handed a junior re-briefed every few weeks while an account manager sits between you and the actual work. In-house gives you full ownership and context, but it's 6-8 weeks to hire and another month before anyone's shipping at speed, plus a $120K+ salary line you're stuck with if priorities shift. A design partner or retainer sits in the middle. It's the model I run at Humbl: embedded like a team member, daily communication, senior-level output, without the overhead of a full-time hire or an agency's layers.

Match the model to the reason from the last section, not to whichever option sounded best on a sales call. If you want the full breakdown of when each model makes sense, including real cost comparisons, I wrote the long version of this argument here.

Write the brief before you talk to anyone

Before you reach out to anyone, write down the goal, who the page or product is for, what success looks like, and the timeline and budget you're working with. Signups. Demos. A specific number.

The brief does double duty. It's also your first filter. Send the same brief to three people and watch what comes back. One repeats it back to you with a few polished words swapped in. Another asks two or three sharp questions before committing to anything. The second person is thinking with you. The first is waiting to be told what to do.

A designer who never pushes back on a brief isn't being agreeable. They're executing blindly, and blind execution is exactly what you're trying to avoid.

Once you've picked someone, get the brief confirmed in writing before work starts: what's included, revisions, payment, and who owns the final files. Twenty minutes now saves you the argument that shows up three weeks in.

Screen for how they think

A portfolio shows you what someone can execute. It doesn't show you how they think, and thinking is what you're paying for.

Ask every candidate to walk you through one real client: what that founder was struggling with, what changed, and what happened after. Listen for whether they describe the client's problem or their own process. Someone who can explain, in plain language, what was going wrong for a past client has probably solved that kind of problem before. Someone who can only walk you through their own workflow is still figuring that part out.

You're hiring someone who can walk into a business they've never seen, understand what's broken, and fix it. Ask questions that test for that.

Use the first call to test their expertise

The first call is the highest-signal hour you'll get before you pay anyone anything. I've sat on both sides of that call enough times to know most of it gets spent on a pitch instead of a real conversation.

A good sign: they ask you questions before they tell you anything about themselves. They want to understand what's not working, who your customers are, and what you've already tried, before they say a word about how they'd fix it. They lead the conversation toward your problem.

A weak sign: the call turns into a tour of their workflow or their tools, or a pitch generic enough to work on anyone. If you leave knowing more about how they use Figma than about whether they understood your business, you have your answer.

By the end of the call you should feel like you talked to someone who gets it, not someone waiting to be told what to do. If you're still unsure, a small paid trial on one page or one screen is a cheap way to settle it before committing to the full project.

Look for proof that's already public

Tracking down and calling a stranger's past clients is a lot to ask of you, and you probably won't do it. Skip the reference call and look for proof that's already sitting in public.

Check LinkedIn recommendations written by founders, not just other designers. Read what they post about and whether it sounds like someone who's solved business problems or someone performing expertise. Ask for one or two case studies with a real result attached, not just a gallery of redesigns. A result you can name, like a raise, a launch date hit, or a number that moved, tells you more than a portfolio ever will.

The red flags that predict a bad hire before you've spent a dollar

Most of these show up before you sign anything. The problem is you don't know to look for them until after.

• No example of ever telling a client no. Someone who's always agreed with every client has never been given room to have an opinion, or doesn't have one.
• A different person shows up to do the work than the one who sold you on the call. Ask directly who's designing this, and whether they're still the one doing it in month three.
• Days of silence when you send a real question, especially the week of a launch or a fundraise. Test it before you're relying on it. A slow reply during a quiet week tells you nothing. A slow reply when it matters tells you everything.
• A brief that comes back reworded instead of challenged. If nothing you wrote got pushed on, nobody read it critically.
• Vague answers about ownership, timeline, or revisions when you ask directly. Precision costs nothing if the answer is already true.

What you end up with when you get this wrong

Skip this process and the failure won't look dramatic. It'll look like your site, technically fine, quietly leaking the money you already spent getting people to it. A 2026 industry estimate puts a typical underperforming startup site at 1.2% conversion, against 3-4% for the same traffic done right. Same ad spend, same cold emails, same favors you called in for the intro. The difference is 12 signups or 40 off the exact same budget.

It'll also look like the small stuff you won't catch until it's live. A 2026 audit of 100 AI-generated landing pages found the same failures over and over: broken social share previews, missing alt text, heading hierarchy that jumps from H1 straight to H4, default favicons, copyright dates nobody updated. None of it shows up when you're the one staring at your own homepage every day. All of it shows up to Google, to screen readers, and to whoever shares your link on Slack.

None of this is a talent problem. It's what happens when you skip the process above and the wrong person ends up holding your brief.