The FDE role, decoded

You can describe the FDE job in three sentences using the employers’ own words, name what success is measured on at three companies, and tell whether a role configures a platform or builds bespoke systems.

What it covers

1. The definition employers write down
2. One customer, many capabilities
3. What a week contains, from people who did it
4. How success is measured, company by company
5. Platform configuration or a bespoke build
6. What the job is not

Key takeaways

• The job is building and shipping software inside a customer’s problem, and several employers say so in their own postings.
• The employers quoted here judge the work by what changes for the customer, and they word it differently: impact on the customer’s goal, production adoption, adoption rather than revenue, or what is different at day 30. Where a posting says FDEs are billable, delivery to spec counts too.
• Palantir, Google and Cursor define the role against advising: Palantir contrasts it with a consultant’s one-time analysis, Google with ‘traditional advisory roles’, and Cursor says ‘FDEs don’t advise’.
• Work out whether the role configures a platform or builds bespoke systems from the verbs in the posting, and lead with the matching stories.

Practice

• Building permits take months
• Why forward deployed engineering, and not a software engineering role?
• Tell me about a time you worked inside a customer’s environment rather than your own. What was hardest?
• When would you tell a customer they do not need an engineer embedded with them at all? Pro

Do this now

Answer the customer-environment question out loud, naming what you built and where it ran

Read 0.1

Given any customer-facing job posting, you can classify it as FDE, SA, SE or SWE work and point to the lines that decide it.

What it covers

1. Why the labels blur
2. Production code versus proofs of concept
3. Pre-sale, post-sale, or both
4. Quota, OTE and what the pay basis tells you
5. Where the FDE sits in the org chart
6. One company, two titles, four tests
7. A classification exercise on real posting lines
8. Answers and the deciding words
9. Saying it in the loop

Key takeaways

• Find the line that says what the engineer builds and where it runs: production code for one customer is FDE work; prototypes, demos or guided implementation is SA or SE work; one capability for every customer is SWE work.
• Pre-sale versus post-sale does not separate the roles cleanly: OpenAI’s and LangChain’s FDE-type postings span both. Ask what the role owns after the signature instead.
• OTE on an engineering title means part of your pay is variable; before the onsite, ask the split and what the variable part is measured on.
• When a posting can’t answer one of the four tests, that test becomes your question for the recruiter.

Practice

• Why forward deployed engineering, and not a software engineering role?
• How do you decide between building a custom solution for one customer and pushing for a product change? Pro
• What customer-facing experience do you have? Be specific about who the customer was.

1 more planned.

Do this now

Answer “What customer-facing experience do you have?” in two minutes: the customer, where your code ran, what you owned

Read 0.2

Say why FDE teams exist, when your target built one and why you are moving now, without a growth number that falls apart at the first follow-up.

What it covers

1. The gap between an API and a working deployment
2. Why now
3. Where the term comes from
4. Who built teams, and when
5. Why growth headlines disagree
6. What a team’s age tells you
7. Two follow-ups, in one short exchange
8. What this means for your pitch

Key takeaways

• Name the four pieces of the gap between a model API and a working deployment (connectors, identity, customer evals and a way back) and say what you would do about each.
• Palantir says it pioneered the role and no source we found gives a founding year, so never offer one.
• OpenAI, AWS and Microsoft announced funded deployment organizations within weeks of each other (OpenAI’s is a new company it majority-owns and controls, and Microsoft’s covers more than FDEs), but several large employers say they had FDEs before those organizations existed.
• Growth figures from different datasets cannot be compared, so quote one with its source and window or none.
• Answer ‘why now’ in two halves, the company’s own dated FDE decision and why you are moving at this point in your career, not with a market statistic.

Practice

• Why this company, and why now?
• Walk me through the career decisions that brought you here. Why did you make each move? Pro
• What kind of problem are you most excited to spend the next two years on? Pro

Do this now

Write your ‘why now’ from your first target’s own dated FDE decision

Read 0.3

You can list the job titles your target companies actually post and explain why searching only for ‘forward deployed engineer’ misses roles.

What it covers

1. Four search rules
2. Titles to search, employer by employer
3. One board, searched end to end
4. Titles that are not what they seem
5. When a title search comes back empty or unclear
6. Consultancies and platform-tied roles
7. What the title tells you about level
8. Building your search list

Key takeaways

