# After a few years as an FDE, choose your exit by the gap you are willing to fill

> Principal FDE, product manager, engineering manager and founder all draw on the same field experience with customers. Each route also demands one skill that day-to-day FDE work barely teaches.

Original: https://fdetimes.net/en/analysis/career-paths-after-forward-deployed-engineer/

After a few years as an FDE, the question of what comes next is usually framed the wrong way. The common exits (Principal FDE, PM, engineering manager, founder, a return to SWE) almost all draw on the same capital: the ability to diagnose a problem on site with the customer.

What separates them is the extra skill each one forces you to learn, and day-to-day FDE work barely teaches it. The more useful question, then, is which skill you are willing to spend the next two years learning.

## The shared capital: diagnose before you build

FDE Academy names this shared capital neatly: FDEs diagnose the problem before building the solution. Founders who skip that step, it adds, end up building for the wrong problem. In practice it is the habit of sitting with a customer who says "we need a dashboard" and discovering that what they really need is data that isn't three days late.

FDE Academy also observes that the FDE track is broader than the SWE track, not faster. That is worth remembering when you compare yourself with friends in pure SWE roles. You are not ahead of them in seniority.

What you do have is exposure to many sides of a product: the customer's infrastructure, their business processes, the people who make decisions, and the pressure of a real deadline.

Once the shared capital is in place, choosing an exit becomes a matter of choosing the missing skill. The paths below are missing very different things.

## Principal FDE: still in the field, but working through others

According to FDE Academy, Principal FDEs and FDE leads take on the company's most complex engagements, often owning an entire vertical such as healthcare, finance or the public sector. You advance without leaving the field, and for people who prefer working with customers to sitting in internal meetings, that is the main appeal.

Cornerstone's posting for a Principal Forward Deployment Engineer shows where the role expands. It describes the position as the bridge between the product engineering team and the company's most strategic enterprise customers. The holder must also mentor junior FDEs and set the standard for customer delivery.

That last detail is the real missing skill. A good senior FDE solves problems with their own hands. A Principal has to get five other people to solve problems to the same standard, even when the Principal is not in the room.

Imagine your team has four FDEs, each handing over to customers in their own way. One writes a runbook; another leaves a few lines on Slack. If you write a handover checklist, persuade the whole team to use it and revise it after each project, you are doing exactly the job that posting describes, even though your title has not changed.

## Moving to PM: the hardest skill is saying no

Many see product as the natural exit. Salesforce's FDEs describe themselves as the voice of the customer, carrying feedback back to the product team to shape the roadmap. Entrepreneur Loop also lists product leadership among the common exits.

Second Talent, comparing the FDE and PM roles, notes that the most common move between them is from engineer to PM. Its guide to the forward deployed PM, a hybrid title between the two roles, lists FDE as one of three roles that typically lead to it.

But Second Talent also pinpoints where FDEs fall short: you need to prioritise, and you need to be comfortable turning down a paying customer. Scale AI's posting for a forward deployed PM asks for candidates who can say no to customers "and explain why".

For an FDE, this runs directly against professional instinct, because the whole job is built around making one specific customer succeed.

Imagine a large customer demands a custom connector for their internal system. As an FDE, you would estimate, build and hand over. As a PM, you have to set that request beside ten requests from ten other customers, and quite possibly reply that the connector will not be on next quarter's roadmap.

This door is not always open. On 5 October 2026, Second Talent counted 81 roles containing "Forward Deployed" on Palantir's careers board, and none carried a product manager title. Second Talent itself cautions that counting titles is a crude tool, and Intercom acknowledges that the forward deployed PM title is still taking shape.

So do not wait for a posting with exactly that name. Look for teams that give FDEs a say in prioritisation, and build your own evidence that you have said no at the right moment.

## Into management: technology is not the bottleneck

FDE Academy states plainly that what FDEs usually have to make up for when moving into engineering management is people management: performance conversations, other people's career development, team structure. Judgement and execution they already have.

That sounds obvious, but it cuts against how many FDEs assess themselves: they think they are ready because they have led an entire deployment.

Leading a deployment is not the same as managing people. In a deployment, the team disbands when the project ends. An EM looks after the same group across many projects: how they grow, when they are burning out, who should take the next difficult engagement.

