How to become a Forward Deployed Engineer

A Forward Deployed Engineer is hired to make a product work inside one customer's systems. To get the job you need to prove two things: you can ship production code against messy, real data, and you can work with the customer while you do it.

1. Find your starting point

Your current role decides what you already have and what is missing.

• Software and backend engineers already write production code. The gap is client work: discovery, scoping and demos. See the software engineer switch plan.
• Data and ML engineers know the data. Add APIs, deployment and stakeholder work. See the data engineer switch plan.
• Solutions and sales engineers already face customers. Add production code and ownership of the deployment. See the solutions engineer switch plan.
• Freshers start with foundations and build proof through projects. See the fresher route.

2. Work through the six stages

The FDE roadmap runs from programming foundations to shipping a deployment. Skip what you already have, and take the free skill test for each stage to check.

1. Programming foundations: Python, Git, testing.
2. Data and APIs: SQL, REST, webhooks.
3. Cloud and deployment: containers, CI/CD, secrets.
4. Applied AI: retrieval, agents, evals.
5. Customer discovery: turning a brief into a build plan.
6. Ship a deployment end to end.

3. Build proof, not certificates

Interviewers want to see something deployed. Pick one portfolio project per level and write a one-page handover note for each, as you would for a client. The monthly challenge gives you a brief, a dataset and a deadline.

4. Practise the case round

What sets FDE interviews apart is the customer-scenario round: a vague brief, live. Practise thinking aloud through discovery, scope and risk. The interview guide lists the usual rounds.

5. Decide whether you need a course

A course is worth paying for when you need structure, feedback or a credential. Before you pay, run the buyer's checklist with every provider.