“Forward Deployed Engineer” (FDE) is a hot job title right now. It means an engineer who goes to a client’s company, sits with the people who do the real work, and builds software that runs there — not a demo, the actual system.
But the title hides one important fact: who owns the platform that engineer builds on. That fact splits FDEs into two very different jobs. The market has no separate name for the second one. This article gives it one: VNFDE — Vendor-Neutral Forward Deployed Engineer.
Most FDEs today work for a vendor — a cloud company, an AI lab, a software company. They build using that vendor’s tools only. This is not an accident. The vendor pays the engineer’s salary because the system the engineer builds ties the client to that vendor. Once it’s built, switching to a different vendor later is expensive and painful. The client stays, whether they want to or not.
A VNFDE does the exact same job — same on-site work, same production code, same responsibility to make sure the client actually gets value — but does not tie the client to one vendor. The VNFDE picks whatever tool is genuinely best for the client’s problem. If a better tool appears next year, the client can switch without ripping the whole system apart.
Same work. Same skills. Completely different outcome for the client.
Vendor-Neutral Forward Deployed Engineer (VNFDE): an engineer who embeds with a client, builds production software for that client, and delivers a system the client can run, change, or move to a different provider without being forced to stay with any single vendor.
Three plain tests to check if someone is really a VNFDE:
If any answer is “no,” the engineer is not vendor-neutral, no matter what their business card says. Big companies are pouring billions of dollars into forward-deployed engineering teams this year. When asked about the risk of locking clients in, more than one of them has publicly claimed their system gives clients more freedom than their competitors’ — while still requiring the client to stay on their own platform. That is lock-in, described using the language of freedom. Right now, there is no word a client can use to ask for the real thing instead of the marketing version of it. “VNFDE” is that word.
A clear name changes three things in practice:
If you do this work — embedding with clients, shipping real systems, and refusing to trap them with one vendor — call yourself a VNFDE. If you’re hiring for this work, ask for a VNFDE by name, and check the three tests above before you believe the answer. The job already exists. It just needs a name that means exactly what it does. VNFDE: A Name for the Forward Deployed Engineer Who Doesn’t Lock You In was originally published in Dev Genius on Medium, where people are continuing the conversation by highlighting and responding to this story.