Forward Deployed Engineer Job Description Guide

By Rome Thorndike

A Forward Deployed Engineer job description is the posting you read before you apply, and it tells you more about the role than the title does. The same job goes out under at least four names (Forward Deployed Engineer, Forward Deployed Software Engineer, FDE, and sometimes Deployment Engineer or Applied Engineer), so the description is where you confirm whether the role is the customer-embedded engineering job you're looking for or a relabeled sales-engineering seat. This page breaks down what's actually in a typical FDE job description, section by section, so you can read one quickly and apply only to the roles that fit.

If you're a hiring manager writing one instead of reading one, the companion FDE job description template has a copy-and-paste version with the sections strong candidates expect. This page is written for the person on the other side of the posting: what each section means and what it signals.

The Five Sections Every FDE Job Description Has

FDE postings vary by company, but almost all of them follow the same five-part structure. Reading them in this order tells you whether to apply within about two minutes.

Role summary: One or two paragraphs on what the team does and where the FDE sits. Look for the phrase "embedded with customers" or "deploy our product at customer sites." If the summary is all about demos and pre-sales, the role is closer to sales engineering than FDE.
Responsibilities: What you'll actually do day to day. This is the section that separates a real FDE job from a relabeled one.
Requirements / qualifications: Years of experience, languages, and the must-have skills. Usually split into "required" and "nice to have."
Compensation and location: Base band (required by law in pay-transparency states), remote or on-site, and travel expectation.
About the company: Boilerplate, but it tells you the company stage, which drives equity and travel more than the role title does.

FDE Responsibilities: What the Job Actually Asks For

The responsibilities section is where FDE job descriptions are most consistent. Across the postings tracked on the FDE job board, the same five responsibilities show up again and again, usually phrased a little differently each time:

Build custom integrations and production code at customer sites. Phrased as "develop bespoke solutions," "build integrations between our platform and customer systems," or "write production code deployed in customer environments." This is the core of the job. If it's missing or soft, the role is not really an FDE seat.
Scope deployments with customer stakeholders. Phrased as "partner with customers to understand requirements," "translate business needs into technical solutions," or "own the technical scope of each engagement." This is the project-definition work that FDEs do that pure SWEs don't.
Serve as the technical point of contact. Phrased as "act as the trusted technical advisor," "lead technical discussions with customer engineering teams," or "be the bridge between our product and the customer." This is the customer-facing half of the role.
Feed product and customer insights back to the team. Phrased as "surface common customer needs to product," "influence the roadmap based on deployment learnings," or "contribute to internal tooling." FDEs are usually the first to spot when a one-off build is actually a generic feature.
Train and support customer teams. Phrased as "enable customer engineers to maintain the solution," "deliver technical training," or "ensure successful handoff." The deployment isn't done until the customer can run it without you.

A useful test: count how many responsibility bullets are about writing code versus running meetings. A genuine FDE description is roughly half and half. If it's 80 percent meetings, the title is FDE but the job is customer success or technical account management. The what is an FDE job guide walks through the day-to-day split in more detail.

FDE Requirements: The Must-Haves and the Nice-to-Haves

The requirements section is where you self-screen. FDE job descriptions are unusually honest about the dual skill demand, so read both halves carefully.

Experience. Most FDE descriptions ask for 3 to 7 years of software engineering experience. New-grad and associate FDE postings exist (Palantir's FDSE track and Salesforce's FDE I are the main ones), but they're a small slice of the market. If a description asks for "5+ years" and you have two, the realistic move is the associate-level postings, not the senior ones.

Languages and tools. Python and SQL appear in the large majority of FDE descriptions. REST API design, Git, and at least one cloud platform (AWS, GCP, or Azure) show up in most. Docker and Kubernetes appear in roughly half. Since 2024, LLM-specific requirements (RAG, vector databases, prompt engineering, model evaluation) have started appearing in AI-company FDE descriptions where they didn't exist before.

Customer-facing ability. This is the requirement that filters most applicants, and it's almost never optional. Phrased as "excellent written and verbal communication," "comfort working directly with customer stakeholders," or "ability to explain technical concepts to non-technical audiences." A description that lists this as required and means it will test it in the interview with a customer-scenario round.

Nice-to-haves. The optional section usually lists domain knowledge (healthcare, fintech, government), specific platform experience (Salesforce, Databricks), or consulting background. Treat these as tiebreakers, not gates. The required section is what you actually have to clear.