If you have never had to hold a hard conversation with a colleague about performance, that is the skill you are missing.

## Founders need to learn sales; SWEs need depth

Entrepreneur Loop writes that many FDEs move into product leadership or sales engineering, or start companies to solve problems they found in the field. A more concrete signal comes from Concept VC: among the Palantir-alumni founders the fund analysed, FDE was the most common background.

This path uses the most shared capital, just as FDE Academy's line about diagnosing before building suggests. The missing skill is harder to measure, but one difference is easy to see.

As an FDE, you usually arrive once the customer has already agreed to work with the company. As a founder, nobody has agreed yet, and you have to get the first customer to sign yourself.

So if you lean this way, ask to join a few demos, or write a technical proposal for a customer who has not yet signed. You will soon find out whether you can stand being turned down.

As for returning to SWE, the "broader, not faster" observation cuts both ways. You bring back a perspective many SWEs lack: how software lives in a customer's real environment. But if the past few years were mostly integration and customisation, be ready to prove depth in a specific technical area.

## Each exit needs its own kind of evidence

The table below sets the missing skill for each path beside things you can do now to show you are learning it.

| Exit | Skill to learn | Evidence you can build as an FDE | How to put it on your CV |
|---|---|---|---|
| Principal FDE | Setting standards and guiding others | A handover checklist the whole team uses; mentoring a junior FDE | The delivery standard you set and the number of projects that applied it |
| PM (via forward deployed PM) | Prioritising, turning down paying customers | A prioritisation memo; a request you recommended not doing | A roadmap decision you influenced with customer feedback |
| Engineering manager | Managing people | Hiring interviews, onboarding new joiners, performance feedback | The number of people you onboarded or mentored, and their results |
| Founder | Selling, getting the first customer to sign | Joining demos, writing technical proposals before a contract is signed | Customers you helped win and the real problem you found for them |
| Return to SWE | Depth in one technical area | A component you own from design to operation | The technical design you were responsible for, not just the integration |

The third column is the one that matters. Most of the evidence for your next move is built inside your current FDE work, provided you deliberately take on the right kind of task.

**Key point:** Choose your next step by the skill you lack, not by the skill you are already good at.

## Start with your current project

If you are in your second or third year, do not wait for a performance review to decide. On your next project, ask for a piece of work from the evidence column of the path you lean towards: a prioritisation proposal if you are thinking about PM, mentoring a new joiner if you are thinking about EM or Principal.

If you are preparing to apply for an FDE role, read job postings the same way. A role that mentions mentoring in the description, or that carries influence over the roadmap, is already opening your next exit.

To learn how to say no to a customer or mentor a newcomer, you do not need to wait for anyone to open a new role. The person who arrives at the next interview with evidence of having learned the missing skill will have an edge over someone carrying only a longer CV.

**Try this week:**

- Take the most recent customer request you went along with and rewrite it as a one-page prioritisation memo: if you had the authority to refuse, would you, why, and what would you propose instead.
- Pick one step in the customer handover process that everyone on the team does differently, write it up as a standard checklist and ask a junior FDE to try it.
- Rewrite the FDE experience section of your CV for the path you have chosen: each bullet should name a problem you diagnosed before you started building.

## Sources

- [What FDEs Become Next: Senior Roles, Leadership Tracks, and Founding Paths After Forward Deployed Engineering (FDE Academy)](https://fde.academy/blog/forward-deployed-engineer-career-after-fde)

- [Principal Forward Deployment Engineer](https://jobs.lererhippeau.com/companies/edcast/jobs/83224388-principal-forward-deployment-engineer)

- [Forward Deployed Engineer vs Product Manager: Roles, Pay and the Forward Deployed PM](https://www.secondtalent.com/occupations/forward-deployed-engineer-vs-product-manager/)

- [Behind The People: Palantir](https://concept.vc/news/palantir-spin-outs-a-deep-dive)

- [What Is a Forward Deployed Engineer? Why More Startups Are Hiring Future Founders Into FDE Roles](https://entrepreneurloop.com/what-is-a-forward-deployed-engineer/)

- [Versioning Up Your Career: How Your vNext is an FDE at Salesforce](https://www.salesforce.com/blog/versioning-up-your-career/)