There’s a new job title going around: forward deployed designer.
It comes from the forward deployed engineer, the engineer who works inside a customer’s team instead of building from headquarters. Lenny Rachitsky’s late-2026 job market report counts about 1,500 open forward deployed engineer roles, up 4.6 times in a year. Design is following. Gamma and Tailor are now hiring forward deployed designers by name.
I already work this way, without the title. Here’s what I think the role actually is, and how to tell whether your company needs one.
What is a forward deployed designer?
A forward deployed designer embeds with the team that has the problem, works inside its real workflow instead of a design file, and ships fixes fast, often in code. The title is borrowed from the forward deployed engineer. The difference from a product designer isn’t skill. It’s where you sit, and what you’re judged on: whether the team actually uses the work.
The clearest definition I’ve seen is David Hoang’s, as AI Goodies summarises it: “someone who embeds with a team facing an ambiguous problem.” Jakob Nielsen is blunter: “It is not simply a traditional UX designer given a trendy new title.”
He’s right. The title is new. The behaviour isn’t. It’s what good design partners have always done when they’re allowed to: get close enough to the work to see where it breaks.
How is it different from how design usually works?
Usually, design happens in a file and then gets handed over. Someone else builds it, and the designer finds out later what survived. A forward deployed designer skips the handoff. They sit where the work happens, learn from the real workflow, hand over working prototypes or front-end code, and judge the work by whether people use it.
| The usual way | Forward deployed | |
|---|---|---|
| Where the designer works | Design files, then a handoff | Inside the team’s Slack, meetings and codebase |
| What they learn from | Briefs and research sessions | The real workflow, as it happens |
| What they hand over | Specs for someone else to build | Working prototypes, and front-end code where it helps |
| What they’re judged on | Whether the design got approved | Whether the team uses it |
Why is this role showing up now?
Because teams got smaller and faster. In the same report, demand for front-end and mobile engineers nearly halved in a year, while designer job posts now list Claude second only to Figma, with Cursor ahead of CSS. When fewer people ship more, a designer who waits for a handoff waits a long time. The work moves to whoever sits inside the team and can take a screen from idea to shipped.
That’s why the forward deployed designer and the design engineer are converging. One is defined by where you sit, the other by what you ship. More and more, it’s the same person.
Does your company need a forward deployed designer?
Only once there’s a real workflow to embed in. Before launch, you need a product designer. After launch, you need a forward deployed one when design keeps getting lost between the file and what ships, or when every new customer or team needs the product shaped around how they actually work.
- Is anyone using the product every week? If not, there’s nothing to embed in yet. Hire a product designer.
- Does design get lost on the way to production? If what ships keeps looking like a cheaper version of what was designed, the handoff is the problem.
- Does each new customer or team need the product shaped around them? If yes, that’s the job forward deployed designers exist for.
If you answered yes to two or three, match the route to how long the job lasts. If every new customer needs a designer on the ground, hire one full time. For one deployment, contract one. If you need product, brand and the front end from one senior person inside your team, an embedded partner fits. I’ve compared four ways to get one.
What does it look like in practice?
For me, it means joining your Slack, working to your weekly rhythm and plugging into your developers and product managers, so the work lands in production instead of staying in Figma. Where it helps, I ship it myself: front-end code in your own codebase, prototypes in code, and marketing sites, with your engineers reviewing anything before it reaches production.
There’s no account manager and no translation layer. The person who sees the problem is the person who fixes it.
I work as an embedded design partner and design engineer for a small number of companies at a time. If design on your product keeps getting lost between the file and what ships, email me or start a project.
