The why is well covered by now. Enterprises buying AI often know what they want it to do, but most of them can’t wire it into their own systems and workflows without help. That gap is exactly why companies selling complex AI products keep ending up with a forward-deployed function whether they planned for one or not, and why the role has gone from niche to increasingly unavoidable in the space of a couple of years.

There’s broad agreement, too, on what a good FDE looks like in the abstract: high agency, genuinely curious and comfortable ignoring the way things are normally done in favour of whatever gets things live.

But none of that tells you how to actually go and hire one. Agreeing on the profile is the easy part. Finding someone who matches it, proving they do before you commit and getting them to choose your seat over the several others they could take instead, is where almost everything written about this role goes quiet.

Half engineer, half consultant, full owner

The job description undersells it. A typical week combines customer discovery, sitting with stakeholders from line analysts to CTOs to find out what the problem is, with production code, the pipelines, integrations and custom services that make the deployment real.

Add system design under constraints most engineers never touch, SSO, VPCs, compliance regimes, legacy systems never built to talk to anything new, being the one who gets paged when it breaks at 2am and feeding what they learn back to the product team so the next customer doesn’t need their own one-off fix. The job is finished when the customer renews, not once the demo works.

Founders and hiring leads who’ve made this hire tend to say some version of the same thing: more than a harder version of a normal engineering hire, this is a different shape of hire entirely, and most processes just aren’t built to find it.

The role doesn’t have one bar. It has three

A normal engineering hire tests for one thing well: can this person build. An FDE hire needs to test for three things simultaneously, at a senior level, in the same person:

• Technical depth strong enough to own a production system inside someone else's infrastructure.
• The discovery and customer-facing judgement to understand what the customer really needs before building anything.
• And the composure to do all of that while a customer is watching, asking questions, and occasionally panicking.

Previously, job postings weren't necessarily consistently asking for strong core engineering. They were asking for sales. There were more commercial roles.

That's flipped in the last six months. Increasingly, the ask is now real AI fluency and fundamental engineering skills, and companies are testing harder for it. It's still an FDE role, but it's very much a software engineering FDE role.

Few processes are built to assess all three with the same rigour, and there's a specific reason the imbalance tends to run one way. Engineering expertise is what's newly in focus, and it's also what a hiring manager already knows how to test properly, so that’s where attention naturally goes. Startups and scaleups are often prioritising this bit, but the risk is that the discovery and customer-facing side gets far less scrutiny by comparison, mostly because it's harder to test and easier to assume it'll show up on its own.

The candidates who can do this aren’t applying just anywhere

The people who can genuinely do all three parts of this job are rare, and they’re not short of options. They’re usually deep inside a team somewhere, well compensated, and not reading job boards. Posting the role and waiting assumes these people are looking. They’re not.

The job is knowing who they are before you start, and making the opportunity land when you reach them directly, since you’ll likely only get one real conversation with each of them.

The fastest way to fail this hire is to take an existing solutions engineer or implementation lead, relabel them FDE, and expect the role to do the rest. The title doesn’t create the capability. The market hasn’t even settled on what to call this role in the first place. Forward Deployed Engineer, Solutions Architect, Deployment Engineer, Technical Program Manager. The same job often sits under at least half a dozen labels depending which company you ask.

A title that means six different things at six different companies was never going to tell you whether someone can do this specific version of the job. Companies that get this right define what the role needs to do for their specific customers and product before they touch a job spec, then hire against that, rather than against the title.

Specific beats agreed on

None of this means the FDE hire is impossible. It just means it needs a different starting point than most companies give it.

Everyone agrees on the headline profile by now. High agency, genuinely curious, the kind of person who’ll ignore the usual way of doing things if it gets the customer to a working product faster. That description is accurate, and it’s also not enough to hire against, because half the market is using the exact same three words and still struggling to fill the role.

Start by being specific about what your version of this role requires. Not the generic FDE description that’s circulating everywhere right now, but what your customers, your product and your stage actually demand of the person sitting in that seat.

Some companies need someone who can architect against legacy infrastructure. Others need someone who can hold their own in a room with a sceptical technical buyer. Few need all three at the same intensity, and knowing which matters more changes who you need to be looking for.

Then assess for all three parts deliberately, and source the way you would for any role where the right people aren't applying: directly, with a clear and specific story about why this particular seat is worth leaving something good for.

Exceptional isn't fixed for this role any more than it is for any other. It depends on what you actually need this person to do, for your customers, in your environment. Get that right first, and the rest of the search gets much easier.