Three job titles. Enormous overlap. Constant confusion.
If you're trying to build out technical client-facing headcount and you're not sure whether to hire a Forward Deployed Engineer, a Sales Engineer, or a Solutions Consultant, you're not alone. Most hiring managers get this wrong at least once.
Here's how to think about it.
Sales Engineer (SE)
The SE lives in the sales cycle. Their job is to win deals.
They partner with Account Executives, run technical demos, answer the hard questions from the customer's engineering or security team, and manage proof-of-concept engagements. When a deal has a technical blocker, the SE removes it.
A good SE understands both sides of the table. They're technical enough to be credible with engineers, and commercial enough to keep the conversation focused on outcomes. The best ones can shift register mid-call — going from API documentation to business ROI in the same breath.
SEs are measured on revenue contribution. Their success is tied to closed deals and pipeline progression. They're a sales resource.
Typical home: Reporting into Sales or Revenue.
When you hire one: When you have a complex product and a long sales cycle, and your AEs need a technical co-pilot. Usually from mid-Series A onwards.
Forward Deployed Engineer (FDE)
The FDE comes in after the deal is won, or late in the sales cycle when the customer needs to see the product working in their environment before they'll commit.
Their job is implementation and integration. They get into the customer's stack, write real code, and make the product work in production. They're engineers first. They just happen to work at the customer interface.
The FDE model came from Palantir, where the product was so complex and the customer environments so specific that standard onboarding couldn't cut it. You had to put engineers on-site. The model has since spread to AI companies, data platforms, and anything where the technical lift of deployment is significant.
FDEs are not running demos. They're building things. Integrations, custom configurations, bespoke tooling. They measure success by customer outcomes: time to value, adoption, expansion.
Typical home: Reporting into Engineering, Customer Success, or a dedicated Solutions Engineering function.
When you hire one: When your product requires real technical implementation work to get value, and customers have complex existing environments. Often relevant from Series B as you move upmarket.
Solutions Consultant (SC)
The Solutions Consultant is the trickiest of the three to pin down, because the title is used inconsistently across the industry.
In most organisations, an SC sits somewhere between the SE and the FDE. They're pre-sales or early post-sales, working with customers to design the technical solution before and during implementation. They're strong on architecture and business process. They tend to be less focused on writing code than an FDE, and less focused on the raw sales cycle than an SE.
Think of them as the person who takes a customer's business requirements and maps them to your product's capabilities. They produce solution designs, lead workshops, and guide the customer through how the platform should be configured and rolled out.
Typical home: Pre-sales, Professional Services, or Customer Success.
When you hire one: When your deals involve complex requirements gathering, multi-stakeholder alignment, or a significant configuration and deployment effort. More common in mid-market or enterprise segments.
How They Overlap
All three roles are technical and customer-facing. All three require communication skills that most engineers don't have. All three end up in customer conversations that a standard product engineer would find uncomfortable.
At smaller companies, one person often covers all three. Your first SE is probably also doing FDE work and solutions consulting. That's fine early on, but it's not a scalable model.
As the company grows, the roles split apart. Sales stays pre-sales. FDEs own technical deployment. SCs bridge the two.
Which One Do You Need?
Are deals stalling on technical questions? Hire an SE.
Are customers struggling to implement and get value post-sale? Hire an FDE.
Are you selling a complex solution that requires significant requirements gathering and design work? Hire an SC.
Are you a 15-person startup with limited budget? Hire an SE who can stretch into the other two, and be honest about it in the job spec.
The mistake most founders make is conflating these roles and writing a job description that asks for all three at once. You'll either attract nobody, or attract someone who is average at all three rather than excellent at one.
Know what you actually need. Then hire for that.