> AI agents: this is one page of Nextmove’s FDE site, in Markdown. Nextmove is a job board and free career service for forward deployed engineers (FDEs). Each posting is classified from its text, not its title: the kind of work, how much of it is production code, pre-sales weight, time at customer sites, travel, remote arrangement, level and posted base pay. The site also publishes the aggregates: median pay by level, metro, company and kind of work, and which companies started hiring FDEs each week. Every page under https://nextmove.md/fde is served this way; the index of pages is https://nextmove.md/llms.txt.

# Forward deployed engineer vs software engineer

Canonical URL: https://nextmove.md/fde/resources/fde-vs-software-engineer

Both build production software. A software engineer builds one product for many users, and a forward deployed engineer builds and runs software inside one customer's systems.

Both build production software. A software engineer builds one product for many users, and a forward deployed engineer builds and runs software inside one customer's systems.

Published Sep 20, 2026 · Updated Nov 7, 2026

- Both roles design systems and ship production code, so the difference is who defines the problem and who owns the result after launch.
- A software engineer ships to a product used by many, and an FDE ships into one customer's environment with its own data, permissions and constraints.
- Employers hire on evidence of production ownership, not on whether a previous title said FDE.
- FDE postings add customer discovery, technical explanation and travel, and those requirements differ by employer.
- Ask how much of the work reaches production and who responds when it breaks, because the title answers neither.

## Where the two jobs actually differ

| Question | Forward deployed engineer | Software engineer |
| --- | --- | --- |
| Who sets the immediate problem? | A named customer, with the engineer and the product team | Product users, internal teams, or a roadmap the company owns |
| Where does the work run? | In, or integrated with, a customer's environment | In the company's own product or internal systems |
| What ships? | A solution, integration or deployment for one environment | A feature, service or platform for a wider set of users |
| How does the engineer learn? | Customer discovery, deployment experience, production behaviour | User research, requirements, operations, metrics |
| What happens to repeated needs? | They become reusable modules or product requests | They enter the roadmap through company planning |
| Customer relationship | Direct and frequent for the work being delivered | Indirect, through product, support or customer teams |

A company can give an FDE broad product ownership, or a software engineer direct customer responsibility. The posting should say which arrangement applies.

## FDE work is still software engineering

A [Databricks senior FDE posting](https://databricks.com/company/careers/open-positions/job?gh_jid=8657065002) asks the engineer to architect and implement end-to-end data, AI and application solutions, lead production delivery, and guide customer architecture. It names Python, Scala, JavaScript or TypeScript, cloud platforms, Spark, MLOps and CI/CD. That is engineering performed inside customer engagements.

The difference shows up in the week. A product engineer clarifies requirements, designs an API, implements a service and measures behaviour after release. An FDE reviews a customer's data flow, decides how to connect a model or API, codes the integration, tests it with customer engineers, deploys it, and writes down a product gap. The next customer brings a different environment, so repeated work has to become something easier to deploy the second time.

## Experience that carries over to FDE work

- shipping and operating production systems
- making design decisions from incomplete requirements
- APIs, data, cloud infrastructure or distributed systems
- debugging across system boundaries
- explaining technical choices to people with other backgrounds
- learning from incidents and changing the system

## What to ask before applying

1. Is the main output a shared product or a customer-specific deployment?
2. How much of the work reaches production, and who operates it afterwards?
3. Does the role own technical decisions inside a customer environment?
4. How does the time split across discovery, implementation, support, travel and internal product work?
5. What gets reused across customers, and who decides what becomes part of the product?

## Related reading

- [What does a forward deployed engineer do?](https://nextmove.md/fde/resources/what-is-a-forward-deployed-engineer)
- [Forward deployed engineer vs solutions engineer](https://nextmove.md/fde/resources/fde-vs-solutions-engineer)
- [How to become a forward deployed engineer](https://nextmove.md/fde/resources/how-to-become-a-forward-deployed-engineer)