A structured framework for CTOs and VPs of Engineering to choose between three client-facing technical roles: Forward Deployed Engineer (FDE), Solutions Architect (SA), and Technical Account Manager (TAM). The core distinction is code ownership — FDEs write and own production code in customer environments, SAs produce architecture artifacts without committing code, and TAMs manage account health post-deployment. Includes a 5-axis decision matrix, three real-world scenarios, common anti-patterns with cost estimates, and a sequential staffing model (FDE → SA → TAM) that maps role transitions to product lifecycle stages.
Table of contents
TL;DR, the code ownership line decidesThe One Line That Separates an FDE from an SAWhere the TAM fits: Post-deployment is a different problem5-axis decision matrix: Choosing the right roleThree scenarios: Which role wins and whyAnti-Patterns: What It Costs to Hire the Wrong RoleSequential staffing: FDE → SA → TAM across the product lifecycleTL;DR, the code ownership line decidesFAQ: Role-selection questions from engineering leadersHow Netguru staffs client-facing technical roles50 Impressions