How we built the FDE framework, and where it's probably wrong
Six axes, four levels, and an honest list of the decisions I am least sure about.
Eighteen years in software, split roughly evenly across three worlds that rarely talk to each other: early-stage startups finding a first customer, growth-stage companies trying not to break while scaling, and large enterprises where the real work is organizational. That split is why the forward deployed engineer is interesting to me — it is the one role that has to be fluent in all three at once. A community person for most of that time. Contributed to Mozilla in the early open-source days, volunteered with the Python community in India around 2009-10, and until recently helped shape the Cloud Native chapter in Hyderabad. I have watched enough communities form to know that the ones that last are built around something people can argue with, not something people are told. Started the FDE Community because a role this in-demand should not be this undefined.
Founder, FDE Community
Six axes, four levels, and an honest list of the decisions I am least sure about.
A field guide to the part of the job nobody writes down — what to do in weeks one through twelve of a deployment.
Every argument for why an engineering job survives AI sounds the same. Here's a specific one that doesn't depend on optimism.