Reading Between the Lines

A few phrases in an FDE job description tell you more than the formal sections do:

"Up to 50% travel" or "willingness to travel": Common at Palantir and enterprise-SaaS FDE roles, especially government and healthcare. AI-lab FDE roles are more often remote-friendly. If travel matters to you, this line is the one to find first.
"First FDE hire" or "help build the function": Signals a company standing up its FDE team. More scope and influence, less structure and mentorship. Good for senior engineers, harder for early-career ones.
"On-call" or "production support": Means the deployments you build, you also keep running. Factor it into the role's real workload.
A base band with a wide spread (for example, $150,000 to $290,000): Usually means the posting covers multiple levels. Your offer lands where your experience puts you, not at the midpoint.

What FDE Job Descriptions Pay

Most FDE job descriptions in pay-transparency states (California, Colorado, New York, Washington, and others) list a base salary band. Across the postings tracked here, the typical disclosed band runs $135,000 to $215,000, with a midpoint near $180,000. Senior and staff FDE descriptions at Google Cloud, OpenAI, and Salesforce push base past $300,000, and equity at AI labs and pre-IPO startups adds materially on top. New-grad and associate FDE descriptions start lower, $130,000 to $165,000 base at the established programs. The full breakdown by employer and seniority is on the FDE salary page.

One thing to note when comparing job descriptions: a band is a range, not an offer. A description listing $160,000 to $260,000 covers everyone from a mid-level FDE to a staff FDE. Where you land depends on your level, your metro, and how you negotiate, not on the average of the two numbers.

How to Use the Description When You Apply

The fastest way to tailor an application is to mirror the responsibilities section back in your resume. If the description leads with "build custom integrations," your top resume bullet should be an integration you shipped, named with the technologies and the customer outcome. If it leads with "act as the technical point of contact," lead with a customer-facing project. The FDE resume guide covers how to do this without rewriting your whole resume for every posting.

The other use of the description is interview prep. The customer-scenario round, which most FDE interviews include, is built directly from the responsibilities you just read. If a description emphasizes scoping ambiguous customer requirements, expect an interview question that drops you into a vague customer ask and watches how you narrow it. The FDE interview questions guide maps the interview rounds back to the job description sections.

Frequently Asked Questions

What is in a Forward Deployed Engineer job description?

A typical FDE job description has five sections: a role summary (where the FDE sits and what the team does), responsibilities (building custom integrations, scoping deployments, serving as the technical point of contact, feeding insights back to product, training customer teams), requirements (usually 3 to 7 years of software engineering experience plus Python, SQL, and customer-facing communication), compensation and location, and company boilerplate. The responsibilities section is the one that separates a real FDE role from a relabeled sales-engineering or customer-success seat.

What are the main responsibilities of a Forward Deployed Engineer?

The five responsibilities that appear in almost every FDE job description are: build custom integrations and production code at customer sites, scope deployments with customer stakeholders, serve as the technical point of contact for the customer's engineering team, feed product and customer insights back to the internal team, and train customer teams to maintain the solution. A genuine FDE description is roughly half coding work and half customer-facing work.

What requirements do FDE job descriptions ask for?

Most FDE job descriptions require 3 to 7 years of software engineering experience, fluency in Python and SQL, REST API design, Git, and at least one cloud platform. Customer-facing communication is almost always a required (not optional) skill and is tested in the interview. Since 2024, AI-company FDE descriptions have added LLM requirements like RAG, vector databases, and model evaluation. New-grad FDE roles at Palantir FDSE and Salesforce FDE I are the main exceptions to the experience requirement.

How is an FDE job description different from a sales engineer description?

An FDE job description centers on writing production code that ships in customer environments, with roughly half the responsibilities about building and half about customer interaction. A sales engineer description centers on pre-sales support, demos, and proofs of concept, with little or no production code. If a posting titled FDE has a responsibilities section that's mostly demos and meetings, it's closer to sales engineering than forward deployed engineering.

How much do FDE job descriptions pay?

FDE job descriptions in pay-transparency states list a base band that typically runs $135,000 to $215,000, with a midpoint near $180,000. Senior and staff FDE descriptions at Google Cloud, OpenAI, and Salesforce push base past $300,000, and equity at AI labs and pre-IPO startups adds materially on top. A listed band is a range covering multiple levels, not a single offer; where you land depends on your level, metro, and negotiation.