0% completed
Solutions Architects, Sales Engineers, and Forward Deployed Engineers
On This Page
Five Customer-Facing Roles
The Roles in One Engagement
How the Roles Compare
Generalist and Specialist SAs
Choosing Between the Roles
Using This in an Interview
Key Takeaways
Practice Questions
Vendors employ engineers whose main work happens with customers rather than on the vendor's own product. Some help a customer decide to buy, which is pre-sales work. Others help a customer succeed with what it bought, which is post-sales work. A few roles do both.
Job titles do not follow these lines consistently. The same work is called solutions architect at one company, customer engineer at another, and solutions engineer at a third. This lesson compares the roles by the work they do, so that you can read a job description and know what the job is.
Five Customer-Facing Roles
The roles differ in three ways: who employs the engineer, when they work with the customer, and whether they write the customer's production code.
Solutions architect. An SA designs the customer's solution on the vendor's platform and stays involved until it runs in production. At large cloud providers, SAs often work with a set of customer accounts across both pre-sales and post-sales.
Sales engineer. A sales engineer, also called a solutions engineer or, at Google Cloud, a customer engineer, supports the sale itself. The work centers on demonstrations, answers to technical questions, security questionnaires, and short proofs of concept. Some companies use these titles for work that is identical to an SA's, so read the job description, not the title.
Forward deployed engineer. A forward deployed engineer (FDE) works inside the customer's environment and writes production code there, such as data pipelines, integrations, and AI applications. The role is common at data and AI companies, where the customer's data and processes need custom software before the product is useful.
Technical account manager. A technical account manager (TAM) supports a customer after the sale. The work centers on operations: support cases that need escalation, planned events, and regular reviews of how the customer's systems run.
Enterprise or cloud architect. This architect works for the customer, not for a vendor. They set the standards that the customer's teams follow and decide which vendors to use, so they are often the person whom the vendor's SA works with most closely.
The Roles in One Engagement
The retailer's engagement shows when each role appears. The diagram places the five roles along the 15 months.
Notice three things in the diagram:
- The SA is present from the first call to the last server. The sales engineer ran the first product demonstration, but the SA led discovery, the design, and the proof of concept.
- The TAM appears after the first wave goes live. From then on, the retailer's engineers have production systems that need support during the holiday sale.
- No FDE was needed. The retailer had 12 engineers who could build and run the platform once they were trained. An FDE fits when the work needs custom code that the customer cannot write, such as connecting an AI model to scattered internal data.
The retailer's own architect appears throughout, because every design decision needed their agreement.
How the Roles Compare
| Role | Employer | Main output | Writes customer production code |
|---|---|---|---|
| Solutions architect | Vendor | Designs, proofs of concept, migration plans | Rarely; samples and prototypes |
| Sales engineer | Vendor | Demonstrations and technical answers | No |
| Forward deployed engineer | Vendor | Working software in the customer's environment | Yes |
| Technical account manager | Vendor | Operational reviews and escalations | No |
| Enterprise architect | Customer | Standards and vendor decisions | Sometimes |
The columns describe the most common form of each role. A small company may combine the SA, sales engineer, and TAM into one job.
Generalist and Specialist SAs
Large vendors employ two kinds of SA: generalists who own the relationship with a set of customers, and specialists who are called in for one technical area. Common specialist areas are data and analytics, machine learning and generative AI, security, networking, databases, and migration.
In the retailer's case, the generalist SA owned the engagement and asked a database specialist to review the plan for moving the order database. The specialist joined for two meetings and one review, and then returned to other customers. Specialist interviews usually go deeper in their area, while generalist interviews test breadth and customer skills more heavily.
Choosing Between the Roles
Each role suits a different kind of engineer. The following questions help you decide which one to apply for:
- If you most enjoy designing systems and explaining trade-offs, the SA role fits best.
- If you most enjoy demonstrations, persuasion, and short sales cycles, the sales engineer role fits best.
- If you want to keep writing production code every day, the FDE role fits best.
- If you prefer operations and long relationships after launch, the TAM role fits best.
For the FDE role, which this course does not cover in depth, see Grokking the Forward Deployed Engineer Interview.
Using This in an Interview
Interviewers often ask why you want this role rather than an engineering or a sales role. Answer with the work you want to do, and support it with something you have done.
"I want to spend most of my time on design decisions with customers rather than on one product's code. In my current team, I led the design review with our largest client's architects, and their questions changed our plan. That conversation was the part of the project I did best, and it is most of an SA's job."
Expect two follow-up questions:
- "Will you miss writing code?" Say honestly how much you will code, such as prototypes and proof of concept code, and why that amount suits you.
- "How is an SA different from a sales engineer here?" Ask the interviewer how their company divides the work, then explain how your experience fits that division.
Key Takeaways
- Pre-sales roles help a customer decide; post-sales roles help it succeed with what it bought.
- Titles vary between companies, so read the work described, not the title.
- The SA usually stays from discovery to production; the FDE writes the customer's code; the TAM supports operations.
- Large vendors use generalist SAs for customer relationships and specialist SAs for depth in one area.
The next lesson, How a Customer Engagement Reaches Production, follows the retailer's engagement through each stage.
Practice Questions
1. A job posting is titled "Customer Engineer" but describes architecture design, discovery workshops, and migration planning. Which role is it?
<details><summary>Show answer</summary>It is an SA role with a different title. The work described is design and discovery across the engagement, which is the SA's work. Prepare for the rounds that test those skills.
</details>2. Why did the retailer not need a forward deployed engineer?
<details><summary>Show answer</summary>Because its own engineers could build and run the platform after training. An FDE is needed when the work requires custom code that the customer cannot write. The retailer's migration needed design and training more than custom software.
</details>3. A specialist SA and a generalist SA interview for the same company. How will their interviews probably differ?
<details><summary>Show answer</summary>The specialist's interview usually goes deeper in one area, while the generalist's tests breadth and customer skills. Both are tested on communication. A specialist should still expect questions outside their area, because their designs connect to the rest of the customer's systems.
</details>Reading Progress
0%
On This Page
Five Customer-Facing Roles
The Roles in One Engagement
How the Roles Compare
Generalist and Specialist SAs
Choosing Between the Roles
Using This in an Interview
Key Takeaways
Practice Questions