Hi there! You’re probably here because you’re curious about Forward Deployed Engineering, attended Propel, or maybe both.
This month, I delivered a keynote to 500 enterprise software professionals at #Propel2026 hosted by Rocketlane.
The topic: What is a Forward Deployed Engineer? When do you need one? And where do FDEs fit inside modern technology organizations?
Forward Deployed Engineering has quickly become one of the most important functions in enterprise software. As software becomes more configurable, more AI-native, and more complex, companies increasingly need people who can bridge the gap between platform capability and customer reality.
People who can build.
People who can manage ambiguity.
People who can sit directly in front of customers and turn problems into outcomes.
A few ideas I wanted to leave the audience with:
1. One Role, Three Disciplines An FDE is a consultant, PM, and engineer rolled into one — directly in front of the customer.
2. Deploy Strategically FDEs should be deployed against high-value, ambiguous problems — not everything. Knowing when not to use an FDE matters just as much.
3. Growth, Not Support FDEs are a growth function, not a support function. They accelerate revenue, unlock expansion opportunities, and help customers realize value faster.