What is a Forward Deployed Engineer, and why does a district need one?

Short answer: a forward deployed engineer (FDE) is a software engineer who works inside the customer’s organization rather than back at the vendor. They sit with the people doing the work, write code on the customer’s own systems, and stay until the thing runs without them. The distinguishing detail is simple: an FDE ships working software on your infrastructure, not a recommendation about it.

Where the role came from

Palantir invented the model in the early 2010s and called it “Delta” internally. It worked well enough that until roughly 2016, Palantir employed more forward deployed engineers than conventional software engineers. The role stayed niche for a decade; OpenAI stood up its own program in early 2025, Ramp, Salesforce, Gecko Robotics and Commure are hiring for it now, and a16z has called it the hottest job in tech (The Pragmatic Engineer).

AI is what made it urgent. A language model is not a product you install. It is a capability that has to be pointed at one organization’s actual mess — its file naming, its permit backlog, its ten-year-old database — before it does anything worth paying for. Somebody has to be in the room to do the pointing.

What it is not

• Not a consultant. A consultant delivers a recommendation and leaves. An FDE delivers something that runs on Monday and is still running in November.
• Not a solutions engineer. The line is sharper than it looks. At OpenAI, solutions architects rarely write code on customer infrastructure and build proofs of concept against anonymized data. FDEs work on the real thing, with the real mess in it.
• Not a vendor rep. A vendor rep configures the parts the platform already supports. An FDE builds the part that does not exist yet, which in local government is usually most of it.
• Not staff augmentation. The point is not more hands. The point is one person who owns the outcome end to end.

What to look for in a district engagement

Florida runs a great deal of its government through special districts — mosquito control, water control, fire, community development. Almost none have a software team. What they have is a small staff, a board, a budget cycle governed by s. 200.065, and a stack of recurring work that eats the week.

1. They write code on your systems. If the deliverable is a slide deck, you hired the wrong role.
2. They start with one workflow you already hate. Not a transformation. One thing, shipped.
3. They log everything. Inputs and outputs both, because in Florida both may be public records under Ch. 119 — a question for your district counsel, not for a vendor.
4. They leave documentation a successor can read. The failure mode of embedded work is that it only runs while that person is there.
5. They tell you what to stop paying for. An FDE who never finds a subscription to cancel is selling, not building.

Why it matters now

The gap in local government is not enthusiasm for AI. Sit through any district conference session and the interest is obvious. The gap is that between “we should try this” and “this runs every Tuesday without anyone thinking about it” there is a person, and that person is not on most district org charts. You can buy software. You cannot buy the translation between what your district actually does and what the software assumes. That translation is the job.

Key takeaways

• A forward deployed engineer builds working software inside your organization, on your systems, and stays until it runs without them.
• The role is not a consultant, a solutions engineer, or a vendor rep — the difference is whether code ships on your infrastructure.
• For a special district, the right first engagement is one workflow you already hate, logged and documented, not a transformation program.

This is the role Good Combinator’s FDE certification is built around. Related reading: how a special district adopts AI responsibly, how a local government should buy AI, and what auditable AI means. Or get in touch.