Hiring FDEs: When to build in-house and when to partner

Written by
Last updated on:
November 16, 2026

Once you know you need forward-deployed engineers, the next question is where they come from. Here's how to weigh a full-time hire against a partner, and when it makes sense to do both.

Deciding that a project needs a forward-deployed engineer (FDE) is the first step. Deciding how to hire FDE talent is the second, and it's often harder. The role was popularized by Palantir, founded in 2003, and it mixes senior engineering with customer-facing work. That combination is hard to find, and few candidates have both.

You can build the capability in-house by hiring FDEs as employees, or you can bring in FDEs from a partner who works inside your team for as long as you need them. Both can work. They differ on cost and speed, and on who holds the knowledge once the project is live.

The market makes the choice more pressing. AI companies including OpenAI, Anthropic, and Cohere are rapidly expanding their own FDE teams, according to eWeek, so more companies are competing for the same candidates.

New to the role? Read Five things to know about forward-deployed engineers.

In-house FDEs vs. an FDE partner: How do they compare?

In-house FDE vs FDE from a partner: time to start, cost structure, commitment, knowledge, experience, and main risk
ComparisonIn-house FDEFDE from a partner
Time to startA full hiring cycle, often months for a rare skill setUsually days to weeks, from an existing bench
Cost structureSalary, equity, benefits, and recruiting costsA rate for the engagement, with no recruiting costs
CommitmentLong-term, with a permanent role to fillFlexible: scale up, swap, or stop
Who holds the knowledgeStays in your companyHas to be handed over before the engagement ends
Experience across deploymentsGrows over time inside your companyBrings lessons from other clients' projects
Main riskA slow or wrong hire for a role you're still definingDependence on the partner if handover is weak

The short version is that hiring full-time builds lasting capability, and a partner gets you moving faster with less commitment.

When does hiring a full-time forward-deployed engineer (FDE) make sense?

A full-time hire is the stronger choice when FDE work is part of how your company will operate for years, not a one-off project. It’s usually the right call if:

  • You have a steady pipeline of FDE-style projects. If one deployment will lead straight into the next, a permanent role pays off.
  • The work is core to your business. If the systems an FDE builds will set your product apart for customers, you'll want that knowledge to stay in-house.
  • You can wait. Recruiting someone with both deep engineering skills and customer-facing judgment takes time, especially with demand rising across the market.
  • You know what the role looks like. You've done this work before and can write a clear job description with real responsibilities.

Budget for the full cost, too. FDE job postings show a median base salary of about $174,000 before equity, according to Bloomberry's analysis of 1,000 FDE job postings, and benefits and recruiting come on top of that. In the USA, you'll also be competing in the same market as AI companies like OpenAI and Anthropic, both based in San Francisco, California, which have their own FDE teams.

Before you post the position, write the job description around real responsibilities, not just a title. That usually means discovery with business teams, building on your own data, and production skills like retrieval-augmented generation (RAG), analytics pipelines, and integration with existing systems. Decide early whether the role is remote or office-based, since FDE work depends on close collaboration with the people who'll use what they build.

For a broader look at hiring routes, read Three ways to hire software engineers.

When does an FDE partner make sense?

A partner is usually the better fit when speed matters more than permanence, or when you're still learning what you need. Look for these signs:

  • You need to start soon. A stalled AI pilot or a deadline won't wait for a months-long search, and a partner can usually have engineers ready to deploy within weeks.
  • You don't know yet if you need the role long term. A partner lets you test the FDE model on one project before you create a permanent position.
  • You want experience from other deployments. A partner's FDEs have likely solved similar integration and analytics problems for other clients, and they can deploy those capabilities on your project quickly.
  • You want an easy way out. If the fit isn't right, a partner can swap the engineer or end the engagement without a difficult conversation about a permanent role.

The trade-off is knowledge. When the engagement ends, what the FDE learned leaves with them unless you plan the handover. Make documentation and training part of the contract from the start, along with regular collaboration with your team.

What about an AI vendor's FDEs?

Some AI companies now offer their own FDEs. According to eWeek, OpenAI set up its FDE team at the start of 2024, and Anthropic planned to grow its applied AI team, which includes FDEs, fivefold. A vendor's FDEs know its platform well, but their job is to make that vendor's product work for its customers, and access may depend on the size of your account. If your solution spans several models or tools, or depends on your own data, an independent partner can work across all of them.

Can you start with a partner and hire later?

Yes, and it can be the lower-risk path. A partner's FDE can get the first project into production while you learn what the role actually involves in your organization and which capabilities your team should keep building.

That experience also helps you shape the role and makes a later hire easier. You'll know which skills mattered, how much of the work was engineering versus discovery, and whether you have enough projects to justify a permanent role. Your job description gets sharper, and the new hire inherits a working system with documentation, not a blank page.

The key is to plan for that transition from the beginning. Ask the partner to document decisions as they go and pair with your engineers, so ownership can move to your team before the engagement ends.

Questions to ask before you decide

  • How many FDE-style projects will we have in the next two years? One or two points to a partner. A steady stream points to hiring.
  • How soon do we need results? If your priorities call for results this quarter, a full-time search probably won't get you there.
  • Who will own the system after launch? If it's your team, plan the handover whichever option you choose, and involve the people who'll run it early.
  • Do we know what good looks like? If you can't yet write the job description, a partner can help you find out.

The same questions apply whether you hire FDE talent directly or through a partner. Answering them first makes the decision clearer for your team and helps you set priorities.

How to evaluate an FDE partner

If you go the partner route, look for evidence rather than titles. As the FDE role has grown, some providers use the title for ordinary staff augmentation. Ask:

  • How do you vet your FDEs? Look for assessments on production engineering and enterprise integration, and ask whether you can see the results.
  • What is the engineer accountable for? Real FDE work ties success to a business result, not hours billed.
  • What happens if the fit isn't right? Clear trial terms lower your risk, so you can be confident before you commit.
  • How does handover work? Ask how the partner makes sure your team can run the system after the engagement ends.

For a full checklist, download our Forward-Deployed Engineer Guide.

Working with FullStack's forward-deployed engineers

If a partner fits your situation, you can hire forward-deployed engineers through FullStack. Our FDEs are senior nearshore engineers who work in your time zone, whether your team is remote or office-based, and each one is assessed on skills like production code and enterprise integration before joining a client team. You can review the recorded coding challenge and interviews yourself.

We send a shortlist of engineers ready to start within 48 hours of your first call, and the first two weeks are free. If it isn't working, we swap the engineer or stop, and you don't pay for those weeks.

Want to see if an FDE is the right fit? Talk to our team about your project.

Learn more

Frequently asked questions

Hire full-time if you have a steady pipeline of FDE-style projects and the work is core to your business. Use a partner if you need to start soon, aren't sure you need the role long term, or want to test the FDE model on one project first. The right fit depends on your priorities and how ready your team is to own the work.

FDE job postings show a median base salary of about $174,000 before equity, according to Bloomberry's analysis. Benefits and recruiting costs come on top of that. A partner charges a rate for the engagement instead, with no recruiting costs.

A full-time search can take months, because the role needs a rare mix of engineering and customer-facing skills. A partner can usually start much sooner. FullStack, for example, shares a shortlist within 48 hours of the first call.

That depends on the partner's contract terms, so ask up front. Either way, a partner engagement can help you define the role and build documentation before you make a permanent hire.

The main risk is losing knowledge when the engagement ends. You can reduce it by making documentation and a planned handover part of the agreement.