What is a forward deployed engineer?
A forward deployed engineer is a senior engineer who works inside your team and owns one problem from the first conversation to a system running in production. What the role does, why the title grew, how it differs from a consultant or a contractor, and what you should receive by day 90.
A forward deployed engineer is a senior engineer who works inside your team, in your channels and your repository, and owns one problem from the first conversation to a system running in production. The work starts in your operation, not in a ticket queue: the engineer learns how the work runs, finds where AI brings a measurable result, writes the specification with your people, and builds it. At yaab, that can be AI in what you sell, in how you operate, or in how you build.
What the role looks like in a week
The first survey of the role covered 1,500 forward deployed engineers and equivalent titles at 154 companies. The median engineer spends 47% of the week with the customer, 31% writing or reviewing code and 22% on internal coordination. Only 6% say they mostly build new product. The job is customer discovery with the right to ship code. Our note on the survey has the full numbers.
Why the title grew so fast
US job postings with the title went from about 200 in 2024 to about 1,200 in 2025, and more than 5,200 appeared in the first seven months of 2026. Three of the five most requested skills differ from a software engineer posting: AI and workflow management are in, agile methodology and software development are out. Our note on the postings has the breakdown.
How it differs from a consultant, a contractor or a platform
A consultant leaves a recommendation. A contractor ships the tickets you write. A platform gives you a tool and leaves the fit to you. A forward deployed engineer takes one problem end to end: finds it, specifies it, builds it, runs it in production, and hands your team a documented, tested system. Our checklist helps decide which of the four should take each problem.
What you should receive, and when
Judge the engagement by what it delivers, not by the hours. By day 30, a specification and no production code. By day 60, the hardest part working on real data. By day 90, your own person running it. Anything else is drift. The first 90 days, step by step.
What stays with you: the system running in production, the specification and the tests in your CI, the code with its history, and the IP. An engineer on your team, or ours, approves every change before it is merged.
Forward deployed engineers at yaab and at Viaro
yaab and Viaro Networks are part of the same group. At yaab, the forward deployed engineer works in a pod that owns one problem and delivers the system running. At Viaro, you add a forward deployed engineer to your team, under your lead, to put AI to work in your codebase and leave your developers faster. Viaro's guide to the role covers that side.
Frequently asked questions
What is a forward deployed engineer in one sentence?
A senior engineer who works inside your team and owns one problem from the first conversation to a system running in production.
Does a forward deployed engineer write code?
Yes. In the first survey of the role, 31% of the week goes to writing or reviewing code. Our forward deployed engineers direct the AI that writes most of it, review every change, and know when to reject what it produced.
How does an engagement with yaab start?
With a 45-minute working session and a discovery week inside your team. Then a pilot: three specifications become pull requests your team approves in weeks 2 to 4, or one agent runs on a real queue in weeks 2 to 7. After that it runs month to month, and you decide the next problem or whether to stop.