What a Forward-Deployed Engineer Is
Loomwork sells a platform that reads business documents with AI and checks the data inside them. In the sales demo it read a tidy PDF invoice in two seconds. Then Harbourline Freight signed up: a Chennai logistics company whose accounts-payable team, led by Farhan Sheikh, checks 6,000 carrier invoices a month by hand. Their invoices turned out to be scanned photocopies, their agreed carrier rates live in 40 spreadsheets, and their IT team will not let a single invoice leave their own cloud account. Someone has to close the gap between the product and that reality. That someone is you, the forward-deployed engineer (FDE).
The rule
Sit with the customer, write real code, stay until it works.
Each part of the rule does work:
- Sit with the customer. You work inside the customer's world: their office, their chat channels, their meetings. You learn how their work really runs, in their words.
- Write real code. You are an engineer first. You build connectors to their systems, data pipelines, small screens and configuration, not slide decks.
- Stay until it works. Your finish line is in the customer's world. At Harbourline it is "carrier invoices are checked faster and more accurately", not "the ticket is closed".
It helps to compare the role with its neighbours. Each answers a different main question:
| Role | Main question | Typical output |
|---|---|---|
| Product engineer | What should the product do for every customer? | Features for everyone |
| Sales or solutions engineer | Can the product fit this buyer? | Demos and proofs before the deal |
| Consultant | What should the customer do? | Advice and recommendations |
| Support engineer | Why is this broken? | Fixes to reported problems |
| Forward-deployed engineer | What will make the product work here? | A working deployment in the customer's systems |
An FDE borrows a little from each neighbour. What makes the role distinct is the combination: real engineering depth, pointed at one customer's outcome.
The shortcut
To tell whether a task is FDE work, ask three quick questions: whose problem, whose systems, whose finish line? When all three answers point at one customer's real work, the task is squarely yours.
Whose problem?
Harbourline's accounts-payable clerks still retype scanned invoices by hand. That is one customer's real pain.
The common trap is to treat the role as "a salesperson who codes a little" or as "a free custom-software shop". Both miss the point. You write code that must hold up in production, and you write it to make the product succeed in a real setting.
Drills
Answer fast — trust the rule.
Which task is most clearly forward-deployed engineering?
For an FDE at Harbourline, what counts as "done"?
What most separates an FDE from a consultant?
You fix Harbourline's scanned-invoice problem with a clever workaround. Then two other Loomwork customers report the same problem. What does the role expect next?
Remember
- Sit with the customer, write real code, stay until it works.
- Shortcut: whose problem, whose systems, whose finish line? One customer's real work means FDE work.
- Trap: acting as a salesperson who codes a little, or as a free custom-software shop.