A hybrid engineering role invented by Palantir in the 2010s and scaled up aggressively by OpenAI, Anthropic, and Scale AI starting in 2024 — not HQ model engineers, not pre-sales engineers. FDEs embed directly with customer teams on-site and turn foundation model APIs into production code running inside the customer's real business. OpenAI FDE postings list base $270K–$385K + equity (total comp easily $500K+); Anthropic Forward Deployed Engineer base $340K–$485K; senior Palantir FDEs regularly clear $400K total comp. The core skill isn't 'prompt tuning' — it's 'sit in a customer meeting, hear the problem, and ship a production-grade demo in two weeks.' Full-stack engineering + rapid prototyping + business intuition + extreme ambiguity tolerance + 25-40% travel. Ex-Palantir FDEs currently occupy most of the engineering leadership at OpenAI, Anthropic, Cohere, and Databricks.
Real bootcamps currently running on jiangren.com.au — click through for the full outline and enrollment
Tap one answer per requirement: I have it, not yet, or not sure. Your first gap view appears below straight away. No sign-in needed; until you save, your answers stay on this page and clear when you refresh.
Answer one requirement and this panel lists what is missing and which transition step on this page covers it.
This view comes only from your own answers. Add material and the evidence level goes up:
Evidence becomes: from your resume
Evidence becomes: resume × job ad
Evidence becomes: measured
Hands-on work and projects happen in the CareerOS desktop app.About CareerOS desktop
Treating FDE as 'an engineer who does PPTs' or 'a sales engineer who writes code'
FDE is about production delivery — not demos, but code running inside the customer's real business. The success metric is 'does the customer keep using it next month'
Assuming strong engineering is enough and ignoring customer communication and business language
FDE interviews include a dedicated 'customer role-play' round — strong engineers who can't listen for pain points or explain ROI simply don't get through
Refusing travel and demanding fully remote
On-site work is where an FDE's value is created — conversations and trust built in the meeting room can't be replicated remotely. Fully remote FDE roles don't exist
Waiting for the customer to hand over clear requirements when facing ambiguity
'The customer doesn't know what they want either' is the FDE default — your job is to help them figure it out with prototypes and data, not wait for a spec document
Shipping throwaway demo code as the production deliverable
FDE must know when to be in hack mode vs production mode — 'the demo runs' is not 'the customer can maintain it'; confusing the two creates customer complaints three months later
Only looking at HQ's Model / Product roadmap for answers
FDEs constantly push reverse requirements back to HQ — you're closer to the real customer than anyone at HQ, and you owe them the ground truth
Start learning the core skills for Forward Deployment Engineer
Start Learning →