What is a Forward Deployed Engineer?

What does a Forward Deployed Engineer do?

An FDE owns the whole path from a customer’s request to a working system the customer can run without them. The work spans seven stages:

1. Discovery. Turn an unclear, often contested request into a specific problem with agreed success measures.
2. Design. Choose the simplest architecture that fits the customer’s real systems, identity, network and data constraints.
3. Building. Write production-grade code, often AI or LLM components, and prove quality with evaluations the customer trusts.
4. Deployment. Ship into the customer’s production environment and keep it secure, observable and compliant.
5. Adoption. Make sure people actually use it: training, workflow changes and honest reporting of impact.
6. Handover. Leave the customer able to operate the solution on their own.
7. Feedback. Turn what was learned in the field into playbooks, reusable components and product feedback.

What skills does a Forward Deployed Engineer need?

The open FDE Competency Framework (draft v0.1) groups FDE skills into 7 industry-neutral domains:

1. Customer discovery and problem framing
2. Solution architecture and systems integration
3. AI/LLM application engineering and evaluation
4. Data engineering and data readiness
5. Deployment, operations, security and responsible AI
6. Stakeholder communication, adoption and change management
7. Delivery leadership and commercial judgment

What are the levels of a Forward Deployed Engineer?

The framework uses three proficiency levels, defined by observable behavior rather than years of experience:

• Associate: delivers well-defined parts of a deployment under guidance.
• Practitioner: owns a deployment end to end for one customer or workstream, working independently.
• Lead: owns several or high-stakes deployments, sets the approach for others and is trusted by customer executives.

How do you become a Forward Deployed Engineer?

There is no single entry path or required credential. Employers hire for a mix of engineering depth and customer judgment, and each defines the role differently today. A practical way to prepare is to work through the framework’s domains and build evidence for each one:

• Write tested, maintainable production code in at least one mainstream language.
• Integrate with real, messy systems: APIs, databases, files and legacy interfaces.
• Build and evaluate an AI or LLM application against real cases, with agreed acceptance thresholds.
• Practice discovery: turn a vague request into a problem statement with a baseline and a target.
• Explain technical trade-offs to executives and operators, including bad news.

The framework document (PDF) lists behavioral indicators for each competency at every level, which you can use as a self-assessment.

For a practical hiring approach, read how employers can assess FDE skills.

Is there a Forward Deployed Engineer certification?

Not yet. The FDE Competency Framework is a draft and nobody can be assessed or certified against it. FDE Council plans to validate it through a formal job task analysis first; any later credential will be governed separately and kept apart from training.