FDE vs Technical Consultant: Employment Model vs Delivery Model
Updated · Tech checked
Technical consultants sell expertise and recommendations, often document-first and billable-by-the-hour; FDEs are embedded builders accountable for shipped, running systems. The difference is accountability for production, not seniority.
The short answer
A technical consultant is hired for judgment and often delivers documents, assessments, and recommendations - with implementation done by the client or a delivery team. An FDE is accountable for the implemented result. Consultants bill hours or fixed scopes; FDEs own outcomes regardless of hours.
Where they genuinely overlap
Both run discovery, write briefs, manage stakeholders, and trade off scope. Great consultants often make great FDEs - after they prove they can ship production code and operate it. That proof is exactly what the portfolio and practical assessments exist to show.
Billing and incentive differences
- Consultant: utilization targets, scope discipline, change requests as revenue.
- FDE: customer adoption and reliability targets; change requests as risk to manage.
- Consulting rewards the well-reasoned memo; FDE work rewards the memo and the working system.
Continue: FDE vs sales engineer · Forward engineering vs forward deployed engineering