ai goodies ✨
Posts
the Forward Deployed Designer / a new role is emerging

the Forward Deployed Designer / a new role is emerging

designers who embed with teams, go to the problem, and leave behind working software instead of decks / this might be the most exciting new design role since "design engineer."

Ioana from AI Goodies
May 21, 2026

✋🏼 Before we get started, I need your help. AI Goodies is still a small, independent enterprise, and it needs your help to grow 🌱

so if you enjoy this read + my vibe, please share the article on your platform of choice, send it to friends, recommend others to subscribe ✔️

yay, thanks + let's get to it.

There's a new role showing up in job boards and design conversations and I think it deserves our attention 🥁 it's called the Forward Deployed Designer.

If you haven't heard the term / it comes from a concept Palantir pioneered in the early 2010s: the Forward Deployed Engineer. These weren't your classic engineer sitting at HQ building features on a roadmap; they were engineers embedded directly at client companies — sitting with analysts, operators, decision-makers — to discover the problem and build the solution in the same motion.

The idea was simple: when you collapse the distance between the person who understands the problem and the person who can build the solution, everything moves faster. The feedback loop tightens. The game of telephone between sales, product, and engineering disappears. You stop building to spec and start building to learn.

That model exploded. Databricks, Scale AI, OpenAI, Anthropic, Salesforce (who committed to 1,000 FDEs), Ramp, Rippling, Intercom > they all adopted variations.

Job postings for forward deployed engineers grew over 800% between January and September 2025. Average total comp for an FDE is now around $238K, with staff-level roles clearing $630K+.

So here's the question David Hoang asked in a recent piece that really stuck with me: why hasn't design had its version of this?

the answer used to be practical / now it's not

For most of design's history, you could embed a designer at a customer site, but they'd still need an engineer to build anything. A designer could observe workflows, sketch solutions, present recommendations, BUT the output was a deck, not working software. Useful / but not the same as what a forward deployed engineer delivers.

Consulting and agency models tried to bridge this gap. Design sprints became the popular format: a week-long workshop with a rigid agenda > map on Monday, sketch on Tuesday, decide on Wednesday, prototype on Thursday, test on Friday. The intent was right: compress the cycle + get to a testable idea fast.

But the format is still a workshop: it’s bounded, facilitated, and disconnected from real implementation. The prototype you build on Thursday is a clickable mockup, not software.

And this is where AI changes the equation. Because now, with tools like Claude Code, Cursor, Replit, Lovable, v0, a designer can go from observing a workflow to building a functional prototype in the same day; not a Figma mockup, a working thing.

And this doesn’t mean designers are replacing engineers. But now designers are able to do the first 80% of a solution independently: research the problem, design the approach, build a functional prototype, validate it with real users. The last 20% (production hardening, systems integration, scale) still needs engineering. But by the time engineers engage, the problem is well-defined and de-risked. That's enormously valuable.

And that's what makes the Forward Deployed Designer possible now in a way it wasn't before.

so what does this role actually look like?

David Hoang defines it well: the Forward Deployed Designer is someone who embeds with a team facing an ambiguous problem, spends time in the field observing real workflows, and rapidly prototypes solutions using AI-assisted development. They leave behind not just a solution, but clarity: a well-articulated problem, a tested approach, and artifacts the team can build on. They compress the discover-design-validate loop from months to weeks.

And here's the key distinction: a consultant optimizes for the engagement. A forward deployed designer optimizes for the problem. The output isn't a 60-page deck or a set of recommendations > it's working software and validated insights. You have skin in the game because you're embedded with the team, not flying in for a workshop.

It's also different from a staff or principal designer at a company. Forward deployed designers are temporary and targeted. They don't own a product area long-term. They bring fresh eyes and cross-pollinated patterns from other domains. They're scoped to the hardest, most ambiguous problems, the ones where you don't even know what to build yet.

this is already happening

It's not just a concept. Companies are already hiring for this.

Gamma (the AI presentation company that just crossed $100M ARR) has an open Forward Deployed Designer role right now. The JD describes someone who partners directly with B2B customers to translate brand identities and templates into the product, leads hands-on education sessions, creates "aha moments," and becomes the bridge between customer needs and product development. $100K–$140K plus equity.

