FDE job description template (2026)
Most FDE job descriptions fail because they are copied from a SWE req and lightly edited. The result: a JD that attracts SWEs who want the salary premium without the customer-facing reality, and filters out actual FDE candidates who can immediately tell the description doesn't reflect genuine understanding of the role. This template gives you a working baseline — role summary, responsibilities, qualifications, and comp bands sourced from how Palantir, OpenAI, Anthropic, and Scale AI actually write FDE JDs.
Why most FDE JDs fail
Three failure modes appear repeatedly in FDE job descriptions that don't produce quality applicants:
SWE-with-customer-bullet framing. The JD describes a standard SWE role — coding, design, deployment — and adds "works with customers" as a bullet at the bottom. This selects for SWEs who want a salary premium, not FDEs who can hold a customer relationship. Strong FDE candidates see through this framing immediately and skip the apply. The ones who do apply are usually engineers who failed to land the SWE role they actually wanted.
Solutions-Engineer-renamed framing. The JD describes pre-sales work — demos, proof-of-concept builds, technical objection handling — and calls it "Forward Deployed Engineer" because that sounds more technical. This selects for Solutions Engineers or pre-sales people who do not ship production code. The FDE role is fundamentally different: FDEs own post-sales deployment, write production integration code, and stay with the account through go-live and expansion. If your bottleneck is winning deals, hire an SE and call it an SE. If your bottleneck is deploying at accounts you've already won, hire an FDE and write a JD that reflects that scope.
Vague-AI-engineer framing. The JD lists "AI," "machine learning," "LLMs," and "customer-facing" without specifying what the person will actually build. This selects for nobody — strong candidates self-select out because they can't evaluate whether the role fits their skill stack. Be specific: "You will deploy our LLM platform at regulated financial institutions, writing Python integration code that runs inside customer VPCs, and own the technical relationship through the expansion cycle." That sentence selects for FDE-shaped candidates and filters out everyone else.
The job description template
Job Title
Forward Deployed Engineer (also: Senior Forward Deployed Engineer, Forward Deployed Software Engineer, Lead Forward Deployed Engineer)
Reports To
VP Engineering, Head of Customer Success Engineering, or CTO (varies by company structure)
Role Summary
We are looking for a Forward Deployed Engineer to own the technical deployment of our [product] at [customer segment — e.g., regulated financial institutions / federal defense agencies / mid-market healthcare systems]. You will write production integration code deployed inside customer environments, scope technical requirements with customer stakeholders, and own the relationship from contract through go-live and post-deploy expansion. This is not a pre-sales role — your work begins after the deal is signed.
You will be the technical point of contact for [1–3] anchor customers, building the repeatable deployment playbook as you go. Expect to spend [percentage, e.g., 30%] of your time on-site at customer locations. The role requires genuine engineering depth — you will write and deploy production code — and genuine customer accountability — you will hold the technical relationship without escalation theater.
Key Responsibilities
- Own end-to-end deployment of [product] at assigned customer accounts, from kickoff through production go-live
- Write custom integration code (Python, TypeScript, SQL) that runs inside customer infrastructure
- Scope technical requirements with customer engineering and business stakeholders, translating ambiguous needs into concrete implementation plans
- Conduct on-site technical workshops and deployment sessions at customer locations
- Debug production issues in customer environments under time-sensitive delivery constraints
- Build and maintain customer-specific deployment documentation, runbooks, and troubleshooting guides
- Identify and drive post-deploy expansion opportunities based on customer usage patterns and technical feedback
- Represent customer technical requirements internally, influencing product roadmap and engineering priorities
- Document repeatable deployment patterns and contribute to the internal FDE playbook
- Train junior FDEs on deployment best practices and customer engagement patterns as the function scales
- Participate in customer-escalation on-call rotation for production-critical accounts
- Collaborate with Solutions Engineers during the handoff from pre-sales to post-sales
Required Qualifications
- 4–7 years of production software engineering experience (backend, full-stack, or data engineering)
- Proven track record of writing and deploying production code in external customer environments (agency work, consulting, technical founder experience, or previous FDE/customer engineering roles)
- Strong proficiency in [specific languages relevant to your stack, e.g., Python and TypeScript]
- Experience with [specific deployment infrastructure, e.g., AWS/GCP, Docker, Kubernetes, CI/CD pipelines]
- Demonstrated ability to scope ambiguous technical requirements with non-technical stakeholders and translate them into working software
- Willingness to travel [specific percentage, e.g., up to 30%] for on-site customer deployments
Preferred Qualifications
- Experience deploying LLM or AI/ML systems in production (LangChain, LlamaIndex, Model Context Protocol, vendor SDKs)
- Domain expertise in [your customer vertical, e.g., healthcare, finance, government, defense]
- Familiarity with regulated or air-gapped deployment environments (SOC 2, HIPAA, FedRAMP, DoD IL4+)
- Track record of owning a customer relationship end-to-end in a technical capacity
- Experience working with columnar data formats (Parquet, DuckDB) and SQL query optimization
- Contributions to open-source projects in data integration, LLM tooling, or developer infrastructure
- Previous experience as a technical founder, agency engineer, or in a consulting role where you wrote production code
Compensation and Benefits
Base salary range: $[low]–$[high] (adjust for seniority, geography, and company stage)
Reference bands from employer-published data:
- OpenAI: $185,000–$325,000 base (Forward Deployed Software Engineer, San Francisco)
- Palantir, Anthropic, Scale AI: Total comp (base + equity + bonus) $250,000–$550,000 at IC5–IC6 (sourced from Levels.fyi self-reported data)
- Early-stage companies: $120,000–$160,000 base, offset with equity and autonomy
Full breakdown at the FDE salary guide (2026).
Additional benefits: [List equity, health insurance, 401(k), travel stipend, home office budget, professional development, on-call compensation, etc.]
Equal Opportunity
[Your company] is an equal opportunity employer. We do not discriminate on the basis of race, religion, color, national origin, gender, sexual orientation, age, marital status, veteran status, or disability status. We are committed to building a diverse and inclusive team.
How to adapt the template by company stage
AI Lab (Anthropic / OpenAI / Mistral shape)
Context: First FDEs, building playbook from scratch
Adapt: Emphasize "you will define the FDE function" and "build the repeatable deployment model." Highlight equity, autonomy, and the opportunity to shape what the role looks like. De-emphasize process maturity — candidates who need a well-defined playbook will self-select out.
Comp: Competitive with FAANG senior engineer bands. Offset slightly lower base with meaningful equity.
Growth-Stage AI-Native (Series C/D)
Context: Recurring deployment cadence, playbook exists but evolving
Adapt: Emphasize "you will own [X] anchor accounts using our existing deployment playbook, and improve the playbook based on what you learn." Candidates want to know there is a baseline to start from and room to grow the function.
Comp: Match or slightly exceed Palantir / Scale AI bands for equivalent seniority.
Enterprise AI Platform (Palantir shape)
Context: Mature FDE function, dozens of FDEs, formal playbook
Adapt: Emphasize scale, process maturity, and specialization opportunities. "You will join a 50+ person FDE organization with dedicated playbooks for [government / healthcare / finance], mentorship from senior FDEs, and clear IC→lead→principal career paths." Candidates value structure, not ambiguity.
Comp: Benchmark directly against Palantir FDSE comp. Publish total comp ranges, not just base.
What good looks like — evaluation rubric
Use these five dimensions to evaluate whether a candidate's background maps to the JD requirements:
| Dimension | What Good Looks Like |
|---|---|
| Production code in customer environments | Resume shows deployed code that runs in external environments (consulting projects, agency work, founder experience, previous FDE roles). Not just "worked on a team that deployed X" — they personally wrote and shipped it. |
| Ambiguous scoping | Can describe a time they received an under-specified customer requirement and turned it into a working technical spec without escalating to a manager every step. Bonus: they pushed back on the customer when the request was technically infeasible and proposed an alternative. |
| FDE vs SE distinction | Understands that FDE is post-sales deployment, not pre-sales demos. If asked "what's the difference between FDE and Solutions Engineer?", they can articulate it clearly. Candidates who conflate the two will underperform in either role. |
| Customer relationship ownership | Owned a customer account directly — not "supported the account team" but "was the technical point of contact, ran the deployment calls, made the technical decisions." Look for first-person language in the resume: "I deployed," "I scoped," not "the team deployed." |
| Post-deploy expansion | Can describe a deployment where they identified and drove an expansion opportunity after go-live. Expansion doesn't mean upselling — it means the customer started using the product in a new way based on the FDE's technical recommendation, and that required additional integration work the FDE led. |
Where to post the FDE job description
The most productive channels for FDE hiring are different from standard SWE hiring. Start with the dedicated FDE job board, then layer in FDE-specific sourcing channels.
FDE Jobs List. Post the role here first — this is the dedicated job board for Forward Deployed Engineer roles, where active FDE candidates are already self-selected. Posting here reaches candidates who are specifically looking for FDE work rather than general SWE roles, and the application quality is materially higher than generic job boards.
Palantir alumni networks. A disproportionate share of the FDE market passed through Palantir's Forward Deployed Software Engineer program. Search LinkedIn for "Forward Deployed" + "Palantir" in previous experience, and post in Palantir alumni Slack channels or mailing lists if you have access.
LangChain / LlamaIndex / MCP contributor pools. Engineers contributing to LangChain, LlamaIndex, Model Context Protocol servers, and similar open-source LLM tooling are doing work structurally identical to FDE daily work. Search GitHub contributors and post in their Discord / Slack communities.
Conference circuits. AWS re:Invent, OpenAI DevDay, Snowflake Summit, and similar enterprise AI / developer experience events are where FDE candidates actually spend time. Speaking at these events or running a booth outperforms generic LinkedIn outreach by a wide margin.
Related resources
- How to hire a Forward Deployed Engineer — when to open the role, interview loop design, sourcing channels, and common hiring mistakes
- FDE salary guide (2026) — employer-published comp bands from live ATS data
- FDE interview questions (2026) — representative questions with reference answers for both sides of the loop
- What is a Forward Deployed Engineer? — role definition, day-to-day, and how it compares to adjacent roles
- FDE vs Solutions Engineer — pre-sales vs post-sales: where the roles diverge
- FDE vs Applied AI Engineer — external deployment vs internal model work
Frequently asked questions
Should the JD require a CS degree?
No. Most strong FDE candidates come from non-traditional backgrounds — agency engineers, technical founders, consultants who learned to code, bootcamp grads with 5 years of production work. The signal is a pattern of shipping code and holding a customer relationship simultaneously, not a specific credential. A JD that requires a CS degree will filter out half the proven FDE population. If you want a filter, require production code portfolios or deployed integrations instead.
How many years of experience should we require for our first FDE?
The first FDE hire should be mid-senior: 4–7 years of production engineering experience. FDEs operate in customer environments where they are often the only engineer in the room, making real-time technical decisions without a manager nearby. An FDE who needs hand-holding on software design is a liability in front of a customer's VP of Engineering. Your first hire shapes what the function looks like internally; hire senior enough that they can define the playbook, not just follow it.
What level of customer-facing experience should we ask for in the JD?
Require concrete signals, not vague phrases. "Customer-facing experience" is too generic and appears in 90% of JDs that don't actually need it. Instead, require: "owned a client relationship from contract through deployment," "ran a production deployment at a customer site," or "worked in a consulting, agency, or technical advisory role where you wrote production code." These phrases select for candidates who have done FDE-shaped work, even if they didn't hold the FDE title.
Should we require travel willingness in the JD?
Yes, and be explicit about the percentage. "Up to 30% travel for on-site customer deployments" is specific and filters at the right stage. "Occasional travel may be required" is vague and delays the conversation until the offer stage, where a travel mismatch becomes expensive. If your deployment model requires on-site work, state the expected travel load explicitly. Candidates who can't do it will self-select out; candidates who can will appreciate the transparency.
What is the most common JD mistake we see?
Listing it as a SWE JD with "customer-facing" added at the bottom. The page should select for the FDE skill stack from line one, not describe a conventional SWE role with customer work as an afterthought. Start with the customer segment ("deploy our LLM platform at regulated financial institutions"), the deployment model, and the integration scope. Candidates who want that work will apply. Candidates who want a standard SWE role will not. That filter is worth more than any screen you add to the loop later.
Should we list comp in the FDE JD?
Yes. Palantir publishes compensation via recruiter conversations, OpenAI publishes salary bands in their ATS, and candidates benchmark against both. Listing a competitive range drives applications; missing it suppresses them. FDE talent is acutely competitive, and candidates who don't see comp will assume you are underpricing the role and skip the apply. If your range is legitimately lower than the market — which is fine for early-stage companies — acknowledge it explicitly and compensate with equity, scope, or autonomy. Silence on comp reads as a red flag.
What technical stack should we list as required?
Be specific to your deployment model. Generic bullets like "Python, TypeScript, SQL" do not filter — those appear in every SWE JD. Name the integration surface ("experience deploying Python services in enterprise customer environments"), the customer infrastructure ("familiarity with AWS GovCloud, air-gapped networks, or SOC 2-compliant deployments"), and the deployment model ("containerized applications via Docker and Kubernetes"). These details signal that you understand what the FDE will actually build and attract candidates with the relevant experience.
Should we differentiate JDs for IC vs lead FDE roles?
Yes. An IC FDE owns one or two accounts end-to-end: the technical deployment, the customer relationship, and the post-deploy expansion. A lead FDE owns the playbook, mentors junior FDEs, represents the function to exec leadership, and shapes what the FDE role looks like at the company. The required experience, the compensation band, and the reporting structure are all different. If you are hiring your first FDE and expect them to grow into a lead role, say that explicitly in the JD — many strong candidates value that trajectory and will self-select in.
Ready to post the role?
Post your FDE job description on FDE Jobs List to reach active Forward Deployed Engineer candidates.
How to hire a Forward Deployed Engineer · FDE salary guide (2026) · FDE interview questions (2026)