
Milos Mandic's interview with Boaz Francis is titled after a hiring signal, and the most useful thing in it is about something else. This is a Rewrite of "look for the spark" into something you can do before the interview starts.
The short version
- Boaz Francis leads forward deployed engineering at Wonderful, in more than thirty countries, after five years at Palantir.
- In Milos Mandic's FDE Hub interview of November 17, 2026, he says he hires for a spark: the candidate who lights up when things get hard.
- In the same interview he describes two hires with the same raw ingredients. At Palantir a new grad lands among experienced FDEs and ramps.
- At a new Wonderful site, the first hire with no experience finds it very hard to put things in motion, so he hires experience there, and goes back to early talent once the country matures. The candidate is constant and the site varies.
- So write the site down first, in four lines: the harness, the eval, the handback path, and the scope that was sold. If all four exist, hire for the spark. If none do, you are hiring the person who builds them, and that is a different req.
What Francis said
The spark first, because it is the headline. Francis told Mandic that tech and experience matter, and that a lot of the job is in personal attributes: grit, motivation, curiosity, and the spark, which he describes as lighting up when things get tough and starting to come up with new ideas. His interviews put candidates under pressure with a clear goal and watch whether they keep attacking it from new directions.
He gives a mix of where his people come from. About one in six or seven are ex-founders. Others come from app development, a few from DevOps, and some from solutions engineering who were frustrated by only building the first stage.
Then the part about sites. Palantir, he says, commonly hires straight from university. When someone with the right raw skills is dropped into an environment with a ton of support around them, people who have been FDEs for many years, they shape up quickly.
Wonderful starts sites in new countries. There, he says, if the first person you hire has all the right skills in raw form and no experience, they are going to find it very, very difficult to put things in motion and scale the team. So he looks for experience at the smaller sites earlier on. Now that many of the countries are reaching maturity, he sees what Palantir sees: early talent lands in an environment that already works and ramps quickly. He calls it a tipping point where experience matters more or less depending on the environment.
And the line from a dinner with other people building FDE organizations, who had concluded they all had to hire ex-Palantir: "Palantir doesn't hire ex-Palantir people. And that still works."
The variable is the site
Read those two hires side by side. Same raw ingredients. Same spark, by his own account of what he screens for. One ramps and one struggles. What changed was where they landed.
A title like Look for the Spark puts the weight on the candidate. Francis's evidence puts it on the environment, and he says so: put the right kind of person in the right environment and they become an FDE.
That matters because most teams asking how to hire FDEs right now are not Palantir and are not Wonderful's mature sites. They are the new site. They are posting a req written for the first case and filling it in the second.
In 2,000 of 17,000: The FDE Shortage Is a Product Problem I argued that the seat needs four things the engineer does not carry in. I'd now use those four as the description of a site.
- A harness they can change on site without a redeploy.
- An eval the customer's cases can join.
- A handback path with a product owner on the other end.
- A sale that sold scope instead of magic.
4 lines
Francis's "ton of support" and "an environment that already works" are the people side of this. These four are the product side. A site has both or it is still being built.
Two different reqs
All four exist. Hire for the spark. Francis's interview is the right one: pressure, a clear goal, and a look at whether the person keeps generating. A strong new grad or a founder between companies can do this job, and the site will teach the rest.
None exist. The person you hire will spend the first quarter building the harness access, the eval, and the route back into product, while also deploying. That is a builder of sites. They need to have done it before, which is what Francis does at his early sites. Interview for it directly. Ask what the handback looked like at their last company and who read it. Ask how a customer's cases got into the eval. The offer is larger and you should know that before the req goes out.
Some exist. Write which ones, and say in the req which the hire is expected to build. Candidates with the spark will take that as the interesting part.
The first hire at a new site also decides what the tenth hire can be. In The FDE Scorecard: Count What Stayed, Not Who Was Sent the function is measured on generalization rate and on hours per deployment falling every quarter. Those are the numbers that tell you a site has crossed Francis's tipping point and you can go back to hiring raw talent.
This week
Before the next FDE req goes out, write the four lines for the site that person will sit in, with a yes or a no on each. Put the answers in the req. The whole series is at The FDE Transition, and this sits in AI Product Management because the four lines are product's to supply.
Related answer: Should you hire experienced forward deployed engineers or train new ones?
Sources: Milos Mandic, "Look for the Spark: A Conversation with Boaz Francis," FDE Hub, November 17, 2026, read in full: the spark, the one in six or seven ex-founders, the Palantir new-grad comparison, the new-site hires, the tipping point, and the quoted line about ex-Palantir hires. I did not watch the video version. The four lines are mine, from the post linked above.
Frequently asked
What does Boaz Francis look for when hiring forward deployed engineers?+
In his November 17, 2026 interview with Milos Mandic on FDE Hub, Francis, who leads forward deployed engineering at Wonderful, says he looks for a technical bar, agency, urgency, and what he calls the spark: when things get tough, the person lights up and starts coming up with new ideas. He also says you cannot compromise on talent.
Why does the site matter more than the spark?+
Because Francis's own examples hold the candidate constant and change the site. Palantir hires new grads into an environment full of experienced FDEs and they ramp. At a new Wonderful site, he says a first hire with the right raw skills and no experience finds it very difficult to put things in motion. Once a country matures, early talent ramps quickly again.
What should be written down before posting an FDE req?+
Four lines about the site the hire lands in: whether there is a harness they can change on site without a redeploy, an eval the customer's cases can join, a handback path with a product owner on the other end, and a sale that sold scope. These are the four things I listed in 2,000 of 17,000: The FDE Shortage Is a Product Problem as what the engineer does not carry in.
What changes if the site has none of the four?+
The hire changes. You are hiring someone to build the site, so experience matters, which is what Francis says he does for small, early sites. The interview should test whether they have stood up a harness, an eval, and a handback loop before, and the offer has to reflect that.
Can you train a forward deployed engineer?+
Francis reports that a group of people building FDE organizations debated exactly this, and his answer was that Palantir doesn't hire ex-Palantir people and it still works. He credits culture and environment. I read that as: the site does the training, so the site has to exist first.


Sign in with LinkedIn to leave a comment.
Sign in with LinkedIn