Blitzy (an autonomous software development platform) introduced the role specifically because their AI platform accelerated engineering so much (they claim 5x velocity) that design became the bottleneck. Their Forward Deployed Designer works on-site with customers 3 days per week, creating production-ready designs, prototyping new workflows, and participating in sprint planning.

ImagineArt is hiring a Forward Deployed Creative > a variation where someone embeds with enterprise clients to help them integrate AI-powered design into their workflows.

And there's now a dedicated Forward Deployed Engineer Job Board that has started listing design-adjacent roles. 😳

The concept was first explored by Nathan Lui in a 2021 Medium piece where he proposed embedding designers within customer success teams, spending 25% of their time on CS responsibilities to get closer to real user problems. His argument was that design roles had been operating increasingly far from users, and the Forward Deployed Designer would change that by bringing design closer to the people using the product every day.

What's different now is that AI gave us the missing piece. Nathan's original vision required a designer to still hand off to engineering. Today's version can prototype and validate independently.

the small team model

Here's where it gets really interesting, especially for companies thinking about how to structure this.

David Hoang describes a squad: a forward deployed engineer, a forward deployed designer, and a researcher. Three people. That's it. They operate like a startup-within-the-company, deployed against a specific, ambiguous problem.

Product discovery, design, and research have always been intertwined but organizationally separated. This team collapses those silos. The researcher identifies the real problem. The designer shapes the solution and iterates rapidly. The engineer handles systems integration and technical feasibility. All in the same room, same week.

And AI amplifies each person. The designer can prototype at engineering speed. The engineer can explore more solutions faster. The researcher can synthesize data that used to take weeks. A three-person team with AI tools in 2026 can cover the ground that used to require a ten-person cross-functional team.

The rotation model matters too. These should be temporary deployments (four to eight weeks), not permanent structures. After the engagement, the squad disbands and members rotate to new problems. This prevents the team from becoming just another product team, and it creates a career path that's actually exciting: instead of being stuck in support roles on feature teams, designers operate at the frontier of the company's hardest questions. ❤️‍🔥

why this matters for all of us

OK so I want to zoom out for a second because I think this is bigger than one new job title.

What the Forward Deployed Designer represents is a fundamental shift in where design value lives. For years, we've been advocating for designers to have a seat at the table. To be included in strategy. To be consulted earlier. And all of that is important.

But the Forward Deployed Designer doesn't ask for a seat at the table. They go to where the table is: they embed, they observe, they build, they validate. And they leave behind something real / not a presentation about what should be built, but a working prototype that's already been tested.

This connects directly to what I've been writing about in recent issues / the shift from making to deciding, the design engineer as canonical role, designers becoming builders. The Forward Deployed Designer is another expression of the same underlying change: designers who have technical leverage, who can close the gap between insight and artifact, and who are measured by outcomes, not deliverables.

And tbh, when I think about what I do with my consulting work (my Futurism Sprints, my Shockproof workshop) it's not that far from this model. You embed with a team, go to the problem, compress the discovery-to-prototype loop, and leave behind clarity and direction. The difference is that now, with AI, you can also leave behind working software.

is this a role for you?

If you're a designer who gets restless on long product roadmaps, who loves ambiguity more than process, who wants to build not just design, and who gets energy from new problems rather than maintaining existing ones > this might be your role.

If you're a consultant or agency designer who's tired of delivering decks that sit in someone's Drive > this might be the model that replaces what you do.

If you're a design leader wondering how to deploy your senior designers against the hardest problems without turning them into permanent feature-team appendages > this is a structure worth exploring.

And if you're in none of these categories but you're curious about where the design profession is heading > add "forward deployed designer" to your vocabulary. I think we're going to hear it a lot more.

🔥 let's collaborate 🤝 get featured in my newsletter

We have the coolest audience that you can get yourself in front of. Reach out at [email protected] if interested 💋

Send the AI Goodies newsletter to a friend who's either excited by AI, or worried, or both 😅

Subscribe to AI Goodies ✨

✨ for more goodies, follow me on:

UX Goodies on Instagram

Ioana Teleanu on Linkedin

thanks + AI & Design Love,

hugs hugs,

Ioana 🪩

/ soft machines