From support engineer to FDE: a realistic path
Updated
Support engineers already own incidents and customers; here is how to convert that into delivery evidence in six months.
Support engineers sit closer to users than most product teams. That proximity converts directly into FDE evidence if you package it right.
The short answer
Turn three incidents into delivery artifacts: one automation, one runbook that others actually use, one postmortem with prevention work shipped. Then write the briefs nobody asked for.
Month by month
Months 1-2: instrument your queue. Tag the top five incident classes with frequency and handle time. The numbers become your portfolio's opening lines. The SLO starter set shows which metrics survive scrutiny.
Months 3-4: automate one triage. Pick the highest-frequency class, build the diagnostic script with an approval gate for destructive actions, publish the runbook. Measure: handle time before and after, escalation share, false-action rate (must be zero).
Months 5-6: write the brief. Choose the incident class that is really a product gap, interview five users, and write the one-page brief with acceptance criteria. You just did discovery; the artifact proves it.
Worked example: the password-reset that was not
A fictional support engineer (fictional) sees 40 reset tickets weekly. Triage shows half are really account-recovery UX failures on mobile. The automation handles true resets; the brief proposes the recovery-flow fix with a success metric (reset tickets down 30 percent in 60 days). One script, one brief: support work becomes delivery work.
Checklist: the conversion
- Three artifacts with numbers, not ticket counts.
- One script a teammate runs without you.
- One brief with in-scope, out-of-scope and success metric.
- One presentation of a trade-off to a non-technical lead.
Related reading
Straight answers
Frequently asked questions
Does support experience count?
Yes when it converts to artifacts: runbooks, scripts, postmortems with numbers. Ticket counts alone do not.
What is the first project?
Automate your most repeated triage with an approval gate, then publish the before-and-after numbers.
What is the hardest gap?
Discovery framing: support answers questions, FDE work questions the request. Practice the brief.