Module 02 · 7 min

FDE vs. The Lookalikes

The title is spreading faster than the operating model behind it. This module gives you the one question that cuts through any job description — and then makes you prove you can use it.

A crowded neighbourhood FDE ? Solutions Eng Architect Prof.Services CustomerSuccess Sales Eng Field Eng Before the sale ← pre-sale | post-sale → Solutions Engineer demos · validates · POCs Solutions Architect designs · recommends Neither is on the hook for production. After the sale Professional Services SOW · billable utilisation Customer Success Eng adoption · health · renewal Each owns a slice. Nobody owns the arc. The FDE spans the whole arc Discovery Architect Build Production Adoption Forward Deployed Engineer …and turns what it learned into product THE QUESTION THAT CUTS THROUGH EVERYTHING “How is success measured?” “Billable utilisation” → this is services “Adoption, reliability, reusable product change” → this is engineering Same title. Genuinely different jobs. Databricks “Senior FDE” Formally: Resident Solutions Architect Professional Services Billable · utilisation Google Cloud “Forward Deployed Engineer” Explicitly NOT advisory Must ship production agentic workflows Embedded builder
The disambiguator

Eight roles, one table

None of these are lesser jobs. They're different jobs. The problem is only that one title is being stapled onto all of them.

RoleWhere it sitsOwns production code?Success measured by
Forward Deployed EngineerDiscovery → adoption → productisationYesAdoption, operational impact, reuse
Solutions engineerPre-saleNoTechnical win rate
Solutions architectDesign and recommendationRarelyArchitecture quality, deal support
Implementation engineerDefined configuration or migrationPartlyDelivery against a defined scope
Professional-services consultantSigned statement of workPartlyBillable utilisation, margin
Customer-success engineerPost-launchNoHealth, retention, renewal
Site-reliability engineerPlatform operationsYesPlatform reliability (not customer outcome)
Sales engineerRevenue acquisitionNoBookings influenced
Field kit

Five questions to ask any posting

1 · How much code will I own?

Strong Production repositories, architecture decisions, code review.

Warning Mostly configuration, demonstrations or ticket escalation.

2 · How is success measured?

Strong Adoption, operational impact, reliability, reusable product change.

Warning Billable utilisation or number of implementations alone.

3 · Where does reusable work go?

Strong Core product, SDK, templates or a deployment platform.

Warning Copied customer repositories with no product pathway.

4 · Who owns the system after launch?

Strong Explicit transition, runbook and operating model.

Warning Permanent informal ownership by the original FDE.

5 · How much travel is expected?

Strong A quantified range and a stated engagement cadence.

Warning “As needed”, with no practical upper boundary.

Published travel, for calibration

Databricks20%
Palantirup to 25%
ServiceNow / Moveworksup to 25%
OpenAIup to 50%

These differences are material to whether the role is sustainable. Establish yours before accepting.

🎮 Game

The Role Sorter

Ten responsibilities, four roles. Get all ten right to earn the Impostor Hunter badge.

Check yourself

Module 02 quiz