An FDE's code only matters if the customer trusts them enough to adopt it — the relationship is not soft-skills garnish, it's the delivery mechanism.
An FDE's code only lands if the customer trusts them: earning trust in small kept promises, speaking the customer's outcomes and vocabulary, managing expectations relentlessly, navigating the org (champion/skeptic), and delivering bad news well.
The problem a customer first describes is almost never the problem worth solving — an FDE's first job is to dig until the real one surfaces.
The problem a customer first states is rarely the one worth solving: discovery techniques (ask why, watch real work, find the decision), the jobs-to-be-done lens, mapping stakeholders and constraints, and writing a confirmed problem frame.
Part software engineer, part consultant, part product manager — the forward deployed engineer works inside the customer's world to turn a hard problem into working software, then carries what they learn back to the product.
The opener to a forward deployed engineering series: the FDE role as a blend of engineer, consultant, and product manager — embedded at the customer, building real software against a vague problem, then carrying the learnings back to the product.