FDE PulseFDE jobs open 441New in 7 days 29Companies hiring 47Remote-friendly 24%Median US pay $216kTop hirer Databricks 125
VINewsletterSaved
VI

The newspaper of the Forward Deployed Engineer

Guide

How to become a Forward Deployed Engineer

Most FDEs arrive from software engineering, solutions or sales engineering, or consulting. Each starting point brings half of the job and leaves a different half to learn: production code for some, customer work for others.

This path follows the order of the move: understand what the role is and is not, close your gap, build proof you can show, get through the hiring loop, then plan the first months and what comes after.

1. Understand the role

  1. What is a Forward Deployed Engineer?

    The role, the skills, who hires and what it pays, in one page.

  2. FDE vs software engineer: both write code, but the FDE owns one customer's outcome

    When your code ships to one customer rather than to everyone, the way you define "done", choose solutions and talk to people every day has to change.

  3. FDE or Solutions Architect: the dividing line is who commits to production

    Both roles can draw the same diagram. Only one has to open a pull request in the customer's repo and get it running reliably in production.

  4. AI Engineer, ML Engineer and FDE: same toolkit, different accountability

    Employers use these job titles interchangeably, and AI and ML Engineers work with the same tools. What sets the FDE apart is who defines the problem and what counts as done.

  5. What separates an FDE from a consultant is not speed but where the lessons go

    Palantir once turned down deals it called "Accenture-with-better-software". That refusal says more than any side-by-side comparison about what makes an FDE different from a consultant.

2. Close your gap

  1. From software engineer to FDE: production code only gets you through the door

    FDE recruiters take for granted the skill you spent years perfecting. What they actually score you on is the thing your current job keeps out of sight.

  2. From solutions engineer to FDE: rebuilding a PoC to production standard

    The demo that won the client over will break on the first malformed CSV. As an FDE, you are the one who has to fix it.

  3. New-grad FDE roles are real, but the door is narrow and opens by season

    Palantir and Applied Intuition are hiring forward deployed engineers who have not yet graduated, while recruiters warn the job needs senior judgement. Both sides are right, and engineers in Vietnam need to know where they stand.

  4. For Vietnamese engineers, the way into FDE work runs through labs that want you in the office, not through “Remote” listings

    One Forward Deployed Engineer listing labelled “Remote” accepts only US citizens. Meanwhile, the labs that openly require office attendance sponsor visas or help with relocation. Which of these should an engineer in Vietnam go after?

3. Build proof you can show

  1. Building an FDE portfolio repo: a simple agent, evals built from real failures, a README and a 3-minute video

    A polished demo only proves the agent got it right once. A repo worth sending shows where the agent fails and how often.

  2. The FDE CV: drop the framework list, state deployment results with a baseline

    People hiring forward deployed engineers read a CV looking for a result they can verify, so a line reading “LangChain, Kafka, Kubernetes” tells them almost nothing.

4. Get hired

  1. The FDE interview, round by round

    Decomposition, coding, take-home, company loops.

  2. Companies hiring FDEs now

    Every company with open FDE roles, its role count and posted pay.

  3. FDE salary: what job posts actually pay

    Posted base-pay ranges from US job posts, by seniority, company and city. Updated daily.

  4. What FDE recruiters look for: code gets you in, customer communication sets the ranking

    You cannot work as an FDE without coding. Once candidates have shown they can code, what decides who gets hired is how well they communicate with customers and win them over.

  5. Same FDE title, very different job: five tests for spotting the impostor roles in a job posting

    FDE job postings are multiplying fast, and the title no longer tells you what you will actually do. To find out, read how the company measures success and where the code you write ends up.

5. Your first 90 days

  1. The FDE 30-60-90 day plan: a six-week target leaves about four weeks with the customer

    The first two weeks usually go on internal work. A new FDE has to pick one small, high-impact task and agree it with the customer before hitting the wall in week five or six.

6. Where it leads

  1. After a few years as an FDE, choose your exit by the gap you are willing to fill

    Principal FDE, product manager, engineering manager and founder all draw on the same field experience with customers. Each route also demands one skill that day-to-day FDE work barely teaches.

  2. From FDE to founder: which habits carry over and which must be relearned

    Y Combinator tells founders to work like engineers embedded with customers. The reverse is only half true, and the missing half decides whether you build a product company or a services business.

  3. FDE work for government and defence: the pay is lower than the rumours, and the real cost is elsewhere

    Job postings from Palantir and Anduril, along with OpenAI salary figures, show that forward deployed engineers working for the state are not paid more. The real costs are security clearances, time away from home and ethical questions about the clients you will serve.