Engineering Is the Entry Ticket [84]
Forward-deployed engineering engagements often fail due to poor discovery, scoping, and stakeholder management rather than technical deficiencies. Engineering skills are necessary to enter the room, but success depends on identifying success criteria, mapping stakeholders (especially those who lose if the project succeeds), and having leadership cover to push back on misguided requests.
Summary
The episode examines why forward-deployed engineering (FDE) pilots fail by analyzing a real case where an SE team spent 9 of 10 weeks waiting for data access, resulting in a last-minute demo with nothing in production. While this appears to be a customer problem, the deeper issue was that no one knew who owned the data and success criteria were never documented. The hosts argue that technical screening—the standard for hiring SEs—tests only the entry ticket. What actually drives engagement success is discovery methodology, proper scoping, stakeholder management, and understanding the political landscape. The hosts stress that discovery is not innate talent but a learnable method: identifying the stated request, uncovering the real problem beneath it, and quantifying the impact. A critical but often-overlooked step is identifying who loses if the project succeeds—such as an ops lead whose team gets automated—because that person can silently obstruct progress. The episode also highlights a subtle failure mode: delivering clean, on-time code that matches specifications but nobody uses because the spec described what the customer thought they needed, not what they actually need. The hosts emphasize that custom builds with no compounding value are pure cost and that good FDEs must push back on requests, but junior engineers won't do this without explicit cover and backing from leadership. The solution is not a two-day workshop or slide deck, but ongoing coaching through live accounts, with managers reviewing stakeholder maps before kickoffs and listening to actual calls. A practical first step is to pick one live engagement and document two things before any building begins: success criteria with an owner and date, and the name of whoever loses if it works.
About this episode
One of Nate's forward-deployed pods spent nine weeks of a ten-week pilot waiting for data access. He and Ava trace that failure, and the built-to-spec trap, back to customer skills nobody trained, then lay out how leaders can coach those skills on live accounts.
Key Insights
- The hosts argue that engineering skills are a necessary entry ticket to customer rooms but do not determine whether an engagement succeeds; success depends on discovery, scoping, stakeholder management, and political awareness—capabilities that junior engineers often lack.
- The speakers claim that discovery is a teachable method, not innate talent, consisting of three repeatable steps: identifying the stated request, uncovering the real problem, and quantifying impact, and that this method can be trained through live-call coaching rather than workshops.
- A critical failure pattern identified is delivering technically perfect solutions that match specifications but go unused because the spec reflected what the customer thought they needed rather than actual needs, and that preventing this requires SEs to push back on requests with explicit leadership backing.
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
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.
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.
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.