What makes a great Forward Deployed Engineer

Job descriptions for Forward Deployed Engineers usually ask for two things: production engineering experience (5+ years) and "customer-facing communication skills." Both are necessary; neither is sufficient.

After interviewing 100+ FDEs in our Founding 100 verification pass, and after a decade of watching Palantir alumni become the most sought-after operators in mid-market AI, here's what actually predicts a great Forward Deployed Engineer.

1. They are comfortable in unstructured environments.

The single biggest filter. An FDE walks into a customer's office on day one not knowing where the bathroom is, much less the data schema. They have to scope the work, pick the tools, recruit the customer-side stakeholders, ship in 8 weeks, and document for handover. None of that is in the JD. All of it is the job.

This filters out 60% of strong full-stack engineers immediately. The rest is shape-matching for the other traits.

2. They write at least three pages of dense English without prompting.

The deliverable that converts an FDE engagement is usually not the code — it's the memo the FDE writes after week 2 explaining what they found, what they're going to build, and what the customer needs to do to make it stick. That memo is the political artifact that gets budget renewed.

Engineers who can write this memo are rare. Most ICs above L5 can; almost no L3-L4 engineers can without a coach. We screen for this with a take-home: "Write me a memo about a system you've shipped and how it could have failed."

3. They have shipped at least one thing they had to defend in a meeting they didn't want to be in.

This is the toughness check. Customer-side rooms are not friendly. Senior CFOs will challenge your architecture choices because they're not sure they trust you. You have to be willing to push back without making enemies. Engineers who've only worked in friendly tech-company environments have not been calibrated for this.

4. They have a strong opinion on at least one tool and a weak opinion on five.

The strong opinion shows depth. The weak opinions on five show breadth + willingness to adapt to customer constraints. Engineers who have strong opinions on everything ("we have to use Kafka") become PRs that miss the point. Engineers who have no opinions get steamrolled by customer engineers.

5. They optimize for the customer's quarter, not their own quarter.

This is the most senior trait. A 2-year FDE optimizes for the deal closing. A 5-year FDE optimizes for the renewal. A 10-year FDE optimizes for the customer's quarterly board update.

Anthropic FDEs trained at Palantir understand this implicitly. Anthropic FDEs hired straight from product engineering roles often don't, and the deals are visibly weaker.

The full screening rubric, the take-home prompt we use at FDEOS for Silver-tier verification, and the five questions in the reference call that predict success — below.