FDE vs. solutions engineer: five real differences, and why most FDE engagements fail for non-engineering reasons

In an October 7 essay, Tim Brömme and Jan-Erik Jank of presales coaching firm SE Rockstars compare forward deployed engineers with solutions engineers. Citing Bloomberry's analysis of about 1,000 FDE postings, they note that "working directly with customers" was the top listed responsibility (55%), ahead of building AI systems (37%), and that 0% of those roles carried a quota.

They name five real differences: SEs mostly work before the contract and FDEs after it; SEs produce proof while FDEs ship production code; SEs earn base plus variable pay while FDEs usually get equity; SEs report into sales while FDEs mostly report into a dedicated FDE team or engineering; and SEs cover many deals while FDEs go deep on a few customers. Tailscale is cited as an exception, with FDE pay tied to quarterly sales targets.

To tell a real FDE job from a rebrand, they suggest asking whether the manager reports to sales, whether pay is tied to sales targets, and whether the role starts before the contract. Two or three yeses point to an SE role with a new title.

The authors argue documented FDE failures are rarely engineering failures: stalled pilots come from unsecured data access and unagreed success criteria, and polished builds go unused when nobody questioned the requirements. For FDE candidates, it is a reminder that discovery, stakeholder mapping and the confidence to say no to one-off customizations matter as much as code.