Last updated October 2026.
A year ago most engineers had never heard the title "forward deployed engineer." Now it's posted by AI labs, enterprise software companies, and consulting firms alike. The descriptions are vague, and plenty of people wonder whether it's real engineering or sales with a new label.
It's usually real engineering. This guide covers what the job is, why demand took off, how it differs from nearby jobs, and what to change on your resume to get one.
What a Forward Deployed Engineer Actually Does
A forward deployed engineer (FDE) is a software engineer who works directly with a customer to get a product working inside that customer's real environment. Not a demo environment. The one with the legacy database, the strange auth setup, the compliance review, and the team that has been burned by three previous vendors.
The core loop is simple to describe and hard to do: sit with the customer, find the workflow that matters, write the code that connects the product to it, and keep going until it runs in production and people use it.
The role came from Palantir, which split customer-facing technical work into two tracks. "Delta" engineers wrote the code that adapted the platform to each customer. "Echo" staff focused on understanding the customer's mission and problems. The pattern spread from there.
In 2026 the title shows up wherever AI is sold into businesses. OpenAI, Anthropic, Salesforce, and Scale AI hire for it, along with many AI startups and consultancies. At an AI company, the FDE turns "the model can do this" into "the model does this, every day, inside our claims process."
Why Demand Exploded
The short version: AI pilots are easy to start and hard to finish. A proof of concept on clean sample data takes days. Getting the same thing running against real customer data, inside real security rules, wired into the tools people actually use, can take months. That last mile is where most enterprise AI projects stall, and it's exactly the gap an FDE is hired to close.
The numbers reflect it, with caveats worth reading:
- Indeed data, as reported by Business Insider, showed FDE postings up roughly 729% year over year, from 643 in April 2025 to 5,330 in April 2026 (Paraform's summary). That's one job board, so treat it as a direction rather than a census.
- Lightcast data reported by Fortune put postings up more than 1,000% for January–August 2026 versus the same months of 2025, with a median advertised salary above $188,000 (about $145,000 for a traditional software engineering role).
- Big employers are committing publicly. Salesforce said it would hire 1,000 FDEs, and EY launched dedicated FDE roles in April 2026 (Christian & Timbers).
- Growth is normalizing, not reversing. An analysis of about 1,000 FDE job posts found the number of open reqs still climbing while the year-over-year percentage settles down, which is what you'd expect once a role goes from novelty to standard.
Percentages that large mostly reflect a small starting base. The takeaway: the role is now common enough to target deliberately.
A Typical Week
No two FDE weeks look the same, but a representative one might go like this:
- Monday: On-site workshop with the customer's operations team to map how invoices really move through their systems, which is not what the process document says.
- Tuesday: Write the integration that pulls documents, runs an LLM extraction step, and writes results back to their ERP. Discover their API rate limits are far lower than documented.
- Wednesday: Build an evaluation set from 200 real documents with their analysts, because "it looks right" is not a launch criterion. Two fields are weak.
- Thursday: Fix those fields, debug a failure caused by a scanned PDF format nobody mentioned, and demo progress to the customer's VP.
- Friday: Travel home. Write up what the core product should handle itself and send it to the product team.
That Friday step matters: good FDE teams feed field lessons back into the product.
FDE vs Nearby Roles
| Role | Main job | Writes production code? | Measured on | Customer time |
|---|---|---|---|---|
| Forward deployed engineer | Make the product work in one customer's real environment | Yes, a lot | Live deployments, adoption, outcomes | High, often on-site |
| Solutions engineer | Design how the product fits a customer, support evaluations | Some, often prototypes | Technical wins, smooth onboarding | High |
| Sales engineer | Win deals with demos and technical answers | Rarely | Revenue, quota attainment | High, pre-sale |
| Software engineer | Build the core product for all customers | Yes | Shipped features, reliability | Low |
| Consultant | Advise on strategy and process, sometimes implement | Varies, often little | Billable delivery, client satisfaction | High |
Titles vary between companies, so read the duties, not the label. Some "solutions engineer" roles are FDE roles in practice, and some "FDE" roles are pre-sales.
Skills That Get You Hired
- Strong coding. Python and TypeScript come up most. You'll write real services, not slides.
- APIs and data plumbing. Auth flows, webhooks, ETL, messy schemas, rate limits, and the unglamorous work of moving data between systems reliably.
- LLM integration. Prompting, retrieval, tool calling, structured outputs, and knowing when a model is the wrong answer.
- Evals. Building test sets from real customer data and measuring quality, so you can tell the customer something better than "it seems to work."
- Debugging in production. Reading logs on someone else's infrastructure, often without full access.
- Customer communication. Explaining trade-offs to a VP and a database admin in the same afternoon.
- Scoping. Turning "we want AI for our support team" into a two-week deliverable with a clear definition of done.
- Travel tolerance. Many roles involve regular on-site time. Ask how much before you accept.
What It Pays
Compensation varies widely by company, level, and location, so be skeptical of any single quoted number. As a rough rule, FDE pay overlaps with software engineer pay at the same company, often with travel on top. At consultancies the structure may look more like consulting pay. Compare an offer against that company's engineering ladder, not against headlines.
Who Transitions Well
- Software engineers who like customers. The ones who volunteer for customer calls.
- Solutions engineers who code. Showing production code is what moves you over.
- Consultants who code, especially those who've shipped data or integration work.
- Startup generalists who did support, sales calls, and infrastructure in the same week.
How to Rewrite Your Resume for FDE Roles
Hiring managers scan for one thing first: have you shipped something that worked for a specific customer under real constraints? Lead with that, then show ambiguity and work with non-engineers.
Before and after examples:
- Before: "Built REST APIs for the payments service."
After: "Built the integration that connected a logistics customer's legacy billing system to our payments API, taking their first live invoices from zero to 4,000 a week." - Before: "Worked on LLM features."
After: "Shipped an LLM document-extraction pipeline for an insurance client, built a 300-case eval set with their analysts, and raised field accuracy enough to remove a manual review step." - Before: "Collaborated with cross-functional teams."
After: "Ran weekly working sessions with a client's ops and security teams to scope and deliver a two-week pilot that converted to a full rollout."
Use your own real numbers, and only claims you can talk through in detail. FDE interviewers will ask exactly how you did it. Also keep the format simple so it parses cleanly; our ATS-friendly resume format guide covers the basics.
The Interview Loop
Loops differ, but most include some mix of:
- Coding. Often practical rather than puzzle-heavy: parse this data, call this API, handle these failures.
- Decomposition or case. "A hospital wants to use our model to summarize discharge notes. Walk us through it." They're watching how you ask questions, scope, and handle risk.
- Customer role-play. An interviewer plays a skeptical or frustrated customer. Stay calm, ask clarifying questions, and don't overpromise.
- Take-home. A small integration or prototype, sometimes with a short write-up for a non-technical reader.
Prepare stories for the customer that pushed back, the deployment that broke, and the project where requirements changed halfway through.
Red Flags in FDE Postings
- Quota in the description. If you'll carry a sales target, it's a pre-sales role with an engineering title.
- 100% travel. Some travel is normal. Living out of hotels indefinitely is a different job.
- No mention of writing code. If the duties are demos, RFP answers, and "technical relationship management," it isn't an FDE role.
- No path back to product. Ask how field learnings reach the product team. If nobody can answer, expect to rebuild the same custom work for every customer.
Where ProfVault Fits
FDE hunting means applying across AI labs, startups, enterprise software companies, and consultancies, each on its own applicant tracking system. ProfVault keeps one structured profile and the free Chrome extension fills applications from it, including dropdowns and attaching your resume file, with no limit on the number of applications. For open questions like "Describe a time you worked directly with a customer," it can draft an AI answer from your profile on 10 applications a month for free. You review every field before you submit.
New accounts start with a 7-day Pro trial: unlimited AI answers in the extension and 5 AI credits for tailored resumes and cover letters. That's enough to tailor a resume for your top FDE targets, leading with the customer-shipped bullets above. Create a free account and pair it with a focused one-week job sprint.
FAQ
Is a forward deployed engineer a sales role?
Usually not. A real FDE role is mainly about writing and shipping code in customer environments. If the posting mentions quota or rarely mentions code, it's likely pre-sales with a new title.
Do I need AI or machine learning experience to become an FDE?
Not deep research experience. Most roles want strong general engineering plus practical LLM integration skills: calling models, retrieval, evals, and handling failures. You can build those with a few real projects.
How is an FDE different from a solutions engineer?
There's overlap, but FDEs typically write much more production code and stay through deployment, while solutions engineers often focus on design, evaluation, and onboarding. Read the duties rather than trusting the title.
Is the FDE trend going to last?
Nobody can promise that, but open roles are still growing as year-over-year percentages normalize. While companies struggle to get AI into production, people who can do it stay in demand.
Related reading
- The new AI job titles of 2026
- What AI companies look for when hiring in 2026
- The one-week job sprint: 50 applications, 10 truly tailored
- The best ATS-friendly resume format for 2026
Ready to stop retyping your resume into every job application? Install the ProfVault Chrome extension (free) and auto-fill any ATS in one click.