FDE Times: FDE vs Technical Account Manager — who fixes the system and who talks to the customer in an incident
A 4 November FDE Times guide splits peak-night incidents: the FDE owns the fault (logs, rollback, patch); the TAM owns customer communication and specialist coordination. It recommends a fixed-cadence three-line update template so both jobs happen without both people doing the same one.
On the eve of a customer’s biggest sale, the system you deployed starts erroring. If both the Forward Deployed Engineer and the Technical Account Manager open a terminal, nobody informs the customer; if both pick up the phone, nobody fixes the fault. FDE Times’s 4 November guide draws the line using AWS Enterprise Support’s TAM model and Palantir’s on-call FDE variants.
FDEs write production code and often carry first-responder duty; TAMs read code but create value through long-term relationships, readiness checks and specialist coordination. Before a peak, the FDE brings load-test numbers and a runbook; the TAM confirms who on the customer side has decision authority. During the incident, the FDE remediates while the TAM keeps leadership informed.
The hand-off that usually breaks is information flow. Agree in advance on a three-line cadence the FDE sends the TAM — what is broken, what is being done, when the next update comes — so the TAM can translate impact without the FDE leaving the terminal, and neither role promises a fix time they cannot own. Afterward, send one joint product feedback note rather than two conflicting emails.
Source: fdetimes.net