The nature of the job description stays virtually unchanged even though the job title does so. For example, one client is looking for a Principal Product Designer while another requests a Design Technologist, a Design Engineer, an AI Product Designer, or—more frequently—a 'product builder'. Although the titles are different, the fundamental expectation has become surprisingly consistent.
The Titles Keep Changing
If you look past the title, the nature of the brief is nearly always the same: you need to find someone who is able to work across product, technology, and business, who is at ease in dealing with ambiguity without having to wait for a specification to be perfectly defined, who thinks in terms of systems, not isolated screens, who collaborates directly with engineers rather than passing on files, and who can tell the difference between the places where AI creates real value and those where it only adds noise.
Most importantly, clients want someone who shows genuine, continuous concern for the quality of the material that finally reaches users.
It is a lengthy statement for a single individual and, increasingly, the only one that counts.
What Clients Are Actually Asking For
If you get rid of the job title, the majority of clients are seeking the same four attributes: judgment, technical proficiency, commercial awareness, and the ability to make complex technology useful, trustworthy, and human. They don't want these capabilities to exist separately; they want the same individual to apply all four to the same issue.
Judgment is seldom evident in a well-presented portfolio; rather, it lies in deciding which problems are worth addressing before investing months in solving them, and in having the confidence to say no when a piece of work will not lead to meaningful value.
Technical fluency doesn't necessarily involve writing production code, although it often does; it means understanding what is truly difficult to build, what has become easier or less expensive, and where AI expands possibilities rather than merely speeding up the wrong solution.
Commercial awareness means that a pleasant experience no one is willing to pay for should not be considered a success. Each design choice has an impact on adoption, retention, cost, risk, or growth, and design decisions are business decisions that are expressed via the product.
Human-centered translation means converting technical complexity into an experience people can understand, trust, and use with confidence. Even if the technology involved is advanced, the end result should not give that impression.
Why This Is Happening Now
As production grows quicker and costs less, the value of design doesn't vanish—it rather moves.
It takes the process upstream to the stage of problem framing, strategic decisions, and expertise in the domain—that is, deciding what is worth building before anyone opens a design tool—and it also takes it downstream to implementation, ownership, and tangible results: staying accountable for whether the product is a success after its first release.
It is at the middle stage—that is, the stage at which a designer produces a refined flow, hands it over to engineering, and then proceeds to the next task—that AI is saving time and labor. It is precisely in the work carried out on either side of this time and effort saving that designers can now generate the most value.
Upstream: Problem framing and decision-making
The upstream work turns the idea that "we should build something for this" into a specific, testable hypothesis by identifying the core problem, determining who it affects, and establishing what evidence would justify investing in a solution and what evidence would indicate we should halt efforts.
The work in question is based on judgment, not on production, and is the kind of work that teams most often fail to carry out when the pressure to ship quickly becomes more important than deciding what should be shipped.
Downstream: Ownership, delivery, and outcomes
Downstream work means staying engaged after the design file is considered complete; it involves working through implementation, supporting the launch, monitoring actual usage, and improving the experience based on evidence.
Success is no longer just about whether the product has shipped; it's about whether it solved the problem it was meant to solve and produced a significant result.
What This Means When You’re Hiring
When preparing the brief, the title matters less than you may think; what matters is that the candidate can trace the full progression from an unclear problem to a solution that has been implemented, accepted, and quantified, and that they take real ownership of it.
It doesn't mean a single person carries out all the tasks; it means they can connect the work across product, design, engineering, and business, rather than having separate sections pass work along through a series of specialists who rarely collaborate. This is the way clients consistently describe the role, no matter what name they give it.
That is also the place in which we have spent a large part of the last 20 years and where, in our opinion, some of the most interesting work is currently being done—namely, assisting startups and scale-ups in developing complex, AI-enabled, high-trust products. The best practitioners in these settings combine solid design skills, systems thinking, technical proficiency, and true product ownership.
Dworkz is a UI/UX design and development firm based in San Francisco, focused on data-driven B2B SaaS companies. If you are defining a role and need help identifying the capabilities that matter—whatever the final title—get in touch.
