The short answer
A forward deployed engineer (FDE) builds and puts technical solutions into use with customers. The work usually combines software or data engineering with direct contact with the people who will use the solution. An FDE may investigate a customer problem, design an approach, write production code, deploy it in the customer’s environment, and carry the work through early operation.
The engineer works with customers to understand their problems, builds solutions for their environments, and brings what they learn back to product and engineering teams. The title does not describe one fixed job. Read the responsibilities, project stages, and customer relationship in each posting.
What the work can include
An FDE might:
- learn how a customer’s process, data, and systems work.
- turn that information into a technical design.
- connect APIs, databases, models, or internal services.
- write and test production code.
- deploy and debug the solution in the customer’s environment.
- explain design choices to customer engineers and other stakeholders.
- watch how the solution performs and fix problems after launch.
- turn repeated customer needs into reusable code or product requests.
Some roles also include technical discovery, evaluations, or proof-of-concept work before a customer commits to a solution. The same role may continue through production delivery. A pre-sales label alone does not tell you how much production work the role includes.
Three common shapes of FDE work
The boundaries overlap. These labels are useful when reading a job description, not as universal job titles.
Production engineering
The engineer ships a working system for a customer and remains responsible for important technical decisions during delivery and operation. A listed Google Partner Forward Deployed Engineer III posting asks the engineer to co-build agentic workflows, develop evaluation and observability systems, and turn recurring field patterns into reusable modules and product requests. The original Google careers posting names Python, cloud AI systems, customer launches, and technical discovery.
Implementation and data integration
The work may focus on moving data, connecting systems, configuring a platform, and building the application around it. A listed Databricks FDE posting describes end-to-end data, AI, and application solutions, production delivery, customer architecture, and deployment. It asks for software or data engineering experience and lists Python, Scala, JavaScript or TypeScript, cloud platforms, Spark, MLOps, and CI/CD. The original Databricks posting is the authority for its requirements and status.
Discovery, evaluation, and proof of concept
Some FDEs work with a customer to understand a problem, test whether a product can solve it, and build a small working version. If the project continues, the engineer may harden the design and ship it. Other roles stop closer to evaluation or hand the implementation to a delivery team. Check the posting for its production and operational responsibilities.
What is an AI FDE?
An AI FDE applies the same customer-facing delivery work to AI systems. The work can include model and prompt evaluation, retrieval and data pipelines, agent workflows, observability, security controls, and integration with customer systems. The engineer still needs to understand the customer’s goal, ship a dependable solution, and explain its limits.
“AI FDE” is not a standardized level or certification. A posting may use the title for production software work, data and model integration, an evaluation role, or a broader field engineering role. Read the technologies and responsibilities together. Look for who owns deployment, what reaches production, and who responds when the system fails.
How to decide whether a posting is FDE work
Ask these questions:
- Who uses or receives the work: external customers, internal teams, or both?
- Does the engineer write production code, configure integrations, build prototypes, or mainly present a product?
- Which project stages are included: evaluation, proof of concept, implementation, and ongoing operations?
- Does the engineer work inside a customer environment and own technical delivery there?
- What happens to repeated field lessons? Does the engineer feed them into reusable systems or product decisions?
The job title is one clue. The answers in the job description tell you what the job asks you to do. For comparisons with nearby roles, read FDE vs software engineer and FDE vs solutions engineer.