The Baseline Moved: What Clients Are Actually Hiring Designers For Now
August 20, 2026
Thank you!
Your submission has been received!
Your submission has been received!
Oops! Something went wrong while submitting the form.
More and more, the brief looks the same even when the job title doesn't. A client will come looking for a Principal Product Designer. The next will ask for a Design Technologist, or a Design Engineer, or an AI Product Designer, or — increasingly — just "a product builder." The label changes. What they're actually asking for has settled into something much more consistent.
Look past the job title and the brief reads almost the same every time: someone who can operate across product, technology and business at once. Someone who can sit with ambiguity instead of waiting for a clean spec. Someone who thinks in systems rather than screens, works closely with engineering instead of throwing files over a wall, has a real opinion on where AI actually adds value versus where it's just noise, and still cares — deeply, stubbornly — about the quality of what actually ships.
That's a wide brief for one person. It's also, increasingly, the only brief that matters.
Strip away the title and what clients want comes down to four things: judgment, technical fluency, commercial awareness, and the ability to turn complex technology into something useful, trusted and human. Not one of those in isolation — all four, in the same person, on the same problem.
Judgment is the one that doesn't show up on a portfolio. It's knowing which problems are worth solving before you spend three months solving them, and having the nerve to say so when the answer is no.
Technical fluency doesn't mean writing production code (though increasingly, it can). It means understanding what's actually hard to build, what's cheap now that used to be expensive, and where an AI model genuinely changes what's possible versus where it just makes the wrong thing faster.
Commercial awareness is knowing that a beautiful flow nobody pays for isn't a win. Design decisions are business decisions wearing a different hat.
As production gets faster and cheaper, the value in design work doesn't disappear — it moves. It moves further upstream, into problem framing, decision-making and domain expertise: the work of deciding what's worth building before anyone opens a design tool. And it moves further downstream, into ownership, delivery and measurable outcomes: the work of staying accountable for whether the thing actually worked, long after the first version shipped.
The middle — the part where a designer hands off a polished flow and moves on to the next ticket — is exactly the part AI has gotten good at compressing. What's left on either side of that compression is where the real work, and the real value, now sits.
This is the work of turning "we should probably build something for this" into a specific, falsifiable bet — what's the actual problem, who has it, what would prove the idea is worth pursuing, and what would prove it isn't. It's judgment work, not production work, and it's exactly the part that gets skipped when a team is under pressure to ship something, anything, fast.
This is staying in the room after the design file is "done" — through the build, through launch, through the first weeks of real usage — and being willing to be measured against whether it worked. Not just whether it shipped.
If you're the one writing the brief, the title matters less than you'd think. What matters is whether the person you're evaluating can hold the whole arc — from an ambiguous problem to a shipped, adopted outcome — in one head, rather than handing pieces of it across a chain of specialists who never talk to each other. That's the profile clients keep describing to me, whatever they end up calling the role. It's also exactly where I've spent most of the last 20 years, and where the most interesting work is right now: startups and scale-ups building AI-enabled, complex, high-trust products, where the strongest people sit somewhere between deep craft, systems thinking, technical adjacency, and real product ownership.
Justin Roberts is the founder of Reloop Digital, a B2B SaaS consulting practice specialising in product strategy, UX design, and digital delivery. If you're trying to work out what to actually hire for, whatever the title ends up being, get in touch.