← back
The Dirty Secret of Forward Deployed Engineering — Natalie Meurer, Sierra
Takeaway
Define customer-facing engineering roles by their actual technical work and accountability, rather than the forward deployed title.
Summary
- Forward deployed engineering began at Palantir with on-premises deployment and platform stability, then expanded into data integration and customer-specific applications.
- As the platform matured, engineers moved from keeping systems running to modeling customer data and turning it into decisions.
- Sierra frames agent engineering as a technical discipline with the customer accountability associated with forward deployment.
- The speaker argues that the forward deployed engineer label now covers so many different jobs that it no longer identifies a precise discipline.
forward-deployed-engineeringsierracustomer-outcomes
Original description
At Palantir, forward deployed started as a literal description: you were deployed, physically, at the customer's site, and the onboarding project was keeping the platform from falling over. Natalie Meurer's dirty secret is that the title never settled after that. It stretched across DevOps, data integration, ontology work in Slate and then Foundry, and solution architecture, until forward deployed engineering meant so many different jobs that the label stopped meaning much. Every company hiring for it, whether they call it forward deployed, customer, or deployed engineering, is describing a slightly different role of a particular vintage. Her argument is that the through line was never the code. As coding agents make writing software cheap, the durable part of the job is the rest of it: integrating the data, understanding the customer, and being accountable to an outcome. That is also why she thinks what the industry now calls agent engineering is really forward deployed engineering under a new name. The tell is in how you charge for it: seat based pricing assumes a tool, while pricing to usage or outcome assumes you are on the hook for the result, which is exactly what a forward deployed engineer has always been. Speaker info: https://x.com/natalie_meurer / nataliemeurer Timestamps: 0:00 - Introduction: the dirty secret of FDE 1:54 - FDE as a subdiscipline of AI engineering 3:46 - Palantir origins: leading with location 4:51 - Firefighting platform stability 6:37 - DevOps, data, and the ontology in Slate 9:02 - Why FDE is not one thing 10:46 - Every company hires a different vintage 12:28 - When code gets cheap, outcomes matter 13:55 - Pricing: seats vs usage vs outcome 15:26 - Agent engineering is FDE reborn