Free roadmapHow to become a forward deployed engineer
A forward deployed engineer goes inside a customer's company and builds until the product works for real. The pay is for one skill: knowing which problem is worth solving. This is the order to learn it in, and how to prove you can do it.
What to learn, in order01Build a whole product alone
On site there is no frontend team and no data team. There is you.
Learn
- Python and SQL, well enough to work without looking things up
- Calling and building APIs
- One cloud: deploy, logs, permissions
- Git and a basic test habit
Proof: one small app you built and deployed alone, with a database, an API and a login, that a stranger can open and use.
02Make AI work on messy data
The demo runs on clean examples. The customer's data is never clean.
Learn
- Prompting and tool use with a current model
- Retrieval over real documents
- Evaluation: a test set of real questions with known answers, run on every change
- Cleaning and joining data you did not design
Proof: an assistant over messy documents, with a written test set and a number: "answers 41 of 50 real questions correctly, up from 23".
03Explain it in plain words
Half the job is a conversation with someone who does not write code.
Learn
- Discovery: asking how the work is done today, and watching it being done
- Writing a one-page plan a manager can approve
- Giving a demo that shows the customer's own case
- Saying "no" and "not yet" with a reason
Proof: a one-page write-up of a real problem: who had it, what it cost them, what you built, what changed.
04Own the result, not the ticket
You are measured on whether the customer uses it, not on whether you shipped it.
Learn
- Picking the one problem worth solving out of ten that were asked for
- Measuring use after launch
- Staying until it works: fixing what breaks in the second week
Where
- The same real project from stage three, taken to daily use
- Job descriptions from Palantir, OpenAI and Anthropic: read what they ask for and map your proof to it
Proof: a number from real use. "Three people use it every day. It replaced a two-hour weekly report."
How to get certifiedThere is no official forward deployed engineer certificate, and no employer asks for one.
What gets you hired is proof that you deployed something real. Certificates still help in two ways: they give your learning a deadline, and they get a CV past a first filter. These are the ones tied to skills the job uses.
Exam names and prices change. Check each provider's page before you book. Several training companies also sell a "Certified Forward Deployed Engineer" badge; none is accredited or requested in job postings, so weigh the price against a project you could build in the same time.
A 90-day plan, at about ten hours a weekDAYS 1–30Ship one app alone
Python, SQL, one cloud. Deployed, with a public URL. Start the cloud associate certificate.
DAYS 31–60Add AI on ugly data
Retrieval plus a 50-question test set. Report the score before and after. Take the Palantir or Databricks associate exam.
DAYS 61–90Do it for a real person
Find one small organisation. Watch how they work, fix one problem, stay until they use it daily. Write the one-page story.
Start stage one todayDescribe it. Ship it.
Every stage on this page needs a real project with a public link. Youmake turns a sentence into a live product. Describe your idea, and ship your first one today.
Build your first projectyoumake.devSources: The Pragmatic Engineer and DataCamp on the role; Palantir Learn, AWS and Databricks on certifications; public reviews of 2026 job postings on what employers ask for. This page is a learning guide, not career or financial advice.