OpenAI details its Forward Deployed Engineering team and the "deployment gap"
OpenAI published a first-person account of its Forward Deployed Engineering (FDE) team, which its lead says was founded in early 2025 to close a "deployment gap" between what models appear capable of and what people can reliably use at work. The post says FDEs work alongside customers on their hardest problems and cites John Deere, which used OpenAI APIs to give farmers personalized setup guidance and support for its See & Spray precision weed-control technology. OpenAI says one life-sciences project cut roughly 90% of custom code after rebuilding around Codex, and that a customer-service voice model's scores on key evals rose from about 60% to 90%+ over six months with Research involvement; these claims are vendor-reported.
The post is a detailed vendor-authored look at how OpenAI organizes enterprise deployment work and feeds customer problems back into products and research, though its performance and customer-impact figures are self-reported.
When Codex came out, someone on the team asked me, “What do we do when Codex can just one-shot the use cases we spent the last few months building?”
That question gets to the heart of what FDE means at OpenAI. We work alongside customers to understand their hardest problems and build solutions they can depend on. What we learn helps shape our products and gives Research concrete problems to solve.
That is progress. If we make ourselves obsolete every couple of months, our FDE team is doing its job.
I founded the team in early 2025 to close what we call**“the deployment gap”:**the distance between what models appear capable of and what people can reliably use to do their work.
Deployment gap diagram showing the gap between available AI intelligence and business value.
Model capabilities have moved faster than the systems and processes needed to put them to use. Sometimes the missing piece is a product. Sometimes a model performs well on a benchmark but cannot do the job with real-life variables and constraints.