• Several employers hire for FDE work under other titles, such as Deployed Engineer, Agent Deployment Engineer and Software Engineer, Agent.
• Some FDE-titled postings describe field hardware, application support or a sales-facing job, so ask what you would build, where it would run and who you would answer to before you trust the title.
• A suffix after the title, naming a product, a region or a clearance program, can be the word that decides whether a posting fits you.
• Search by duties as well as titles, and read what a title search returns before you trust it.

Practice

• What level do you think you are, and why?
• This team supports government customers. Do you hold or can you obtain a clearance, and how do you feel about that work? Pro
• Which of our APIs or products have you built with, and what did you find limiting? Pro

Do this now

Answer ‘What level do you think you are, and why?’ against one real posting from your search list

Read 0.4

You can state the travel a specific posting asks for, the questions you will ask about it, and your own limit, before the recruiter call.

What it covers

1. Read the travel line before anything else
2. Two travel lines, worked end to end
3. The range between employers, and inside one
4. Remote does not mean no travel
5. What individual accounts describe
6. Decide your limit, then ask

Key takeaways

• Stated travel ranges from occasional to most of the year, and it varies within a single employer by team.
• A remote listing can still require regular customer visits.
• “Flexible” can mean your flexibility or the client’s, and “up to” can be the norm: ask whose flexibility it is, and plan for the ceiling.
• Decide your travel limit in weeks, tell the recruiter early, and ask which teams fit it.

Practice

• This role involves travel to customer sites. What can you commit to, and what would make it unworkable?
• This team supports government customers. Do you hold or can you obtain a clearance, and how do you feel about that work? Pro
• FDE work can mean travel and constant context switching. Tell me how you have handled a sustained period of heavy load. Pro

Do this now

Write your travel answer for your posting: its travel in weeks, your weeks a month, longest stint, one team question

Read 0.5

Turn any FDE job posting into a one-page prep plan: what you would build, how pay and travel really read, and what the interview is likely to probe first.

What it covers

1. The posting page
2. Duties that reveal the real job
3. Requirements you can bridge and ones you cannot
4. One posting, filled in: Okta’s Senior FDE
5. A second posting, filled in: Databricks’ Sr. FDE
6. Two AI-lab lines, read in brief
7. Turning the posting into prep priorities
8. Keep one page per target and reread it before each round

Key takeaways

• Rank the duty lines instead of counting them; the tags your two most specific lines point to are your guess at what the loop will probe, and that guess is an inference to test with the recruiter.
• Always record whether pay is base, OTE or unstated, with the date you read it.
• Lines copied across a company’s postings describe the unit; the line that names a protocol, platform or artifact is the topic to study first.
• Keep one posting page per target company and reread the rows each round needs before you walk in.

Practice

• What is the hardest technical problem you have solved? Take me into the details. Pro
• What customer-facing experience do you have? Be specific about who the customer was.
• Which of our APIs or products have you built with, and what did you find limiting? Pro

1 more planned.

Do this now

Annotate one posting, then answer ‘What customer-facing experience do you have?’ for its customer type

Read 0.6

You can tell a two-minute story that connects your past work to the FDE job, and give a ‘why FDE, not software engineering’ answer grounded in it that survives three follow-ups.

What it covers

1. What hiring leaders say predicts a good FDE
2. Evidence you already have
3. Teaching, founding and a first career
4. The shape of a bridge story
5. The short ‘why FDE’ answer, built from the story
6. Reasons that collapse under follow-ups
7. Rehearsing against the follow-ups

Key takeaways

• Build an answer that carries two signals: a pull toward customers and outcomes, and proof you can build the thing. Show only the first and it can read as leaving engineering.
• A bridge story names one customer, what they asked for against what they needed, what you built, and what changed for them.
• At senior level, the same story shows you owned the customer’s outcome end to end. At staff or principal level, it names a problem several customers share, the design other engineers built on, and who carried on without you.
• A reason survives follow-ups when it comes from your own work, names what an FDE role gives that a product role does not, and accepts a cost.
• Lead with the short answer, give the story when asked, and rehearse both against ‘why not product engineering?’ on the question page.

Practice

• Why forward deployed engineering, and not a software engineering role?
• What kind of problem are you most excited to spend the next two years on? Pro
• What customer-facing experience do you have? Be specific about who the customer was.
• Give me your background in about a minute, ending with why this role.

1 more planned.

Do this now

Give your short answer and the story behind it in two minutes, then take the three scripted follow-ups

Read 0.7