A forward deployed engineer (FDE) is an engineer who works inside a customer’s organization to make a product work in that customer’s real environment: configuring it, connecting it to the systems around it, building what is missing, and staying until people use it.
The role began at Palantir, spread through AI companies such as OpenAI and Anthropic, and is now one of the fastest-growing job titles in technology. This guide explains what “forward deployed” means, what the job involves, how it compares with software engineers, solutions engineers and consultants, and what the same model looks like inside a corporate legal department.
What does “forward deployed” mean?
Forward deployed means working where the customer works: on the customer’s systems, with the customer’s data, alongside the people who will use the product. The phrase comes from military usage, where forward deployed forces are stationed near the area of operations, away from their home base.
Palantir made the title famous. In its own description of the two biggest engineering roles at the company, Palantir explains that its forward deployed software engineers, internally called “Deltas”, deploy its platforms to customers and are responsible for technical outcomes there. Product engineers focus on “one capability, many customers”; a Delta focuses on “one customer, many capabilities” (Palantir, Dev versus Delta).
What does a forward deployed engineer do?
A forward deployed engineer configures a product to one customer’s workflows, integrates it with that customer’s systems, builds what is missing and drives adoption until people use it. They own the distance between a product that works in a demo and a product that works in one particular organization. Day to day, that means:
- Learning the workflows and data. How the work actually runs, which systems hold which records, and where the data is incomplete.
- Configuring the product around those workflows, approvals and rules.
- Integrating it with the systems it has to live with: finance, HR, identity, document storage.
- Building the missing pieces: scripts, workflows, reports, custom applications and, increasingly, AI agents.
- Driving adoption: training, change management and support through go-live.
- Feeding back what they learn, so the product and the next deployment improve.
How is a forward deployed engineer different from a software engineer, solutions engineer or consultant?
A forward deployed engineer is tasked with building and running a solution with the customer, inside the customer’s environment, until it is in use. Software engineers build the product, solutions engineers support the sale, and consultants can be engaged for many roles, from advising to delivering the work. The titles overlap, so the clearest way to separate them is by where the person works and when their job is done.
| Role | Where they work | What they own | When the work is done |
|---|---|---|---|
| Software engineer | Inside the product team | The product, for every customer | Ongoing release cycle |
| Solutions engineer | Pre-sales, with the account team | Demos and technical fit | At signature |
| Vendor professional services | On the vendor’s own product | Configuration to a statement of work | At go-live |
| Consultant | Alongside the client, in the role the engagement calls for | Advice, analysis and recommendations, and often design, implementation and ongoing delivery | When the engagement’s scope is delivered |
| Forward deployed engineer | Inside the customer’s environment | The outcome at that customer | When the product is in use |
The roles also combine. A consulting engagement can include advisors, program managers and forward deployed engineers, each doing the part of the work they are best placed to do.
Building the legal operations function from scratch?
Assessment, roadmap, and delivery for the operational side of the department: spend, technology, process, vendors, and the data that proves what legal delivers. Advice from operators who ran the function.
See Legal Ops ConsultingWhy are AI companies hiring forward deployed engineers?
AI companies hire forward deployed engineers because AI products create value only once they are connected to a customer’s own data and workflows. Someone has to connect the model to that data, shape the workflow around it and earn the users’ trust. Andreessen Horowitz described this in 2025, noting that even model providers such as OpenAI and Anthropic were hiring forward deployed engineers to win enterprise customers (a16z, Trading Margin for Moat).
Demand has followed. Fortune, citing Lightcast data, reported that job postings for forward deployed engineers rose more than 1,000% between January and August 2026, and more than 4,600% compared with 2023 (Fortune).
The model has reached legal work too. As of October 15, 2026, OpenAI is recruiting a Forward Deployed Engineer for legal to embed with law firms and legal teams, choose the first use case and prove measurable value.
What is a forward deployed engineer in a legal department?
In a legal department, a forward deployed engineer is a practitioner who works inside the department to configure, integrate and drive adoption of its ELM, CLM, document management and AI platforms. Corporate legal departments have lived with the problem this role solves for years: software bought, configured and only partly used.
- A Gartner survey of 140 legal functions found that most had failed to capture the full benefits of their technology investments, and just 23% scored highly for digital readiness.
- Gartner had earlier predicted that by 2025 corporate legal departments would capture only 30% of the potential benefit of their CLM investments.
- The Thomson Reuters Institute found that only 20% of legal professionals were measuring the return on their generative AI investment.
The gap sits between buying a platform and running the work on it. A forward deployed engineer for a legal department closes it by combining two kinds of knowledge: how legal work runs (matters, outside counsel invoices, contracts, documents, approvals) and how the platform behaves once it is configured. In many legal teams the same person carries the title legal engineer or legal technologist; what defines the forward deployed version is that they work inside the department and stay accountable until the system is used.
What does a forward deployed engineer do on legal platforms?
On legal platforms, a forward deployed engineer configures the system around the department’s workflows, connects it to the systems around it and stays through adoption. The specifics depend on the platform:
- Enterprise legal management and eBilling. Matter types, billing guidelines and invoice routing configured to the department; accounts payable, HR and single sign-on integrated; LSR and intake built on the platform. The ELM implementation guide sets out the phases.
- Contract lifecycle management. Templates, approval chains and clause libraries built around how legal, procurement and sales work, with the contract library migrated and searchable.
- Document management. Matter-centric workspaces, migration off shared drives and legacy systems, and governed access to AI features.
- Legal AI. Frontier models, use-case tools such as contract extraction, and the AI already built into the ELM, CLM and document platforms, tested on the department’s own data with success criteria agreed up front. Our legal AI consulting page covers the pilot model.
- After go-live. Administration, reporting and continuous improvement, which is where managed legal operations picks up.
When does a legal department need a forward deployed engineer?
A legal department needs a forward deployed engineer when its platforms are bought but only partly used, or when AI pilots are not reaching production. The signals are usually operational:
- An implementation has stalled, or the system is live and the team still works around it.
- Integrations were scoped out of phase one and never built.
- A long-serving administrator is leaving and the configuration lives in their head.
- AI pilots produced demos that never reached production.
- The vendor configured the product, and nobody designed the process around it.
A small team on a single out-of-the-box tool may never need one. A department running several platforms, or rolling out AI on top of them, usually does.
Bottom Line
A forward deployed engineer is defined by where the work happens and what they answer for: inside the customer’s environment, accountable for the product being used. AI companies adopted the model because their products only create value once they are connected to real data and real workflows.
Need the function run, not just advised on?
Swiftwater embeds senior practitioners directly into legal operations, handling bill review, matter management, and program delivery on your behalf.
See Managed ServicesLegal departments face the same gap with ELM, CLM, document management and AI platforms, and the research shows how often the value goes uncaptured. The question for a General Counsel is who will sit with the team, on the platform, until the work runs on it.
Swiftwater’s practitioners work this way across ELM, CLM, Docusign, document management, IP and legal AI platforms, and our forward deployed engineers stay with your team from configuration through adoption.
Frequently Asked Questions
What is a forward deployed engineer?
A forward deployed engineer is an engineer who works inside a customer’s organization to make a product work in that customer’s environment. They configure the product, integrate it with surrounding systems, build what is missing and stay until people use it. Palantir made the role well known, and AI companies such as OpenAI and Anthropic now hire for it.
What does forward deployed mean?
Forward deployed comes from military usage, where forces are stationed near the area of operations, away from their home base. In software it means the engineer works where the customer works, on the customer’s systems and data, alongside the people who will use the product.
What is the difference between a forward deployed engineer and a solutions engineer?
A solutions engineer works in pre-sales, showing how a product fits a prospect’s needs, and their job is largely done at signature. A forward deployed engineer works after the sale, inside the customer’s environment, and their job is done when the product is in use.
How is a forward deployed engineer different from a consultant?
A consultant can be hired for different roles: advising, delivering analysis and recommendations, and going further into design, implementation and running the work. A forward deployed engineer is tasked specifically with building and running a solution with the customer, on the customer’s own systems, through adoption. Many consulting engagements include forward deployed engineers.
Do legal departments use forward deployed engineers?
Yes, though the title is new to legal. Corporate legal departments use practitioners who work inside the department to configure, integrate and adopt ELM, CLM, document management and AI platforms, and AI companies are now hiring forward deployed engineers specifically for legal work.
