Rebrand or Real Role? The FDE Test [86]
The episode examines whether Forward Deployed Engineers (FDEs) represent a genuinely different role from Solution Engineers or merely a rebranding strategy. Through analysis of real job postings and market trends, the hosts present a three-question test to distinguish authentic FDE positions from SE roles with inflated titles.
Summary
The episode opens with a relatable dilemma: a CEO asking about hiring FDEs, an SE receiving a competing offer with a different title but similar work, and questions about compensation and titling misalignment. Nate and Ava address whether FDEs and SEs are fundamentally different roles. While acknowledging similarities, they identify five genuine differences: timing (SEs work pre-signature, FDEs mostly post-signature), output (SEs produce proof, FDEs ship production code to live customer environments), compensation structure (SEs are base-plus-variable around 70-30 split, FDEs get base-plus-equity), reporting lines (FDEs report to dedicated teams, engineering, or go-to-market in varying percentages), and account load (SEs cover 3-5 AEs with 20-30 quarterly deals, while FDEs focus on 1-2 deep customers). However, analysis of roughly 1,000 FDE postings reveals that 55% list direct customer work as the top responsibility, with only 37% emphasizing AI systems—contrary to market perception. About 22% of FDE hires come from SE or solution architect backgrounds. The hosts identify the critical issue: candidates accepting FDE titles discover they're performing pre-sale demo work similar to SEs, leading to feelings of deception and high turnover. The proposed solution is a three-question test: Does the manager report to sales? Is pay tied to sales targets? Does the role start before the contract? Two or three affirmative answers indicate an SE role with a new label. Nate qualifies this for lean teams where everyone touches pre-sales. The core insight is that the FDE trend represents the market recognizing that SE skills command engineering-level salaries, not genuine role differentiation. The final recommendation: instead of hiring new FDE teams, organizations should price existing SEs as the engineers they already are.
About this episode
Nate built a quick test after his CEO asked whether to hire forward deployed engineers and an SE got poached by the title. He and Ava sort out where FDE and SE really differ, where they're the same job, and what the trend says about SE pay.
Key Insights
- The hosts' analysis of approximately 1,000 FDE job postings found that direct customer work (55%) is the most common responsibility, while AI systems building ranks second at only 37%, contradicting widespread market perception about what FDEs primarily do.
- The hosts argue that the FDE trend is fundamentally the market recognizing that Solution Engineer skills command engineering-level compensation, describing this as 'title arbitrage' rather than a substantively different job category.
- The hosts claim that candidates who accept FDE titles experience disillusionment by month three when they discover their actual responsibilities involve sales-driven demo work and quotas identical to SE roles, resulting in higher-than-necessary turnover and damaged employee trust.
Topics
Transcript
Hey there and welcome to Leading Pre-Sales, the show for solution engineering leaders who want to build teams that drive revenue and not just demos. My name is Tim and I'm the co-founder of SE Rockstars. And together with Jan, we've coached over 350 solution engineers and their leaders across several dozens of companies. Every conversation you hear on this show is based on real coaching situations, real challenges, real problems that SE leaders like you are dealing with right now. None of this is made up. We use AI to bring these stories to life, through our two hosts, Nate and Ava, but the insights come straight from the trenches. Each episode gives you one actionable takeaway you can…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Leading PreSales | The Solution Engineering Leadership Show
Core vs. Context: When Your SEs Should Let a Build Deal Go [92]
The episode teaches solution engineering leaders to distinguish between core and context business functions when customers consider building custom solutions versus buying software. SEs should let lightweight, context-focused builds go while fighting harder for core capabilities, and leaders must publicly validate this approach to change team culture.
The Iceberg Under Every Build Deal [91]
Solution engineering leaders need a standardized five-year cost model to evaluate Build vs. Buy decisions in the AI era, grounded in hidden maintenance costs and opportunity expenses rather than vendor pitches. The key is creating an 'iceberg checklist' of often-overlooked costs and having customers co-create the financial analysis rather than presenting a pre-built case.
Leaderboards, Not Cameras [89]
The episode examines why AI adoption dashboards and leaderboards often fail to drive behavior change, and proposes an alternative approach: publicly sharing AI workflows that actually shipped on real deals, ranked by peer reuse rather than usage metrics.
Your SEs Just Inherited the Customer's Bill [88]
Solution engineers must own usage estimation and sizing in consumption-based pricing models, even though they don't set prices. When SEs fail to accurately estimate how often workflows trigger, customers face billing surprises that damage relationships and renewals.
No Quota, Still Commercial [85]
Forward Deployed Engineers (FDEs) should be measured on time-to-first-value and usage ramp rather than traditional sales quotas, with compensation tied to commercial outcomes that directly correlate to revenue under consumption pricing models. Success requires a disciplined 10x cost-recovery model, a defined pilot-to-contract path, and mandatory product feedback loops to prevent FDE teams from becoming expensive consulting operations.