Remote Forward Deployed Engineer Jobs (2026): A Quarter of the Board, With an Asterisk
The phrase “remote Forward Deployed Engineer” sounds like a contradiction. The job is named after deployment — the whole idea is that you go to where the customer is, sit in their office, and untangle problems they haven’t managed to describe to anyone else. So candidates tend to assume remote FDE roles barely exist, and recruiters tend to bury the location question until late in the process. Both are wrong, but in opposite directions. Remote FDE jobs are more common than the name implies — and less remote than the listing implies. Here’s what the board actually shows.
A quarter of the board says “remote”
On the fde.directory board in early September 2026, of 216 open listings, 55 mention remote — any role whose location or tags include remote or remote-flexible. That’s 25%, one in four. For a role built around physical presence, that is a genuinely surprising number, and it’s the first thing to correct: if you’ve been assuming you have to move to San Francisco or New York to do this work, a quarter of the market disagrees.
Dig one level down, though, and the 55 split into two very different things:
| Category | Count | What it actually means |
|---|---|---|
| Remote-first (location starts with “Remote”) | 36 | Company is genuinely distributed; no anchor office required |
| City + remote option | 19 | HQ role with remote flexibility bolted on |
| Global remote (not US-only) | 4 | Can be based nearly anywhere |
So the honest count of truly remote-first FDE seats is 36, about 17% of the board. The other 19 are San-Francisco-or-New-York roles that will “consider remote” — worth applying to, but the center of gravity is still the office. And of the 36, only a handful (Cloudflare, GitLab, Ava Labs, MongoDB’s international listing) are open beyond a single country. If you’re outside the US hoping to work remotely for a US FDE team, that four is your realistic universe.
“Remote” is not “no travel”
Here’s the asterisk that the word “remote” hides. A remote FDE job means you don’t report to an office five days a week. It does not mean you stop visiting customers — and for this role, customer visits are the job, not a perk. Across the board, 36 listings explicitly mention travel, and the numbers are not small. Re:Build Manufacturing lists one of our remote seats as “Remote (US), up to 75% travel to plants.” Palantir, the company that coined the modern FDE, tells candidates to expect travel “up to 25%” to client sites, and independent reports put the broader market at 25–50% depending on team and account (Pragmatic Engineer, Exponent).
Read those two facts together and the real shape of a “remote FDE” role appears: your base is your home, but your work is still on the road. You’re trading a daily commute for a suitcase. For some people that’s a better deal — no relocation, live where you like, deep-focus days between trips. For others it’s the worst of both worlds — the isolation of remote work plus the disruption of travel. The mistake is reading “remote” as “sedentary.” Price the travel in early; if a listing goes quiet on the travel percentage, that’s the first question to ask on the call, not the last.
Where the remote seats actually live
The remote-first roles aren’t scattered evenly across the market — they cluster. Look at who’s hiring them: Databricks, Snowflake, MongoDB, GitLab, Cloudflare, Twilio, Redpanda, Tailscale, Alteryx, Monte Carlo, Warp. That’s a roster of infrastructure, data, and developer-tools companies — firms that were already remote-native as organizations and whose “deployment” work is often as much about integration and enablement over a screen share as it is about sitting in a customer’s war room.
Compare that with the companies whose FDE listings are firmly on-site: the frontier AI labs. The pattern is consistent — the closer a company sits to the research frontier, and the more its deployments involve novel, high-touch, figure-it-out-in-the-room work, the more it wants bodies in the building. The infrastructure and enterprise-SaaS end of the market, where the product is more mature and the integration playbook more repeatable, is where remote flexibility concentrates. That’s the single most useful filter for a remote job hunt: if geography is your hard constraint, weight your search toward infra, data, and dev-tools FDE roles, and treat the frontier-lab seats as on-site until proven otherwise.
It also reframes what remote FDE work is. At a Databricks or a Snowflake, a remote FDE looks a lot like a technical account owner who deploys, integrates, and expands a known platform inside enterprise customers — high value, but a different daily rhythm from the ambiguity-heavy, embedded work at an OpenAI or a Palantir. Neither is better. But they’re not interchangeable, and “remote” is a surprisingly reliable signal of which one you’re looking at.
The practical read
If remote is a preference, you have real range — a quarter of the board is in play, and you should apply widely, including to the city-plus-remote roles where flexibility is negotiable. If remote is a hard requirement, your realistic pool is closer to the 36 remote-first seats, concentrated in infrastructure and developer-tools companies, and you should read every one of them for the travel line before you get attached. And wherever you land, remember the asterisk: the best remote FDE roles still put you in front of customers regularly. The ones that don’t are usually the ones that quietly stopped being forward-deployed at all.
Want the remote-flagged FDE roles as they post? Browse the board or subscribe for the weekly.
— A. George