Tudor Panturu
ENES
Field notes / 07

Forward deployed engineer, by another name

Some software only pays off once somebody makes it work inside a real company: its systems, its data and its politics. A forward deployed engineer is that somebody. The role starts from the customer’s problem and works inward to the product, and it stays until the thing is in use. It is in demand because AI products are powerful and hard to connect to how a company actually runs. The title is new to most people. The work is not. I have done it for years as a technical manager, a solutions architect and a product owner.

What the role asks for, and where I learned it

  1. 01

    Start from the customer’s problem, not from the product.

    The inside operator’s hat. Inside a company you see what the business will actually use and pay for. The product comes second.

  2. 02

    Get into the real systems.

    The integrator’s hat. The ERP, the legacy system nobody documents and the security review decide what can launch. A solution that ignores them stays a demo.

  3. 03

    Build what the standard product does not cover.

    The builder’s hat. Custom modules, integrations and migrations were the agency’s daily work.

  4. 04

    Ship a working answer before a perfect one.

    The builder’s hat again. First the part that moves the needle, then the rest.

  5. 05

    Translate in both directions.

    The integrator’s hat. The boardroom and the engineering team need the same facts in different words, and what the field teaches has to reach the people who build the product.

  6. 06

    Judge what is worth building.

    All three hats. Some requests should be built, some configured and some declined, and saying which is part of the job.

Forward deployed engineer Three hats Customer’s problem Real systems Custom build Working first Translation Judgement The title, the sender, the keyboard

The words job descriptions use

Titles
Forward deployed engineer, FDE, forward deployed software engineer, solutions engineer, customer engineer, implementation engineer
What it does
Works inside the customer’s environment, integrates with the systems already there, builds what is missing, feeds what it learns back to the product team
What it is measured on
Time to value, adoption, retention

Where it differs

  • The title. Nobody has called me a forward deployed engineer.
  • The sender. The role is usually sent by a software vendor into its customer. I was sent by an agency or a consultancy, or sat inside the company itself, and worked with whichever product the problem needed.
  • The keyboard. The role writes production code as part of the job. I direct more of the code than I type, more and more through AI agents, and I review what ships.

Public sources

All field notes Next note Map the terrain first