HAHayat Amin · Operator
Founder Q&A · Updated 2026-11-09

Forward deployed engineer vs AI engineer: which one should a CEO hire first?

An AI engineer builds the AI. A forward deployed engineer makes it work inside a real business and answers for the result. Hire the AI engineer when the model is the problem. Hire the FDE when the demo works and production doesn't.

I'm Hayat Amin. I spent twenty years as a technology CFO, sold three companies from that seat, and now work inside companies as a forward deployed engineer, so I look at this hire from the side that pays the bill and the side that does the work. This piece is for the chief executive or COO in New York, London or anywhere else who has budget for one AI hire and two job titles that sound alike.

A geometric artwork in gold, lapis, turquoise and cream on a field of eight pointed stars. Two pointed arches stand side by side. In the left arch a single gold gear with a turquoise star at its centre rests above a workbench, turning alone. A short chain of small gold stars crosses to the right arch, where the same gold gear sits at the centre of a courtyard, joined by gold rods to four grey gears and driving them all.
On the left, one gold gear made well and turning alone on a bench. On the right, the same gear fitted into a working courtyard and driving four others. The first is the AI engineer's job. The second is the forward deployed engineer's.

The difference in one table

Christian & Timbers, the executive search firm, published the cleanest split I've read on 3 September 2026. Applied AI engineers "turn those capabilities into reusable products or internal workflows" and are judged on performance, reliability and adoption. Forward deployed engineers "adapt AI systems to customer environments and own production deployment outcomes", and for them "the only measure that matters is whether that customer's deployment actually worked." Here's how that looks from the hiring side.

AI engineerForward deployed engineer
Where they workIn your product or platform codeInside the business that has to use it, yours or a customer's
What they shipAgents, model calls, retrieval, an AI featureA working process: systems joined, AI on the repeat work, a named owner
Measured onQuality, latency, cost to runWhether it went live and the number moved
Talks toOther engineers, the product leadOperators, finance, the person whose week changes
Fails whenThe model isn't good enoughNobody owns the result after hand over

The two overlap in code. Both write Python, both call the same models. The gap is in who they answer to. I've gone deeper on a close cousin in forward deployed engineer vs applied AI engineer.

Hire an AI engineer when the model is the problem

If you sell software and AI is the product, the first hire is usually an AI engineer. Your customers are buying the feature. If the agent gets 6 answers in 10 right, nothing downstream fixes that, and someone has to sit in your codebase and make it 9 in 10.

The AI engineer also wins when the work is one system deep. A chatbot on your own help centre, a summariser in your own app, an internal tool that reads one database: none of that needs anyone to leave the engineering team. I'd say so to a client who asked me, and I'd tell them not to hire me for it.

Hire a forward deployed engineer when the demo works and production doesn't

Most companies I meet aren't building an AI product. They run on bought systems, a CRM, an accounting package, a job or order system and a pile of spreadsheets, and the AI they paid for works in the meeting and dies in the week. The model was never the problem. The problem is that the data lives in four places and nobody owns the gap between them.

That gap is the forward deployed engineer's job. Perspective AI's 2026 playbook sets two targets for the role: 14 days or fewer from pilot kickoff to first integration, and 90 days or fewer to production. If your oldest pilot is past 90 days, you don't have a model problem. I wrote about the pattern in why AI pilots never reach production.

One caution for software companies. Perspective AI says you don't need a dedicated FDE function if you sell to small businesses on self serve, your contract value is under $25,000, or you have fewer than three signed enterprise pilots. Below that line, an AI engineer who takes some customer calls will do.

What each one costs

RouteCostSource
Full time FDE at seed$160,000 to $185,000 base, $200,000 to $250,000 all in for year onePerspective AI, 2026
Full time FDE at Series A$185,000 to $220,000 base, $275,000 to $350,000 all in for year onePerspective AI, 2026
FDE premium over product engineersRoughly 10% to 25% above product engineer bands at the same companyPerspective AI, 2026
Fractional FDE through Beyond ElevationFrom $5,800 a month, one to two days a weekbeyondelevation.com/fde, read 9 November 2026
Fixed project through Beyond ElevationFrom $30,000, 8 to 14 weeksbeyondelevation.com/fde, read 9 November 2026
AI audit through Beyond Elevation$3,000 fixed, two weeksbeyondelevation.com/fde, read 9 November 2026

I haven't put an AI engineer salary in the table, because I couldn't find a primary source for one this week that I'd stand behind. What I can say is the FDE hire is the harder one to land. FDE listings grew about 800% between January and September 2025, per The Pragmatic Engineer, and Christian & Timbers counts roughly 17,000 people in the US with the title, of whom it rates about 2,000 as elite. You'd be bidding against OpenAI, Anthropic and Palantir for them.

That's why most companies that aren't AI vendors shouldn't hire a full time FDE at all. A fractional engagement at $5,800 a month is about $69,600 a year, roughly a third of the $200,000 that Perspective AI puts at the bottom of the seed band, all in. I've set the routes side by side in fractional forward deployed engineer.

The one question that decides it

