Deployed Lab

Module 1 · The FDE role and mindset · Chapter 1

What an FDE actually does

15 min1 live simulation5 checks
In 30 seconds

The one picture to remember: the FDE is the chef who cooks in your kitchen.

The problem A delivery company tells a software vendor: "We need AI for our supply chain." Three engineers build a late-delivery predictor (a made-up, typical story). Six weeks later nobody uses it. The data sat in a system they could not reach, and nobody had asked the planners how their day works. The missing person is the FDE: the one who sits with the users and makes the software work in the messy real world.

Next: you will meet a few words again and again. Here they are in plain language, then the real numbers on why this job is worth learning.

Words you'll meet

Why it is worth learning right now

Real data from public job boards, snapshot 15 November 2026. Posted base salary only.

367open FDE-style roles
10companies hiring
$243Kmedian posted base pay
$146K to $445Kposted base range

Who is hiring: OpenAI (95 roles), Palantir (91), Databricks (86), Anthropic (46), plus Scale AI, Cohere, Stripe and others. Pay is only listed on some postings (144 of the 367 list US-dollar ranges), and ranges vary by level and location. See every opening on the jobs and pay page.

Next: who does what. Four jobs touch software and customers, and people mix them up.

Four jobs, one kitchen

Four jobs touch software and customers. Picture a restaurant. Only one chef cooks in your kitchen.

Four jobs pictured as four kinds of chef Four boxes side by side. The software engineer designs the recipe and the factory kitchen. The solutions engineer does a tasting demo at a trade show. The consultant writes a report on how your kitchen should run. The forward deployed engineer cooks in your kitchen and trains your staff. Software engineer Designs the recipeand the big factorykitchen, forthousands ofcustomersIn real terms: buildsthe product that manycustomers all use Solutions engineer Tasting demo ata trade show.Shows it can tastegood, then helpsclose the saleIn real terms: showsthe product to a buyerand answers theirtechnical questions Consultant Writes a report onhow your kitchenshould run. Thensomeone elsedoes the cookingIn real terms: studiesthe problem and writesadvice FDE Walks into YOURkitchen, cooks withYOUR ingredients,fixes the oven andtrains your staffIn real terms: buildsand runs the softwareinside the customer'sbusiness
Four jobs as four kinds of chef, with the real job in plain words under each. Only the FDE stays in your kitchen until the food is really being served.

Where the picture breaks down: a real FDE also carries what worked back to the company, so the product gets better for everyone.

Next: the title "FDE" is not used the same way everywhere.

Three jobs share one title

Companies use "FDE" in different ways. Always read the posting.

Next: how these jobs differ in practice: where does each person's week go?

Where does the time go?

Same week, four different people. Every job is a mix of five things. Click each role to see its mix.

Illustrative profiles, not measured. In this picture, the FDE is the only role high on both customer time and responsibility if it breaks.

The bars are the author's rough picture, not measured data. Compare the shapes, not the numbers.

RoleTime with customersTime writing codeResponsibility if it breaks
SDELowHighLow
Solutions engineerHighLowLow
ConsultantHighLowLow to medium
FDEHighMediumHigh

Next: how a real FDE project goes, start to finish. We follow one made-up delivery company through five stages.

How an FDE project goes: the map

Every project has five stages, like moving house. Press next to see the whole map first.

The example we follow: a delivery company with 6 planners, who keep goods moving. Their VP of operations (VP means vice president) has just said "We need AI for our supply chain." The supply chain is the path goods take from makers to buyers.

The five stages of a customer project Five stages in a row: Discover, Proof of concept, Pilot, Production, Expand. A dashed path carries what you learn to the product team, and another dashed path carries the improved product to the next customer at Discover. Discoverlook around Proof of concepttry the idea Pilotsmall real trial Productionthe full move Expandmore teams Product teamproduct builders what we learn goes herenext customer starts here
  1. Watch how the work really happens. The first request ("AI for our supply chain") is rarely the real problem. You leave with a clear problem, a champion at the customer, and a way to measure success.
  2. Build the smallest thing that shows the idea working, fast. Example: a screen built from 500 sample shipments.
  3. Five planners try it on real, messy data. Many projects stall here, because nobody owns the move to production.
  4. Everyone depends on it. You add alarms, access rules, a security review and a plan to undo changes.
  5. A system that works earns the next team and the next use case. You reuse what you built.
  6. What you learn here is handed to the product team, so the next customer starts further ahead. We explain this loop after Stage 5.
Customer-facingQuick prototypeYour running systemProduct team

Now we walk the stages one by one. Stage 1 starts with a phone call.

Stage 1: Discover, the first call

In Discover you do not build anything. You talk and you watch, to find the real problem.

Below is the first call with the VP. You are the FDE. Choose how you respond and watch two meters: customer trust, and scope risk (the chance the project grows beyond what you can deliver).

