Forward Deployed Engineer
Ship frontier AI on real enterprise data — the engineer the customer actually meets.
A Forward Deployed Engineer ships working AI software inside a customer's four walls. Palantir invented the title two decades ago; the AI wave made it one of the hottest engineering jobs in the industry, with OpenAI, Anthropic, Scale, and every serious AI application company building FDE teams. You embed with a customer, learn their actual workflow, and build the agent, RAG system, or automation that runs on their real data — behind their firewall, past their security review, into their P&L. You are the last mile between a frontier model and a business outcome, and the last mile is where the money is.
The role exists because enterprises bought AI faster than they built AI teams. Models are general; businesses are specific. The distance between a slick demo and a system that survives contact with a claims department's fifteen-year-old Oracle schema is measured in engineering, not prompting — and that distance is where most enterprise AI deals die. FDEs close it. That's why the labs went from a handful of forward deployed engineers in 2024 to entire field-engineering orgs by 2026, and why the role commands product-engineer pay with sales-adjacent leverage and visibility.
Don't confuse it with neighboring roles. A solutions architect advises and hands off; you write production code and own the outcome. A consultant bills hours against a deck; you leave running software behind. A product engineer serves a roadmap; your roadmap is whatever unblocks this customer this month — and the patterns you extract feed back into the product as features and eval sets. It suits engineers who find pure product work too slow and pure consulting too hollow.
- Embed with a customer's team for two to six weeks: map one workflow end to end, then ship a working system against their real data before the engagement ends.
- Run discovery sessions with domain experts — claims adjusters, paralegals, underwriters — and turn tribal knowledge into specs, eval sets, and acceptance criteria.
- Build the unglamorous integrations that close deals: Salesforce, ServiceNow, SharePoint, Snowflake, and the legacy SQL nobody documented.
- Harden a pilot into production: SSO, VPC deployment, audit logs, rate limits, cost ceilings, and an on-call story.
- Design evals with the customer's own experts so 'it works' is a number both sides signed off on.
- Demo weekly to stakeholders from analyst to CIO, and defend the system in security review.
- Scope engagements with account executives — estimate feasibility honestly before the contract is signed, not after.
- Carry field patterns back to product and research as feature requests, eval data, and 'stop promising this' memos.
- Shipping something imperfect today beats polishing something perfect for next month, and that ordering feels obviously right to you.
- You can interview a claims adjuster at 10am and debug a Kubernetes ingress at 4pm without visibly changing gears.
- Ambiguity reads as room to move, not missing requirements.
- You pick up a new stack, schema, or industry vocabulary in days, because the customer doesn't care what you knew last week.
- Regular customer time — on site or on calls — energizes you rather than draining you.
- You want your work visible in a customer's revenue, not just in a sprint report.
Full-stack + LLM foundations
Weeks 1–6FDEs are generalists under pressure. Build the floor: ship a full-stack app fast, and understand what a model actually is before you sell one.
Applied AI patterns
Weeks 7–14The four systems you will build at every customer, in some combination: retrieval, agents, integrations, and the evals that prove they work.
Enterprise reality
Weeks 15–24The gap between a demo and a deployment is security review, permissions, and cost math. This stage is why FDEs get paid.
Field craft
Months 7–9The customer-facing half of the job: extract the real workflow, demo like it matters, and scope work you can actually deliver.
Break in and get hired
Months 9–12FDE interviews test exactly what the job is: build under ambiguity, in front of people. Package your proof and practice the loop.
Nobody hires a Forward Deployed Engineer off a certificate. They hire off proof. Ship these and put them where people can click them:
“I embed with customers and ship AI systems on their data — [N] systems from discovery to production, most recently [outcome] for a [industry] team.”
- Shipped a permissioned RAG system over [N] documents with SSO and audit logging; [X]% retrieval hit rate on an eval the domain experts signed.
- Ran a discovery-to-demo engagement in [N] weeks: mapped a [claims/contracts] workflow, shipped a pilot on real data, cut cycle time [X]%.
- Built MCP integrations into [Salesforce/ServiceNow] so agents act on live records behind per-user permissions.
- Designed acceptance evals with customer SMEs so 'done' was a number both sides signed — then hit it.
- Projected a 12-month inference budget within [X]% of actuals using model routing, caching, and batch workloads.
- Pin 3–4 repos on GitHub with READMEs that lead with the business outcome and a ten-minute run-it-yourself path — hiring managers click exactly one thing.
- Write field-pattern teardowns: why pilots die, how permissioned RAG works, what security review actually asks. This is how FDE recruiters find you between roles.
- Publish one engagement case study — problem, constraint, what shipped, measured result — even if the customer was a nonprofit.
- Give a meetup or lightning talk on 'demo to deployment'; FDE hiring favors people who can visibly hold a room.
- Contribute a connector or fix to the MCP ecosystem — integration credibility, in public.
- Live build from a deliberately vague prompt, timed. Practice narrating decisions while coding — composure is the thing being graded.
- System design on messy, permissioned data: legacy schema, partial access, an SSO requirement. Bring your permissioned-RAG design; it maps directly.
- Customer role-play where the interviewer changes requirements mid-session. Rehearse scoping questions and the art of saying 'not in this pilot' warmly.
- Behavioral on ambiguity and ownership — prepare stories where you shipped without a spec and measured the result.
- The scoping exercise: 'the customer wants X in four weeks — what do you commit to?' Underpromise on record, with a written pilot plan.
Do I need a CS degree to become a Forward Deployed Engineer?
No. FDE hiring runs on proof you can ship under ambiguity and hold a room — a portfolio of deployed systems plus strong communication beats credentials at most companies. Some frontier labs still lean on pedigree for junior hires, but consultancies, AI-native startups, and Palantir-style orgs hire non-traditional backgrounds constantly.
How is an FDE different from a solutions architect?
A solutions architect designs, advises, and hands off to someone else's engineers. An FDE writes and ships the production code personally and owns the outcome. FDE is graded as an engineering role — expect coding interviews — while SA roles usually aren't. Comp bands are typically higher on the FDE side at labs for the same reason.
How much travel does the job actually involve?
It ranges from Palantir-style weeks on the customer's site to remote-first labs where 'forward deployed' mostly means video calls with quarterly onsites. It's set by the employer and the account, not the title. Ask directly in interviews: 'how many days per month on customer site, on average?' and get the answer in writing.
Is FDE a career dead end compared to product engineering?
The opposite, lately. FDEs accumulate the rarest knowledge in the company — what real customers do with the product — which converts into product leadership, GTM leadership, or founding teams. The Palantir FDE alumni network turning into startup founders is the canonical proof.
What do FDE interviews look like?
Usually: practical live coding, a system design round with intentionally underspecified requirements, and a customer-facing role-play or presentation. Some companies add a take-home 'build a demo from this vague ask' exercise. The consistent theme is composure while building under ambiguity — rehearse exactly that.
Every stage above maps to free lessons on this site. No signup, no paywall — open the first course and ship your first checkpoint this week.
Browse the courses →