Discover the right enterprise problem, engineer the right AI solution, deploy it safely and make sure it creates value in real work.
Why the role exists
Access to capable models does not automatically produce a useful enterprise system. Production AI must work with real data, permissions, APIs, workflows, cloud environments, security controls, service levels and people. A prototype can look impressive while still lacking evaluation, rollback, monitoring, adoption or a defensible business case.
Current role descriptions show the pattern clearly. OpenAI describes FDE ownership from discovery and technical scoping through build and production rollout, measured through adoption and workflow impact. AWS describes embedded engineers co-developing production agentic systems with customer teams. These examples establish a market pattern; they do not mean every employer defines the title identically.
OpenAI FDE careers · AWS Forward Deployed Engineering
What does an FDE own?
| Responsibility | Practical question | Typical evidence |
|---|---|---|
| Discover | What problem is important enough to solve? | Stakeholder map, workflow, KPI baseline |
| Qualify | Is AI valuable, feasible and responsible here? | Opportunity scorecard, risk register |
| Design | What workflow and architecture govern the solution? | Target process, architecture, evaluation plan |
| Prototype | Do the highest-risk assumptions hold? | Working slice, golden dataset, baseline |
| Build | Is the system secure, integrated and maintainable? | Tested code, pipelines, connectors |
| Deploy | Can release be observed and reversed safely? | UAT, release checklist, rollback, runbook |
| Adopt | Are people using it in real work? | Usage signals, enablement, feedback |
| Optimize | Are quality, reliability, cost and value improving? | Traces, scorecards, KPI review |
Explore the complete Enterprise AI Deployment Lifecycle →
Is FDE a coding role?
Yes. Credible FDE roles commonly require production-grade engineering. The amount of coding changes with seniority and delivery stage, but the role should not be treated as no-code consulting. An FDE must be able to inspect technical evidence, challenge assumptions and contribute hands-on when delivery depends on it.
The capability model
Find root problems, establish baselines and define success.
Build secure, tested and maintainable production services.
Engineer governed retrieval, agents and evaluation.
Connect identity, APIs, cloud, observability and recovery.
Apply least privilege, threat modelling and oversight.
Run UAT, workflow change, feedback and value review.
Use the FDE Skills and Portfolio Checklist →
How success is measured
Shipping code is necessary but insufficient. An FDE is measured through production adoption, task quality, workflow impact, reliability, security, cost, user satisfaction and reusable delivery patterns. The metric should be defined before the team claims impact; a demo, anecdote or model benchmark alone is not proof of operational value.
FDE versus adjacent roles
| Role | Usual centre of gravity | Common difference from FDE |
|---|---|---|
| Applied AI Engineer | Model-powered product behaviour | Often product-centred; customer embedding varies |
| Solutions Architect | Feasibility and architecture | May not remain hands-on through adoption |
| Forward Deployed Software Engineer | Custom software delivery | Often has stronger explicit full-stack emphasis |
| FDE | End-to-end enterprise outcome | Owns discovery, engineering, rollout, adoption and feedback |
What should an FDE portfolio prove?
A credible portfolio makes the whole deployment visible: problem and baseline, architecture, code, data, integrations, evaluations, threat model, release controls, observability, adoption, impact and individual contribution. It should explain failed assumptions and trade-offs. Confidential information must be redacted or replaced with a reproducible simulation.
Build evidence across the complete deployment chain.
Review KDigital’s advanced 16-module programme, then speak with an advisor about your strongest anchor and the gaps you need to bridge.
Review the FDE curriculum →