There’s a job title appearing in design listings that you might be seeing for the first time: Forward-Deployed Designer.
The odd-sounding title doesn’t go out of its way to explain what the job actually involves.
The title borrows from Palantir’s Forward Deployed Software Engineer role, where engineers embed with customers to configure and adapt software to their needs.
The basic idea is similar: you work directly with a software company’s customers, helping them put its product to work. You understand how they work, design around their needs, and help deliver the solution.
But the designer roles themselves vary considerably. Some companies want forward-deployed designers to design and ship software alongside engineers. Others want them to help customers use what’s already available.
Same title, different jobs
Across the listings I looked at, at least two versions of the role emerge. Tailor and Norm AI use the title for product designers who help define and ship software for customer deployments. At Gamma, the work is closer to customer adoption and enablement: translating customers’ brands and templates into Gamma content, leading hands-on education sessions, and bringing what the designer learns back to the product team.
At Tailor, which provides a platform for building business software, the designer leads design for customer implementations. They work with customers to understand operations, roles, and workflows, then partner with engineers and product managers to deliver the experience.
The assignment also extends beyond that customer. The designer identifies recurring needs and brings them into Tailor’s design system, shared components, and product roadmap. A solution developed for one implementation should improve future implementations.
Norm AI describes a similar role in legal software. Its designer joins client and partner scoping conversations, turns requirements into workflows and prototypes, and works alongside forward-deployed engineers through implementation and QA. The listing explicitly asks the designer to recognize when a client-specific solution should become a reusable product or component.
At Gamma, the emphasis is different. Its hiring announcement describes translating customers’ brand identities and templates into functional content, leading hands-on education sessions, and bridging customer needs and product development. That’s closer to helping customers adopt an existing product and get more value from it.
These roles share direct customer contact, but what you actually do differs. You could design a new workflow, create branded templates, or teach a team how to use the product.
Isn’t this what designers already do?
If you’ve worked in consulting, service design, or enterprise software, much of this will sound familiar. Working inside a client’s organization, understanding their processes, and helping a team deliver a solution have long been part of those jobs.
Even the title predates the current AI boom. In 2021, Nathan Lui published The Case for the Forward-Deployed Designer, proposing a designer embedded partly in Customer Success. The idea was to give designers regular contact with user problems through support, onboarding, and account work, and the opportunity to design improvements in response.
Ron Bronson also describes using this approach at 18F for years without calling it forward-deployed design. His account emphasizes multidisciplinary skills and the leadership support needed to make customer-facing delivery work.
And I worked this way years ago, designing custom front-end trading applications for major banks. We practically lived in our clients’ offices, and I spent time on trading floors seeing how the software fit into the reality of their work. It was wild, and it was one of the best ways to understand what people actually needed, especially in a domain as complex as finance.
That kind of access is a gift. It’s the sort of access many designers spend years asking for. The longstanding problem isn’t that designers don’t value customer contact; it’s that companies don’t always provide the time, access, and support to make it part of the work.
So the title doesn’t establish a new design discipline. In roles like Tailor’s and Norm’s, it makes customer implementation an explicit responsibility. You’re helping a particular organization use the software, while identifying what that work should contribute to the wider product.
Do you need to code?
“Forward-deployed” doesn’t establish a consistent technical requirement.
Norm AI mentions prototyping in code or with AI-assisted tools when that helps the team learn faster. Scale AI’s related public-sector role, currently titled Staff Product Designer, goes further, explicitly asking designers to work in code alongside engineers to build and refine the shipped experience.
That’s where the role can overlap with design engineering. A role might combine customer-facing design with technical implementation, but you need to check what “building” means: an interactive prototype, a coded proof of concept, or production software.
What to look for in a listing
The title offers a general direction, but the responsibilities reveal whether the role fits your skills and interests.
Look for answers to four questions:
- What will I produce? Product experiences, custom interfaces, templates, training, or a combination?
- Who will I work with? Customers and a dedicated engineering team, or primarily Sales and Customer Success?
- What technical work is expected? Design specifications, coded prototypes, or production contributions?
- How does customer work improve the product? Is there a clear responsibility for turning recurring needs into shared capabilities?
You don’t need to adopt the title to recognize relevant experience in your own work. If you’ve helped clients define problems, designed complex workflows, and worked with engineers through delivery, you may already have much of what these companies are seeking.
What the title tells you reliably is that working directly with customers is part of the job. It tells you far less about what you’ll design, how much authority you’ll have, or whether you’ll be expected to code. For that, you still have to read the listing.
