Forward Deployed Engineer is a job title you hear a lot lately. The idea is simple: instead of building software in an office and shipping it to the customer, you go to the customer, learn how they actually work, and build the fix on the ground.
EDI people have been doing a version of this for years. When a retailer's 856 keeps failing, you do not fix it from the spec. You sit with the warehouse team, watch the packing bench, and find the label printer nobody told you about. Then you fix the map.
The spec will tell you the segment order. It will not tell you that the night shift skips the scan when the line backs up, or that the label stock changed last Tuesday. That is the kind of thing you only learn standing next to the bench.
The FDE version adds one thing: you stay. You do not hand over a spec and leave. You embed with the team, learn the exceptions, and keep shaping the solution until it survives contact with the real operation.
Staying means you see the second and third versions of the problem. The first fix handles the normal case. The exceptions show up in week three, when the seasonal staff start and the returns pile up. An FDE is still there for that.
That is also why the title is showing up next to AI work. An agent that reads purchase orders is easy to demo. An agent that survives a real receiving dock is a different job. It needs someone who has watched the dock.
Most AI demos happen in a browser. The receiving dock has bad lighting, torn labels, and a scanner that drops characters. The model is the easy part. Knowing which failures matter is the job.
I have spent seven years in EDI and supply-chain integration. Most of that time was FDE work before the title existed.
Now I do it with AI in the loop. The discipline is the same. The tools got better.