Do Forward Deployed Engineers Code? Yes, and Here Is How

Yes, forward deployed engineers code

The job descriptions are clear on this. In the July 2026 census of 292 FDE roles, 42% of descriptions emphasized Python, 34% called out data, SQL, or pipelines, and 59% highlighted APIs or integrations. Those are core building activities, not occasional side tasks, and they show up across a large share of postings. An FDE is expected to open an editor and produce working software.

At the same time, 98% of those descriptions emphasized customer-facing work, which is the highest signal in the entire dataset. That combination is the whole identity of the role. The coding is real and the customer contact is constant; neither one is a garnish on the other. When people ask whether FDEs code, the honest answer is yes, and they do it while staying close to the people they build for.

What forward deployed engineers actually build

The census points to a fairly consistent technical toolkit. It skews toward glue work and data, the kind of building that turns a general product into something that fits one customer's specific reality.

Python and scripting

With 42% of descriptions emphasizing Python, it is the most commonly named language, and for good reason. FDEs use Python to automate workflows, transform data, prototype quickly, and stitch systems together. It is the default tool for turning a rough customer requirement into something running, and comfort with it is close to a baseline expectation for the role.

SQL, data, and pipelines

Data work is central, with 34% of descriptions calling out data, SQL, or pipelines. A large part of the job is getting the customer's data into a usable shape: writing queries, building pipelines, and reasoning about how information flows through their systems. Strong SQL and a solid grasp of data modeling tend to separate comfortable FDEs from struggling ones.

APIs, integrations, and sometimes front-end

Integration is the most-cited technical theme, with 59% of descriptions highlighting APIs or integrations. Much of an FDE's code connects the product to the customer's existing tools and systems. Some roles also involve building front-end interfaces or lightweight applications so customers can see and use what was built, though the depth of front-end work varies more from posting to posting than the data and integration work does.

How much is coding, and how it differs from a pure SWE role

There is no single split that fits every FDE role, and honest ranges vary by company and engagement. What the data makes clear is that coding and customer work coexist rather than trade off cleanly. With 98% of descriptions emphasizing customer-facing work and strong technical signals throughout, a typical week mixes building software with discovery calls, demos, and steady communication with stakeholders. Expect real coding time, not a full uninterrupted engineering calendar.

That is the key difference from a pure software engineer role. A back-end SWE can often go deep on one system for days with minimal outside contact; an FDE context-switches between writing code and talking to the people it is for, and that context is a feature of the job rather than a distraction from it. The scope of code tends to be broad rather than deep: integrations and pipelines across many surfaces instead of years spent inside one large codebase.

If you want to prepare for that reality, practice the two halves together instead of separately. Rung is built for exactly this: you write code in the browser against real tests, practice SQL on live datasets, work through applied-AI scenario drills modeled on ambiguous customer problems, and run mock interviews with an AI interviewer that pushes on both your implementation and how clearly you can explain it to a stakeholder.