Expert PerspectivesAI Leadership
The team you need is changing. Meet the forward-deployed engineer.
Software hiring is shifting from narrow functional silos to engineers who sit inside live business workflows and stay through adoption. Here is what the data shows and how leaders should respond.
Edited with AI assistance. Drafted by Justin Rohatinsky and refined with team feedback; market statistics verified and formatted with AI assistance.

Shared strength.
The perspective
Examine your capabilities and where work gets stuck before rewriting your org chart. Whether client-facing or embedded with internal operations, forward-deployed engineers close the gap between promising technology and measurable business results.
The team you need is changing
Software teams are changing, and companies have some real decisions to make about how they hire, organize, and develop their people.
The hiring trends across the industry tell a consistent story: product roles are growing faster than traditional engineering, overall engineering demand has leveled off, and standalone openings in design, front-end, and mobile development have softened. Meanwhile, demand for forward-deployed engineers has climbed sharply.
According to labor-market data from Lightcast, US job postings for forward-deployed engineers jumped from roughly 200 in 2024 to about 1,200 in 2025, then crossed 5,200 postings in the first seven months of 2026 alone. Separate talent tracking from Draup shows FDE demand up 380% between Q1 2024 and Q1 2026, making it the fastest-growing technical role in the market while demand for traditional solutions engineers fell 14%. And across recruiting platforms, Bloomberry and Paraform recorded a 1,165% year-over-year spike in FDE job listings.
For business leaders, this raises a practical question: what combination of skills will help our teams turn technology into measurable business results?
Roles are consolidating around outcomes, not handoffs
Before looking at any new title, it helps to name the deeper shift underneath it. When we ask our Client Advisory Board what they are seeing inside their own organizations, the answer is clear: roles are expanding and consolidating.
Product managers are doing more validation before handing requirements off. Designers are owning more of the workflow and front-end execution. Engineers are expected to understand the business problem directly rather than waiting for a ticket in a back corner. At the same time, S&P Global Market Intelligence research found that the share of companies abandoning most of their AI initiatives before production jumped from 17% to 42% in a single year.
That is the real problem behind the hiring numbers. Building a prototype or buying a software license is rarely the bottleneck anymore. Turning technology into reliable daily adoption inside messy, real-world operations is.
Why forward-deployed engineers are gaining ground
The forward-deployed engineer model was pioneered by Palantir and has since been adopted at scale by frontier labs and enterprise platforms including OpenAI, Anthropic, Amazon, and Salesforce. Today, roughly 65% of active FDE hiring comes from enterprise companies rather than AI research labs alone.
Two shifts explain why the role is taking off:
- Deciding what to build matters more. Product management openings have grown faster than pure coding roles because companies are putting heavier emphasis on deciding what to build and why.
- Deployment inside real operations is where value gets won or lost. Traditional software engineers often sit far from the customer, and traditional sales engineers stop at demos. A forward-deployed engineer bridges both: an engineer who sits directly with an operations team, understands the workflow, connects the necessary systems, and adjusts the solution based on what happens in practice.
In practice, we see forward-deployed engineers operating in two ways:
- Client-facing FDEs, who embed with an external customer’s operations team to integrate software or AI into live legacy systems and stay through adoption.
- Internal business-facing FDEs, where the company’s own operating units are the client—meeting directly with finance, service, or commercial teams to assess workflows, data, and infrastructure so AI actually works in people’s day jobs.
Data from Draup backs up how hands-on the role is: FDEs spend an average of 47% of their workweek embedded with operational users, and 64% of their effort goes toward deploying and customizing existing systems rather than greenfield builds.
Build teams around customer problems
A practical response to these hiring trends is to organize teams around customer and operational problems and give them ownership for results all the way through implementation and adoption.
- Product leaders establish clear priorities and define what measurable success looks like.
- Engineers stay close to the people actually using what they build.
- Designers help teams untangle workflows and make tools genuinely usable, even when dedicated standalone design hiring slows.
- Forward-deployed engineers connect those disciplines by bringing deep technical execution directly into the live operating environment.
The title may be new to some organizations, but the underlying need is familiar. Someone has to make sure the software works where the business needs it.
Someone has to make sure the software works where the business needs it.
What this looks like in practice
That approach can take several practical forms depending on where a business feels friction most:
In customer service: A company introducing an AI tool for support might pair a product manager with a forward-deployed engineer and a designer to identify the highest-volume recurring tasks, connect internal knowledge sources cleanly, and test the workflow side by side with support agents. Success is not launching a chatbot; success means agents resolving issues faster and customers getting better, more accurate answers.
On the commercial side: A forward-deployed engineer might embed directly with sales and marketing teams to automate account research, tighten lead routing across the CRM, and help reps follow up more effectively without manual copy-pasting.
Both examples combine technical execution with a grounded understanding of the people, data, and processes a technology needs to support.
Start with the gaps. Measure the results.
My view is that companies should use these shifts as a reason to examine their capabilities before rewriting their org chart.
Start by asking where work gets stuck and what prevents a good idea from becoming a useful result. From there, develop your existing people, hire for the gaps you can clearly identify, and bring in outside expertise where it accelerates the team. (If you want a structured baseline first, our AI Readiness Assessment maps leadership, workflows, data, guardrails, and adoption in one view.)
At SolutionStream, I believe we need to hold ourselves to that same standard. Whether through embedded AI implementation or specialized technical talent, if we adopt a new role, tool, or way of working, we should be able to show how it improves delivery, adoption, or business performance. The proof should be in what the team accomplishes.
Examine your capabilities before rewriting your org chart. Start by asking where work gets stuck and what prevents a good idea from becoming a useful result.
Sources
- Lightcast — Q: What is a Forward Deployed Engineer? A: The fastest growing AI job
- Draup — Forward Deployed Engineer Demand Is Up 380%
- Paraform — How to Hire a Forward Deployed Engineer in 2026 (including Bloomberry & S&P Global data)
- Fortune — Why Forward-Deployed Engineers Are Silicon Valley’s Fastest-Growing Six-Figure Job (Sep 2026)
- Forbes — AI Giants Bet Billions on the Most Expensive Job in Enterprise (May 2026)

Behind the perspective
Justin Rohatinsky
Chief Revenue Officer
Justin Rohatinsky is SolutionStream’s Chief Revenue Officer. His role brings the client’s goals, the engagement model, and the team’s capabilities into the same conversation.
Connect with Justin Rohatinsky Read Justin Rohatinsky’s profileThe Article CompanionAnswers from this article only
Good reading.
Better questions.
Explore this perspective. Find a useful passage. Take the next step.
What would you like to explore? Start with a question below, or ask about your team.
The article stays the source. This companion cites approved content and makes room for human judgment.
Let’s talk 