The unsung heroes of chip sales: field application engineers

Jay Goldberg

Posts: 99   +2
Staff
Editor's take: In our ongoing exploration of the business of selling compute systems, we found that there is a giant blind spot in how the sales process actually works. Sales support engineers, sometimes also called Field Application Engineers, can be an incredibly valuable resource for any company selling technical products. Unfortunately, many companies fail to fully appreciate their importance.

Picture this: A chip vendor has a shiny AI accelerator, but how do they actually get that into the hands of their shiny hyperscaler customer? A key part of that process is the Sales Engineer. These people go by many titles – Field Solutions Engineer or Sales Support Engineer, but we have always known them as Field Application Engineers (FAE).

These are engineers deeply immersed in the intricacies and configurations of the chips their company sells. They do not design the chip but help customers make the most of those chips.

Editor's Note:
Guest author Jonathan Goldberg is the founder of D2D Advisory, a multi-functional consulting firm. Jonathan has developed growth strategies and alliances for companies in the mobile, networking, gaming, and software industries.

Getting a new chip to work is always a challenge for a customer. Spend some time building a PC, and the problem becomes obvious very quickly. Now subtract a common firmware system and 1,000 how-to YouTube videos to walk through every bug, and multiply the complexity by a few orders of magnitude.

The role of Field Application Engineers is to solve those problems – to provide software tools, configurations, and bug fixes that get systems up and running. Longer-term, they help customers design methods for scaling those chips into complete systems and then racks and rows of compute. This is an invaluable resource to customers and can make the difference between a busted demo and a committed purchase order.

Today, every hyperscaler hardware team is bombarded by literally dozens of AI chip solutions. Everyone on the team has a friend, cousin, or former roommate pitching them on some new chip. As such, these teams are loathe to let another salesperson in the door. They do not need any more PowerPoint presentations showing all the ways some chip is 30% more power efficient or 10x better on some random benchmark.

But a knowledgeable FAE who can solve actual problems is always welcome. The biggest value the FAE can bring a chip company is the fact they will always be welcome for customer visits.

To say this value is not always appreciated is a major understatement. Few outsiders are even aware of the role. More problematic is that most chip companies do not fully value FAEs or really understand their role.

A big part of the problem is that FAEs do not fit neatly into company org charts. There is considerable conflict within organizations. Every engineering team is chronically short-staffed, so it is painful to see talented engineers "wasted" on sales.

In fairness, organizing an effective sales support team is a complicated balance. For an FAE to be effective, they need to understand the inner workings of the chip almost as well as the engineers who design the chip. The only way to achieve that is for the design engineers to spend time educating the FAEs (or at least closely document their work for later reference). That, of course, takes time away from them actually designing the chip.

There is no easy way around this trade-off, and management teams just need to make the strategic calculation around FAEs' value. On the other hand, FAEs need to be motivated to direct their efforts in the right direction. Often FAEs end up getting pulled in every direction at once. Here, at least, there is a solution – FAEs need to participate in sales quotas and share in commissions. For what it's worth, this is often a great career move for FAEs, positioning them to move into sales, into engineering, or often a move to the customer.

We have recently been doing a lot of work around this area and on this role. While few companies have perfected it, the good news is that there is significant flexibility in how it can be approached. There may not be a single perfect way to structure this role, but companies have ample opportunity to develop a model that works best for their specific needs.

Permalink to story:

 
This was kinda freaky to read....
As a Business Systems and Solution Analyst, my role was an almost identical situation to the above... I was part of the sales process for selling both software and hardware solutions to business' and I had to understand BOTH ends of the process.
I needed to know the software intricately, ALMOST down to the code level and all its capabilities and customisation options, AND I had to know the industry needs we were targeting, right down to the user experience (ironically, it was working with the end users and the processes they needed that I enjoyed the most, coming up with novel and out of the box ways of streamlining their processes)
The best time in my career was when I permanently transitioned to Health Systems and Solutions for medical centres, hospitals and pathology labs, and getting to work with real pathologists, nurses, doctors and even in some cases, patients, to customise and delivber systems and processes for the relevant medical area (I was the lead Analyst on the HPV Vaccination Programs and the Bowel and Breast Cancer Research Centre here in Australia - best feeling ever).
I'm (semi)-retired now, but the above brought a lot of nostalgic and positive memories thinking of all the people I helped (in a tangential roundabout way...)

PS. Great article - I understand the difficulties fitting the role into the business. The Business Systems Anaylyst was often faced with the same issue. Where to fit us in on the org chart... the customer facing sales end, the IT division, where to put us? (most often placed with 1 foot in each department, forcing us to be in the frustrating position of having 2 bosses, and often conflicting directives from both...)
 
Last edited:
I’m a “Project Consultant” but I’m always getting involved exactly like in this article. Sales person goes in, sells them on a firewall, I then get involved to see how we can integrate it and work closely with the client to find solutions to potential issues, or work out changes to their work flows.

It does feel like a thankless job, sales guy makes all the commission, I have to actually do everything and spend all my time with the client.
 
It does feel like a thankless job, sales guy makes all the commission, I have to actually do everything and spend all my time with the client.
I can understand how you feel, however, consider that if it wasn't for the salesman making the sale in the first place, you might not have that thankless job at all.
 
Typically, a semiconductor organization has internal application engineers reporting to the product line and field application engineers reporting through the sales organization. The product line apps engineers train the field apps..not design ;)

Think of it this way, the FAEs are the voice of the customer and the internal apps guys are the bridge between design and the customer.
 
Back