A forward deployed engineer (FDE) is a software engineer who works directly inside a customer’s environment to build, integrate and ship the custom code that makes a product work for that customer, then feeds what they learn back to the product team.
Below is a copy-ready forward deployed engineer job description template you can paste into your ATS, plus three variants (AI/LLM, industrial and energy, and cleared government work), posted pay from 60 live US job ads, and an interview scorecard.
We pulled every pay figure on this page from public job postings and primary sources in November 2026, so you can set a range that candidates will take seriously.
Key takeaways
- Across 60 US forward deployed engineer postings that listed pay (October 20 to November 17, 2026), the median posted range was $150,000 to $215,000 in base salary, with a median midpoint of $185,000.
- That midpoint is about 36% above the May 2025 BLS median for all software developers ($135,980). Budget for an FDE as a senior hire, not a standard developer.
- Indeed counted 5,330 FDE postings in April 2026, up from 643 a year earlier, according to Indeed data reported by Business Insider. Demand has moved well beyond AI labs into manufacturing, energy, airlines, insurance and retail.
- The biggest JD mistake is hiding travel and customer time. State the split (for example, 40% customer-facing, 60% building) and the travel range in the first screen of the posting.
- Screen for three things together: production-grade coding, the ability to scope a messy customer problem, and clear communication with non-engineers. Most candidates have two of the three.
What does a forward deployed engineer do?
A forward deployed engineer is the engineer you send to a customer when your product cannot deliver value on its own. They sit with the customer’s team, map the real problem, write production code, connect the product to the customer’s data and systems, and stay until the deployment works in production. Palantir made the title famous. AI companies made it one of the fastest-growing jobs in tech, because a model or platform that demos well still has to be wired into each customer’s data, security rules and workflows before anyone sees a return.
In a typical week an FDE splits time between customer discovery calls and workshops, hands-on building (integrations, data pipelines, agents, internal tools), debugging in the customer’s environment, and writing up what the core product should absorb so the next customer does not need custom work. That last part is what separates an FDE from a consultant: the job exists partly to make itself smaller over time.
| Part of the job | What it looks like | What to say in the JD |
|---|---|---|
| Discovery | Running working sessions with operators, managers and IT to find the problem worth solving | “Lead discovery with customer stakeholders and turn vague goals into a scoped build plan” |
| Building | Writing production code: APIs, integrations, data pipelines, AI agents and workflows, internal tools | “Write and ship production code in Python and TypeScript (or your stack) against real customer data” |
| Deploying | Getting it running inside the customer’s cloud, network and security rules | “Deploy into customer environments (AWS, Azure, GCP or on-prem) and own reliability through go-live” |
| Feedback loop | Turning repeat customer needs into product requests and reusable components | “Partner with product and core engineering to turn field patterns into product features” |
| Commercial support | Joining late-stage sales calls, scoping pilots, defending timelines | “Support pre-sales scoping and pilot design with the account team” |
Forward deployed engineer job description template
Copy this into your ATS and replace everything in [brackets]. It is written to be posted as-is: short enough to read on a phone, with the pay range, travel and customer time up front, since those are the three things FDE candidates check first.
Forward Deployed Engineer
Location: [City, State] / [Hybrid / Remote, US] | Travel: [10–30%] to customer sites | Pay: $[150,000]–$[215,000] base + [bonus / equity] | Type: Full-time
About the role
[Company] builds [one-line product description]. As a Forward Deployed Engineer, you will work directly with our customers to turn [product] into working, production systems inside their business. You will spend about [40]% of your time with customers, scoping problems and running working sessions, and about [60]% building, writing code, integrating systems and getting deployments live. What you learn in the field will shape our core product.
What you will do
- Lead discovery with customer stakeholders, from operators to executives, and turn loose goals into a scoped plan with clear success measures
- Design, build and ship production code (integrations, data pipelines, APIs, AI workflows and internal tools) on top of [product]
- Connect [product] to customer systems such as [ERP, CRM, data warehouse, MES, SCADA, EHR] and handle authentication, data mapping and edge cases
- Deploy into customer environments on [AWS / Azure / GCP / on-prem] and own reliability, monitoring and fixes through go-live
- Travel to customer sites [about X days per month] for workshops, rollouts and critical launches
- Write clear documentation and train customer teams so they can run what you built
- Spot patterns across customers and work with product and core engineering to turn one-off builds into product features
- Support the account team on technical scoping for new pilots and expansions
What you bring
- [3+] years of professional software engineering experience shipping production code
- Strong [Python] and at least one of [TypeScript, Java, Go]; solid SQL
- Experience building integrations with REST/GraphQL APIs and working with messy, real-world data
- Hands-on experience with [AWS / Azure / GCP], containers and CI/CD
- A track record of working directly with customers or internal business users and explaining technical trade-offs in plain language
- Comfort owning ambiguous problems end to end with little structure
- Ability to travel [X%] and, if required, obtain [background check / customer site access]
Nice to have
- Experience with [LLM APIs, retrieval (RAG), agent frameworks, evaluation]
- Prior work as a forward deployed, solutions, implementation or founding engineer
- Domain knowledge in [industry: manufacturing, energy, healthcare, finance, logistics]
- Front-end experience (React) for building customer-facing tools quickly
What success looks like
- First 30 days: Ship a working fix or feature for an existing customer and complete product training
- First 90 days: Own one customer deployment from discovery to production
- First 12 months: Lead multiple deployments and get at least one field-built component adopted into the core product
Pay and benefits
The base pay range for this role is $[X]–$[Y], plus [bonus target / equity]. Final pay depends on experience, skills and location. Benefits include [health, dental, vision, 401(k) match, PTO, travel policy].
[Company] is an equal opportunity employer. [Add your standard EEO and accommodation statement.]
Before you post: check that your range is legal in every state where the job can be done. Colorado, California, Washington, New York, Illinois and several other states require a good-faith pay range in postings, and a remote US role usually falls under those rules.
Template variants: swap these lines for your type of FDE
“Forward deployed engineer” now covers several different jobs. Pick the variant closest to yours and replace the matching sections in the template above.
1. AI / LLM forward deployed engineer
Common at AI labs, AI startups and enterprise software companies adding AI features. Replace the “What you will do” bullets 2 and 3 with:
- Build and ship LLM-powered applications and agents for customers, including prompt design, retrieval (RAG), tool calling and guardrails
- Create evaluation sets with customers, measure quality, cost and latency, and iterate until the system meets agreed thresholds
- Integrate models with customer data sources and permissions so answers are accurate and access rules are respected
Add to “What you bring”: hands-on work with at least one major model API, an evaluation framework, and vector or hybrid search. Postings in this group ran highest in our sample, with a median posted midpoint of about $200,000.
2. Industrial, manufacturing and energy FDE
Growing fast at manufacturers, utilities, grid operators, oil and gas companies and industrial software vendors. These roles pair software skills with plant or field systems. Replace the integration bullet with:
- Integrate [product] with plant and field systems such as PLC/SCADA historians, MES, CMMS, ERP and IoT sensor data, working with controls and IT/OT security teams
- Spend time on site at plants, substations or facilities, following site safety rules and lockout/tagout procedures
- Turn operator and engineer feedback into tools that cut downtime, scrap or manual reporting
Add to “What you bring”: exposure to OT data (OPC UA, MQTT, historians), comfort on a plant floor, and an engineering degree if your customers expect one. If you need someone who can also read ladder logic, look at candidates coming out of controls engineering and automation integrators.
3. Cleared / government FDE
Defense, intelligence and federal civilian programs. Add a line to the header: Clearance: [Active TS/SCI required / Secret, able to obtain]. Then add:
- Deploy and support [product] in accredited environments (IL5/IL6, classified networks or air-gapped systems)
- Work on site with mission users at [base / agency location] [X days per week]
- Follow program security, change control and documentation requirements
US citizenship is usually required for these roles, and the clearance requirement shrinks the pool sharply. In our sample, a TS/SCI FDE role in Tampa posted $110,000 to $170,000, below the overall median, so cleared employers competing with commercial AI companies often need to move pay up or offer clearance sponsorship.
Senior, staff and lead FDE
For senior roles, raise the experience bar to 6+ years, add “lead deployments for our largest or most complex customers,” “mentor other FDEs,” and “set reusable patterns and tooling for the FDE team.” In our sample, senior, staff, principal and lead FDE postings had a median posted range of $152,000 to $282,000.
Forward deployed engineer salary: what range to post
We collected 60 US forward deployed engineer postings with a stated annual pay range, posted between October 20 and November 17, 2026, from employer job boards, Indeed and Glassdoor. We grouped them by level using the job title and removed duplicate listings. Ranges are posted base pay, not total compensation, so equity and bonus are on top.
| Level | Postings | Median posted low | Median posted high | Median midpoint |
|---|---|---|---|---|
| Entry / junior / early career | 4 | $87,500 | $144,250 | $114,500 |
| Mid-level (title: Forward Deployed Engineer) | 48 | $150,000 | $215,000 | $182,500 |
| Senior / staff / principal / lead | 8 | $152,000 | $282,400 | $221,225 |
| All postings | 60 | $150,000 | $215,000 | $185,000 |
Total compensation runs higher than posted base. Self-reported data on Levels.fyi puts the median US forward deployed engineer total compensation (base plus stock plus bonus) at $225,000, with the 25th percentile at $170,000, the 75th at $300,000 and the 90th at $361,000. Those packages lean toward large tech and AI companies that pay in equity. If you are a mid-sized company paying mostly cash, the posted-base table above is the better benchmark.
Location still matters. In our sample, the median posted midpoint was about $197,500 in California and $196,250 in New York, versus about $174,900 in Texas and $165,300 in Illinois. Texas had more paid FDE postings than any state outside New York and California, with openings in Dallas, Irving, Addison, Richardson, Houston, The Woodlands and San Antonio.
| If you are… | Post this base range | Why |
|---|---|---|
| An AI startup or AI lab competing for top FDEs | $180,000 – $250,000 + equity | Matches the AI-native postings in our sample; candidates compare you directly to the labs |
| A SaaS or enterprise software company | $155,000 – $220,000 + bonus/equity | Close to the software-company median midpoint of about $185,000 |
| A manufacturer, utility, insurer or other non-tech employer | $140,000 – $200,000 + bonus | Non-tech employers in our sample posted a median midpoint of about $165,600; go higher if the role is AI-heavy |
| A consulting or IT services firm | $130,000 – $190,000 | Consulting postings had the lowest median midpoint, about $159,000 |
| Hiring early-career FDEs | $95,000 – $145,000 | Entry-level postings clustered here; strong new grads with internships often get more |
For local benchmarks on the closest standard role, see our software developer salary pages for Dallas-Fort Worth, Houston, Austin and Atlanta, or run any role and city through the salary calculator. Plan to pay an FDE well above those figures.
Who is hiring forward deployed engineers right now
Indeed counted 643 forward deployed engineer postings in April 2025 and 5,330 in April 2026, according to Indeed data reported by Business Insider. Lightcast data reported by Fortune shows the same trend: FDE postings rose more than 1,000% in January through August 2026 compared with the same months of 2025, while overall tech postings grew 13%.
The bigger shift for hiring managers is who is posting. In our November 2026 sample, fewer than half of the paid FDE postings came from AI-native companies. The rest came from software companies and, increasingly, from employers you would not expect: a home appliance maker, an industrial distributor, a grid operator, an airline, an insurer, a retailer, an energy major, an electrical services contractor and a test equipment maker. That means you are competing for the same candidates as AI labs, whatever industry you are in.
If you hire in Texas or the Southeast, the competition is local too. Our sample included FDE openings in Dallas, Irving, Addison, Richardson, Houston, The Woodlands, San Antonio, Atlanta, Durham, Charleston, Tampa and Sarasota. Apollo recruits IT and software talent in many of these markets, including Dallas, Houston, Austin and Atlanta.
Forward deployed engineer vs. software engineer vs. solutions engineer
Many FDE postings fail because they are really a different job with a trendier title. Use this table to check that you are hiring the role you need.
| Forward deployed engineer | Software engineer | Solutions / sales engineer | Solutions architect | Implementation consultant | |
|---|---|---|---|---|---|
| Builds for | One customer at a time | All customers at once | Prospects during the sale | Customer designs across accounts | Customer configurations |
| Writes production code | Yes, daily | Yes, daily | Demos and prototypes | Sometimes | Rarely; mostly configuration |
| Customer time | High (often 25–50%) | Low | Very high | High | High |
| Owns go-live | Yes | No | No | Advises | Yes, for setup |
| Measured on | Working deployments, adoption, product feedback | Features shipped, quality | Deals closed, technical win rate | Architecture quality, account growth | On-time, on-budget rollouts |
| Travel | Moderate | Rare | Moderate to high | Moderate | Moderate to high |
If the person will mostly configure your product without writing code, call it an implementation or solutions role and pay accordingly. If they will build features for every customer from your office, hire a software developer. Use the FDE title only when the job truly combines both, because candidates will judge the role against FDE pay.
Required vs. preferred skills for an FDE job description
Keep the “required” list short. Every extra must-have shrinks a pool that is already small, and strong FDEs come from many backgrounds: startup engineers, former founders, consultants who code, and engineers who have done customer-facing integration work.
| Area | Required (typical) | Preferred |
|---|---|---|
| Coding | Production experience in Python or a typed language (TypeScript, Java, Go); SQL | Two or more languages; front-end (React) to build tools fast |
| Data and integration | REST APIs, auth (OAuth, SSO), data mapping and cleanup | ETL tools, data warehouses (Snowflake, Databricks, BigQuery), event streaming |
| Cloud and deployment | One major cloud, containers, CI/CD | Kubernetes, infrastructure as code, deploying into customer-managed or on-prem environments |
| AI (if relevant) | Has built and shipped something with an LLM API | RAG, agents, evaluation, fine-tuning, cost and latency tuning |
| Customer skills | Has worked directly with customers or business users and explained trade-offs clearly | Ran discovery workshops; supported sales; consulting background |
| Ownership | Owned a project end to end with little direction | Founder, early-stage or “first engineer” experience |
| Domain | Not required for most roles | Industry knowledge that matches your customers (manufacturing, energy, healthcare, finance, government) |
How to interview a forward deployed engineer
A standard coding loop misses half of this job. A good FDE process tests coding, problem scoping and customer communication, ideally in one realistic exercise. Here is a five-step process most teams can run in two weeks.
| Step | Who | What it tests | Length |
|---|---|---|---|
| 1. Recruiter screen | Recruiter | Pay range, travel, customer-time fit, work authorization or clearance | 20–30 min |
| 2. Hiring manager call | FDE lead | Past deployments: what they built, for whom, what broke, what they would change | 45 min |
| 3. Coding and integration exercise | Two engineers | Writing working code against a messy API or dataset, not puzzles | 60–90 min |
| 4. Customer case simulation | FDE + account lead acting as customer | Discovery questions, scoping, pushing back, explaining trade-offs | 60 min |
| 5. Product and values conversation | Product lead or exec | How they turn field work into product feedback; judgment under pressure | 45 min |
Forward deployed engineer interview questions
- Walk me through a deployment you owned from first customer meeting to production. What did the customer think they needed, and what did they actually need?
- Tell me about a time a customer asked for something your product could not do. What did you build, and what did you push back on?
- You have two weeks to show value at a new customer whose data is a mess. What do you do in the first three days?
- How do you decide whether to build a one-off fix for a customer or push for a product change?
- Explain a technical trade-off you made to a non-technical executive. How did you know they understood?
- Describe a time a deployment failed in production. How did you find the cause, and how did you communicate it?
- What part of customer-facing work drains you, and how do you handle it during a heavy travel month?
- For AI roles: how do you decide an LLM feature is good enough to put in front of a customer’s users?
For more general engineering questions to round out the loop, see our list of interview questions to ask software engineers.
FDE interview scorecard
Score each area from 1 to 4 after every interview. Hire when a candidate averages 3 or more and has no 1s. A 4 in coding cannot make up for a 1 in customer communication in this role.
| Area | 1: Concern | 2: Mixed | 3: Strong | 4: Exceptional |
|---|---|---|---|---|
| Production coding | Cannot finish working code | Works but fragile | Clean, tested, handles edge cases | Fast, clean and explains choices clearly |
| Problem scoping | Jumps to a solution | Asks some questions | Finds the real problem and success measure | Reframes the problem and narrows scope to quick value |
| Customer communication | Jargon-heavy or defensive | Clear with engineers only | Clear with technical and non-technical people | Builds trust fast; handles pushback well |
| Ownership and ambiguity | Waits for direction | Needs some structure | Drives work with little guidance | Has owned outcomes end to end repeatedly |
| Product feedback | Only thinks about the customer in front of them | Mentions patterns when asked | Turns field work into clear product input | Has shipped field work back into a core product |
Forward deployed engineer job description mistakes to avoid
- Hiding travel and customer time. Candidates who want a pure coding job will quit after their first heavy travel month. Put the percentage in the header.
- Leaving out pay. FDE candidates get a lot of recruiter outreach. Postings without a range get fewer qualified applicants and, in many states, break pay transparency laws.
- Posting a support or sales role with an FDE title. If the job does not involve writing production code, experienced FDEs will spot it in the interview and walk.
- A 20-item required list. Cut it to the five or six things you truly screen on. Move the rest to “nice to have.”
- No definition of success. Say what a good first 90 days looks like. It tells candidates the role is real and gives your interviewers a shared bar.
- Ignoring burnout. FDE work is intense. Say how you handle on-call, launches and travel recovery. It is a real selling point.
Need help hiring a forward deployed engineer?
Apollo Technical has recruited engineering and IT talent since 2010. We can help you find software engineers who have worked in customer-facing, integration and deployment roles, including candidates for industrial, energy and manufacturing FDE positions where software and plant systems meet. Talk to our team about your opening.
Forward deployed engineer job description FAQ
What is a forward deployed engineer job description?
A forward deployed engineer job description defines a software engineering role that works directly with customers to build, integrate and deploy custom solutions on a company’s product. It should list the customer-facing duties, the coding and deployment work, required skills, travel, the share of time spent with customers and a pay range.
What does FDE stand for?
FDE stands for forward deployed engineer. Some companies, including Palantir, use forward deployed software engineer (FDSE) for the same role.
How much should I pay a forward deployed engineer?
In 60 US postings with stated pay from October to November 2026, the median posted base range was $150,000 to $215,000, with a median midpoint of $185,000. Senior and staff FDE postings had a median range of $152,000 to $282,400. Equity and bonus are usually extra.
Is a forward deployed engineer the same as a solutions engineer?
No. A solutions or sales engineer mainly supports the sale with demos and prototypes. A forward deployed engineer writes production code after the sale and owns getting the deployment working in the customer’s environment.
Do forward deployed engineers write code?
Yes. Writing and shipping production code is the core of the job. FDEs build integrations, data pipelines, AI workflows and tools, then deploy and support them in the customer’s systems.
How much travel should a forward deployed engineer job include?
Most FDE postings list occasional to moderate travel, often 10% to 30%, with more during launches. State your expected range and customer time in the job description so candidates can judge the fit before they apply.
What qualifications should a forward deployed engineer have?
Most employers ask for several years of software engineering experience, strong Python or another production language, API and data integration skills, cloud experience, and a record of working directly with customers. AI-focused roles add LLM, retrieval and evaluation experience.
Methodology: We collected US job postings titled “forward deployed engineer” (and close variants such as forward deployed AI engineer) posted October 20 to November 17, 2026, from employer job boards, Indeed and Glassdoor. We kept the 60 unique postings that listed an annual pay range and excluded hourly and monthly contract rates. Level comes from the job title. Employer type was assigned by Apollo Technical. Median figures are medians of the posted low and high ends of each range.