Notice: the best path never said yes or no to the six weeks. It asked what goes wrong today. Trust rose and risk fell at the same time.

The VP's answer gave you a clue: planners spend hours phoning carriers (trucking firms) to find late shipments. Next, turn that clue into numbers.

Stage 1: Discover, turn the clue into numbers

A vague wish is hard to act on. A number is easy. In Discover, an FDE measures how big the problem is today (the baseline), so you can prove later that it got better.

Made-up example: the 6 planners spend about 4 hours a day phoning carriers to find late shipments.

Planner hours spent chasing carriers each week A bar of 120 hours per week split in two equal halves. The left half, 60 hours, is time saved if chasing is cut in half. The right half, 60 hours, is time still spent chasing. 6 planners x 4 hours x 5 days = 120 hours per week 60 hours saved 60 hours still spent goal: cut chasing in half still needed for hard cases 60 hours saved is about 1.5 full-time people (at 40 hours each)
Illustrative numbers. The whole bar is today's cost (the baseline). The left half is the goal.
  1. One planner chases carriers 4 hours a day.
  2. 6 planners: 6 x 4 = 24 hours a day.
  3. 5 days a week: 24 x 5 = 120 hours a week. This is the baseline.
  4. Goal: cut chasing in half. 120 / 2 = 60 hours saved (a guess to agree with the VP).
  5. One full-time person is about 40 hours, so 60 / 40 = 1.5 people's time.

So you leave Discover with four things: a clear problem (late shipments found too slowly), a user (the planners), a baseline (120 hours a week) and a champion (a person at the customer who wants this to work).

Next: Stages 2 and 3. You have a clear problem. Now you build something and put it in front of real users.

Stages 2 and 3: Proof of concept, then pilot

Three weeks into the project, you have built a POC. It shows late shipments on a screen, using a sample file of 500 shipments. Here comes the moment that tests every FDE.

Scenario The VP loves the demo and says: "Can we switch it on for all planners on Monday?" The real system has about 20,000 shipments a week, and the security team has not seen it. What do you say?

The demo is real, but it only proves the idea works on 500 clean rows. A pilot with a small group tests it on the real 20,000 shipments, with security and an owner in place, before everyone depends on it. Saying yes risks the tool failing in front of all the planners on Monday. Saying no throws away goodwill. Agreeing what "ready" means keeps both the trust and the safety.

A sample reply: "I would love that. First, let us run it with 5 planners for two weeks on real data, and ask security to review it. Then everyone gets it the Monday after."

The gap between a working demo and a system people trust is where projects commonly stall. Demos run on clean sample data and skip access rules, alarms and ownership. Closing that gap is a large part of what customers pay an FDE for.

Next: Stage 4. A pilot that works needs to become something everyone can depend on.

Stage 4: Production

Production is the real thing real people depend on. If it breaks at 9 a.m. Monday and someone cannot work, it is production.

Think of a school play. Rehearsal in an empty hall is practice. Opening night with parents in the seats is production.

On opening night you need working lights and a plan for when things go wrong. For software, that means:

For the delivery company, this is the week all 6 planners start relying on the screen. This is where an FDE earns their pay.

Next: Stage 5, and the part that makes an FDE different from everyone else.

Stage 5: Expand, and the loop back to the product

Expand. The screen works. Now the warehouse team asks for one too. You reuse what you built, so the second project is faster than the first.

Then one more thing happens. It is called the loop back.

What is it?

Something you built for one customer becomes a feature of the product, for every customer.

Example: the planners asked "alert me when a shipment is more than 2 hours late". You built it for them. A month later two other customers ask for the same thing. The product team makes it a built-in setting.

Why does it matter?

How does it happen?

  1. Notice: you build the same fix a second time.
  2. Write it down: what the customer asked for, and the hours it saved (your baseline numbers).
  3. Hand it over: give the product team that evidence.
  4. Build it once, in a general way: as a setting, not hard-coded for one customer.
  5. Next customer: starts from the feature, so their Discover is shorter.

Why don't regular software engineers do this?

It is not that they cannot. It is where they sit. This is a pattern in many companies, not a rule for every one.

The FDE sees the real mess and can build the fix. That makes the FDE the link between customers and the product.

Next: you have now seen the whole job. Here is what you can practise in the rest of the course.

What is coming in this course

You just did one exercise. The rest are hands-on too. Seven chapters are free, so you can try the next ones now:

Start the next free chapter

Mix-ups to avoid

Recap

In the field A team demoed a document-search assistant on sample PDFs. On the pilot they connected the real file share. Half the files were scans, and the assistant happily quoted HR files to anyone who asked. Fixing that took longer than building the demo.

Chapter quiz

Four questions. Score 70% or more to mark this chapter complete.

Review