About

The FDE Community is an open-source commons for the forward deployed engineering discipline: a canonical competency framework, routes into the role, writing by people doing the work, and local chapters.

Everything is a file in a public repository. Content is CC BY 4.0, code is MIT.

Why it exists

Forward deployed engineer is one of the most sought-after roles in software and nobody agrees what it is. Search for it and you find a dozen guides published this year by companies selling something adjacent, no two of which define it the same way.

An engineer with eight years of experience can't tell whether she qualifies. A VP told to stand up an FDE function invents the job description from scratch. Both are solving the same missing-standard problem alone, badly, in parallel.

That's a coordination failure, and coordination failures are what communities fix.

Who started it

Rohith Reddy Gopu. 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 rather than technical.

That split is why this role is interesting to me. The forward deployed engineer is the one job that has to be fluent in all three at once — startup improvisation, growth-stage discipline, and enterprise patience — usually in the same week.

I have also been a community person for most of that time. I 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. Enough communities to know that the ones that last are built around something people can argue with, not something people are told.

What it's trying to become

In order, because each step only becomes honest after the one before it:

1. A standard people actually use. A framework cited in leveling conversations and job descriptions, improved by the people it describes.
2. Somewhere to learn the craft. Routes in from the jobs people hold today, and writing about the parts nobody documents.
3. Local chapters. Run by local organizers with a real playbook, not a franchise.
4. Country events, then one global gathering. Only once the chapters exist and want it.
5. A place to hire and be hired. Once there are enough people here to make it worth it.

What it will not become

A certification business. A vendor's community. A job board that sells access to candidates. A course seller. These are written into Governance as commitments rather than left as good intentions, because good intentions are what erode when money arrives.

Where it's today

Launched July 2026. One person, one framework draft, one forming chapter, and a public repository.

Most of this site is a plan rather than a crowd, and it says so wherever that's true. The alternative — inventing member counts and seeding chapters in cities where nobody volunteered — would make it look better today and be worth less.