Forward-deployed engineer: the role, and when a fractional one fits

Embedded is the word that defines a forward-deployed engineer. The engineer works inside the customer’s systems and team instead of delivering from outside, and stays until the software runs in production. A fractional one does the same for a few days a week, which suits teams that need the skill without a full hire.

Written by Ben Friedman, fractional forward-deployed AI engineerPublished · 2 min read

Key takeaways

  • The role was popularised by Palantir and has spread across AI companies.
  • Its output is running software in the customer’s environment, not a recommendation.
  • Fractional fits when the work is real but does not fill a full-time seat.

How the role differs from its neighbours

Consultant
Studies the problem and advises. Someone else builds.
Solutions engineer
Shows how a vendor’s product could fit, before the sale.
Agency developer
Builds to a written specification, usually from outside your systems.
Forward-deployed engineer
Learns the process on site, builds inside your stack, and owns the result until it works with real data.

Why AI work suits the model

AI projects are short on specification. The rules for an exception are in somebody’s head, and the shape of the data is only clear once you open it. An engineer who sits in the team’s chat and tools hears the exception the day it happens and adjusts the build that week. A specification written up front would have missed it.

A fractional week, concretely

On my engagements the week is split: several days inside the client’s chat and ticketing tools, the rest elsewhere. One person at the client owns the process, and each week ends with a demo. I work through accounts you create. The stages and what each delivers are on the FDE page.

When to hire full-time instead

If you have a year of AI builds queued and a team to supervise an engineer, hire one. A fractional arrangement is for the stage before that: one or two builds that must work, no roadmap yet, and nobody in-house who has shipped an agent. It is also a way to learn what the full-time job description should say.

Frequently asked questions

Is a forward-deployed engineer the same as a contractor?
The contract may look alike. The difference is where the work happens and what counts as done: inside your systems, and done means running in production with someone trained to own it.
Does the engineer need access to production?
To what the build touches, yes, through accounts you control and can revoke. The trust page lists how access and data are handled.

Wondering whether your first AI build justifies an embedded engineer? Thirty minutes will settle it.

About the author

Ben Friedman runs Viter, a forward-deployed AI engineering service. He has spent over ten years running Atlassian and operations tooling, including as internal Jira lead at Aroundtown, and holds the ACP-610, ACP-620 and ACP-120 certifications. He builds JAMES, the AI Jira administrator.

Next in this topic · 4 of 5Anatomy of a change plan: what an agent shows you before it touches Jira The five things a plan has to contain before I let an agent change a production Jira site, with an example.Read next →