Why AI-native teams need Forward Deployed Engineers more than Solutions Engineers
Solutions Engineers help win the deal. Forward Deployed Engineers make the deployed product work. For AI-native teams selling capability rather than features, that distinction decides the renewal — and the cap-table.
Every AI-native scale-up eventually hits the same wall: the demo wowed the customer, the contract closed, and six months later the product still isn't producing the outcome the customer paid for. The instinct is to blame the model. The cause is almost always organisational — you hired Solutions Engineers when you needed Forward Deployed Engineers.
The Solutions Engineer's job is to close
Solutions Engineering is a beautifully optimised function. SEs run discovery, build the bespoke demo, navigate procurement, and hand a signed contract to Customer Success. Their incentives are aligned to logo acquisition and ARR. This works extremely well for products with deterministic value — CRMs, observability, data warehouses.
It does not work for LLM products. The moment the contract closes, the SE rolls onto the next deal. The customer is left with an evaluator who hasn't shipped the integration, no eval suite, no fallback strategy when the agent hallucinates, and no relationship with anyone who can push fixes into the product.
The Forward Deployed Engineer's job is to make it work
FDEs are paid to produce the deployed outcome. They write the eval set against the customer's golden data, instrument the customer's workflow, ship the integration, train the customer's team, and feed everything they learned back into the product roadmap. They stay on the account for months, not weeks.
This sounds expensive — until you compare it to the cost of a churned six-figure logo and the negative reference the customer becomes in their industry.
What the ratio should look like
Healthy AI-native teams we see in New York and SF run roughly 1 FDE per $500k–1M ARR on the account, scaling down as the deployment stabilises. SEs remain for pre-sales motion, but the ownership transfer on close is to an FDE, not to a generic CSM.
Hiring this in the US is competitive: senior FDEs with shipped LLM agent experience are in single-digit supply in New York. The platforms that work pre-screen on rubric (reasoning, communication, ownership) and present anonymised shortlists in 48 hours, not weeks.
Key takeaways
- SEs optimise for close. FDEs optimise for deployed outcome.
- LLM products fail customer-specifically — generic CS can't fix them.
- Plan for ~1 FDE per $500k–1M ARR until the deployment is stable.
- Hire on rubric, not on resume keywords.
Continue reading
What does a Forward Deployed Engineer actually do?
A practical, in-the-room look at the Forward Deployed Engineer role — from its Palantir origins to how OpenAI, Anthropic and US AI-native scale-ups deploy FDEs against real customer problems in 2026.
Direct Hire vs Placement — picking your track under US placement law
A founder-friendly guide to the two US placement tracks: when Direct Hire (leasing personnel) is mandatory, when Placement (placement) is allowed, and how cross-border arrangements are constrained by US contractor classification.
Hiring Forward Deployed Engineers in New York without breaking placement law
A founder's checklist for legally hiring FDE contract talent in New York — what the labor office New York inspects, how to structure supervision, and the contract clauses that keep you on the right side of US placement law.