FDE Times: get FDE experience before you apply by owning an ambiguous problem at your current job

FDE Times published a career guide on October 14 aimed at engineers whose CVs are full of ticket-driven API work but who want FDE roles that ask for customer discovery and problems with no spec. The core claim, drawing on advice from fde.academy, Scaler, and MindStudio, is that you can practise that work at your current company before you quit.

The piece walks through a warehouse-software example: recurring “file import failed” tickets that no team owns. Instead of patching from logs alone, the engineer sits with support, finds that customers lack a required warehouse-code column, then presents two options to the head of operations in business language—fast default versus a two-week mapping UI—ships the chosen path, and measures ticket volume before and after.

Six steps turn that into evidence: hunt unowned recurring pain, get close to users, write a one-sentence spec and ask to own it for a fixed period, present options to a non-technical decision-maker, ship and measure one number, then leave a one-page artifact. The guide contrasts ticket-style CV lines with FDE-style lines that lead with ambiguity, non-engineers, and the artifact, and flags traps such as picking work that is too big, fixing without talking to users, leaving no written record, or changing another team’s system without inviting review.

For people trying to move into forward deployed roles, the article matters because it treats FDE skill as something you can demonstrate with a small, real problem and a measured outcome, not only with a new job title.