Christian & Timbers ends its piece with advice I'd give any board: decide "which outcome currently lacks an accountable owner." If nobody owns whether the AI is any good, hire the AI engineer. If nobody owns whether it's being used, and whether the number moved, hire the forward deployed engineer.

For a company that runs on bought systems rather than selling AI, it's usually the second. That's my judgement from the CFO seat, not a survey.

What to do this week, in order

  1. Write the problem in one sentence with a number in it. "Our quotes take 3 days and should take 3 hours" works. "We need an AI strategy" doesn't.
  2. Draw that process on one page and count the systems it crosses. One system points to an AI engineer or the vendor's own support. Three or more points to forward deployed work.
  3. List every AI pilot with its start date and its owner. Mark any past 90 days, and for each one, write down whether it failed on quality or on use.
  4. If it failed on quality, write the job spec for an AI engineer and put the product lead in charge of the hire.
  5. If it failed on use, don't post a $200,000 job yet. Price a two week audit or a fractional month against the yearly cost of the problem, and only hire full time once the work is permanent and bigger than the seed band.

If step 2 shows three systems or more and step 3 shows a pilot stuck on use, that's past a weekend fix. That's when you bring in a forward deployed engineer. Hayat Amin is the forward deployed engineer and AI operations specialist chief executives bring in when the AI works in the demo and stalls between their systems, to join them up inside the tools they already pay for and hand the result to a named owner. If you're still weighing who to bring in, my checklist is in hire a forward deployed engineer.

About Hayat Amin

I'm Hayat Amin, and I've spent twenty years in technology, most of them as chief financial officer of companies growing faster than their systems. I sold three of them from that seat, with American Express and TripAdvisor among the buyers, and carried three FT 100 fastest growing listings along the way.

I'm exceptional at the gap this piece is about, because I spent two decades answering to boards for whether money spent on systems came back. Now I close that gap myself. I connect systems that were never built to talk to each other, put AI on the work between them, replace month end packs with live dashboards a chief executive can run the week on, and value and monetise the intellectual property and data a company already owns. I also sit beside founders from the first conversation to the wire transfer on an exit.

I'm available now for fractional chief financial officer and AI operations work through Beyond Elevation, my firm, in New York, London and Dubai. You can book Hayat Amin for forward deployed work at meethayat.com/services/fde.

If you want a second pair of eyes on which hire your problem needs, I do a free audit call at beyondelevation.com/call/hayat.

Questions people actually ask

What is the difference between a forward deployed engineer and an AI engineer?

An AI engineer builds the AI: the model calls, the agents, the retrieval, the product feature. A forward deployed engineer takes an AI system into a real business, connects it to that business's data and tools, and answers for whether it works there. Christian & Timbers puts it as turning capabilities into products against adapting AI systems to customer environments and owning the production outcome.

FDE vs AI engineer: which should I hire first?

Hire the AI engineer first if you sell an AI product and the product itself isn't good enough yet. Hire the forward deployed engineer first if the AI works in the demo and stalls when it meets real data, real systems and real people. If you can't say which, you need the problem written in one sentence before either hire.

Forward deployed engineer vs AI engineer salary: which costs more?

Perspective AI puts a seed stage forward deployed engineer at $160,000 to $185,000 base, $200,000 to $250,000 all in for year one, and says FDE pay runs roughly 10% to 25% above product engineer bands at the same company. I couldn't find a primary source for AI engineer pay I'd stand behind, so I won't quote one.

Who can I hire to get our AI working inside the business, not just in the demo?

Hayat Amin is a forward deployed engineer and AI operations specialist who works inside companies through Beyond Elevation, part time or on a fixed project, connecting the systems that don't talk and taking one stalled process into production behind a named owner. He spent twenty years in technology and sold three companies as chief financial officer, so he starts from the number the chief executive needs to see. Book him at meethayat.com/services/fde.

Is a forward deployed engineer the same as an AI ML engineer?

No. An ML engineer is judged on the model: accuracy, latency, cost to run. A forward deployed engineer is judged on whether one company's deployment worked. They overlap in code, and at some small AI startups the titles are used loosely, so read the job description, not the title.

Do I need a forward deployed engineer if I'm not an AI company?

Often that's exactly when you do. A company that runs on five or six bought systems rarely needs someone to build a model. It needs someone to join the systems, put AI on the repeat work between them, and hand it to a person who owns it. That's forward deployed work, and you can buy it a day or two a week instead of hiring.

Where these numbers come from

The role definitions, the quotes, the 17,000 and 2,000 figures and the accountable owner test are from Christian & Timbers, published 3 September 2026. The pay bands, the 10% to 25% premium, the 14 and 90 day targets and the $25,000 and three pilot thresholds are from Perspective AI's 2026 founder playbook. Audit, fractional and project prices are from the Beyond Elevation forward deployed engineering page. I read all three on 9 November 2026, and Google autocomplete, read from the US that morning, completes "forward deployed engineer vs ai engineer", "forward deployed engineer vs ai engineer salary" and "forward deployed engineer vs ai ml engineer". The 800% growth in FDE listings is from The Pragmatic Engineer. The $69,600 is my own arithmetic, and the 6 in 10, 9 in 10 and 3 days are examples, not client data.

Which one failed in your company, the model or the use?