Remote Forward Deployed Engineer Jobs: Do They Exist?

Published July 5, 20263 min read
Home office setup with laptop and monitor

Search any job board for "remote Forward Deployed Engineer" and you'll find a contradiction in terms: a role literally named for being deployed forward to the customer, advertised as work-from-home. So do remote FDE jobs actually exist?

Yes — but they're rare, structurally specific, and worth understanding before you filter your search. On our live index (pulled directly from company career feeds hourly), roughly 5% of FDE postings are fully remote and about a third are explicitly hybrid. Here's where the remote roles hide, and how to get the flexibility without waiting for a unicorn posting.

Why most FDE roles can't be remote

The FDE value proposition is proximity. The job exists because platforms don't deploy themselves — someone has to sit with the customer's ops team, absorb the unspoken context, win over the skeptical DBA, and be in the room when the demo lands or breaks. Three forces keep the role physical:

  1. Trust velocity. Embedded engineers earn in weeks what remote engineers earn in quarters. Customers paying seven figures expect faces.
  2. Data gravity. Plenty of deployments touch on-prem, air-gapped, or classified systems that can only be accessed on-site — the entire Palantir government business runs this way.
  3. The sales shadow. FDE work is revenue work, and sales culture treats showing up as table stakes.

Remote engineer on a video call from a home desk
Remote engineer on a video call from a home desk

Where remote FDE jobs actually exist

The exceptions follow patterns:

  • Global coverage pods. Companies serving customers in regions where they have no office hire remote FDEs in-region — a remote FDE in India or Brazil covering local accounts. These are the most common fully-remote postings on our index, from companies like Databricks and Cohere.
  • Developer-tool deployments. When the "customer stakeholder" is another engineering team, embedding over Zoom and Slack works far better than it does with claims adjusters. Baseten-style inference-infrastructure roles are the canonical case.
  • Post-deployment ownership. Some orgs split "land" (travel-heavy) from "expand and sustain" (remote-friendly). Senior FDEs who've banked customer trust often negotiate into the second bucket.
  • Cleared-but-remote government work. Counterintuitively, some US-government programmes hire remote FDEs for unclassified workstreams, with occasional SCIF visits.

Traveller with a laptop bag crossing an airport terminal
Traveller with a laptop bag crossing an airport terminal

Hybrid is the real answer

If you want FDE work with flexibility, the realistic target isn't "remote" — it's low-travel hybrid, which is now the dominant mode at AI-native companies. A typical OpenAI or Anthropic enterprise FDE works from home or a hub office most of the week with travel bursts around kickoffs, go-lives, and executive reviews — commonly 20–40% travel, concentrated rather than constant.

Questions that surface the honest number in interviews (more in our interview guide):

  • "For the specific accounts this role covers, how many on-site days did the last person average per month?"
  • "Is travel steady-state or bursty around milestones?"
  • "Can deployment weeks be batched — e.g., one week on-site per month rather than two days every week?"

Negotiating remote flexibility

Leverage in FDE roles is account-shaped, so negotiate account-shape, not policy:

  1. Region-match yourself. Applying from a city with a cluster of the company's customers makes you cheap to deploy — the strongest remote-friendly argument there is.
  2. Trade travel peaks for remote troughs. Offering genuine flexibility during go-lives buys credibility for remote-by-default the rest of the time.
  3. Aim senior. Remote flexibility correlates with seniority; customers accept video from the architect they already trust. If you're early-career, expect (and honestly, seek) the travel — the embedded reps are what compound your career fastest.
  4. Watch pay geography. Some companies band remote pay by location; a "remote" offer at a lower band can cost more than the flights would have. Check bands against our salary guide.

Where to look right now

We maintain a dedicated, always-current page of fully-remote FDE roles, plus hybrid filtering across the whole index:

Star the roles you like and save your search filters from a free account — new matching roles land hourly.

Frequently asked questions

Can Forward Deployed Engineers work remotely?

Sometimes. Fully-remote FDE roles exist — typically global support pods, developer-tooling deployments, and some government programmes — but they're a small minority. Most FDE roles are hybrid: home- or office-based with regular customer travel.

What percentage of FDE jobs are remote?

On our live index, roughly 5% of FDE postings are fully remote and about a third are explicitly hybrid. The customer-embedded nature of the role keeps fully-remote scarce compared to general software engineering.

Which companies hire remote FDEs?

Databricks, Baseten, Cohere, and various AI startups post remote-eligible FDE roles most often, usually for regions where they have customers but no office. OpenAI and Anthropic FDE roles are mostly hybrid; Palantir FDSE roles are mostly on-site/travel-heavy.

How much travel does a hybrid FDE role involve?

Anywhere from a few customer visits per quarter (AI-company enterprise pods) to 3–4 days per week on-site (Palantir government work). Always ask for the honest number in interviews — it varies more by account than by company.

Ready for your next FDE role?

Browse verified Forward Deployed Engineer jobs, updated every 6 hours.