Grokking the Forward Deployed Engineer Interview
Vote

0% completed

​

Forward Deployed Engineers, Solutions Architects, and Software Engineers

The Solutions Architect's Answer

The Product Software Engineer's Answer

The Forward Deployed Engineer's Answer

When Each Role Works

Comparing the Three Roles

Moving Between Roles

Using This in an Interview

Key Takeaways

Practice Questions

Title image: one customer request goes to three roles, and each role produces a different output.
Title image: one customer request goes to three roles, and each role produces a different output.

"We bought access to your model three months ago. Our own demo sends 1 claim in 4 to the wrong queue. We need our claims routed automatically."

This is the request from the car insurer in What a Forward Deployed Engineer Does. Three kinds of engineer at the AI company could answer it. A solutions architect would answer with a design, a product software engineer with a product change that every customer receives, and a forward deployed engineer with a working system inside the insurer. All three answers are useful, and none replaces the other two.

The Solutions Architect's Answer

A solutions architect (SA) is an engineer who helps a customer decide how to use a product, usually before or during the sale. For the insurer, an SA would run a two-hour workshop with the claims manager and engineers, then write a design. It names the systems that connect to the model, the path of the claims data, and how the six queues map to model requests.

The design also includes a cost estimate. At 1,200 claims a day, the insurer receives about 36,000 claims in a 30-day month, so the estimate prices about 36,000 routing requests plus a margin for retries and tests.

The SA writes little code, perhaps a short sample that sends one claim to the model. The insurer's engineers are expected to build the rest. For this insurer, a design alone would not have been enough, because a two-hour workshop rarely finds missing photos, scanned reports, and unwritten fraud conditions.

A similar role is the sales engineer, who demonstrates the product during the sale and answers technical questions. Both roles are measured partly by whether the customer purchases the product and keeps using it.

The Product Software Engineer's Answer

A product software engineer (SWE) builds and maintains the product that every customer uses, and rarely works with one customer directly. The product engineer learns about the insurer's request from the FDE's report and asks what change would help all customers, not only this one.

One answer is per-queue confidence thresholds. A confidence threshold is the minimum score a model suggestion needs before the system acts on it without a person. The product allowed one threshold for all requests, while the insurer needed one per queue. The product engineer builds that option once, tests it, and releases it to every customer. The next three insurance customers used it without custom code. The work is measured across all customers: whether the feature works, how many use it, and how often it fails.

The Forward Deployed Engineer's Answer

A forward deployed engineer (FDE) builds the working system for one customer, inside that customer's environment, after the sale. For the insurer, the FDE read 300 claims with the adjusters, tested a prototype on 2,000 past claims, piloted it on two queues, and handed the production system to the insurer's engineers. Routing work fell from about 100 to about 30 adjuster-hours a day. The FDE also sent three reports to the product team, including the one on per-queue thresholds.

Only the FDE's answer changes the customer's results directly. The design and the product feature both matter, but someone still has to connect them to this insurer's claims, rules, and people.

One customer request answered three ways: a design from the solutions architect, a working system from the forward deployed engineer, and a product feature from the product software engineer.
One customer request answered three ways: a design from the solutions architect, a working system from the forward deployed engineer, and a product feature from the product software engineer.

When Each Role Works

The SA works mostly before and during the sale. The FDE works after the sale, during an engagement of weeks or months. The product engineer works on the product continuously, so a change one customer requests is usually released months later.

The roles also depend on each other. The SA's design is an input to the FDE's discovery, which checks it against real data. The FDE's reports are an input to the product plan. When both handoffs work, one customer's problem becomes a feature that later customers receive without an engagement.

When each role works with the insurer: the solutions architect before the sale, the FDE during the six-week engagement, and the product engineer after it, with the FDE's reports going to the product team.
When each role works with the insurer: the solutions architect before the sale, the FDE during the six-week engagement, and the product engineer after it, with the FDE's reports going to the product team.

Comparing the Three Roles

Solutions architectForward deployed engineerProduct software engineer
ServesOne customer at a time, often before the saleOne customer at a time, after the saleAll customers of the product
Main outputDesigns, estimates, and recommendationsA working system in the customer's environmentProduct features and fixes
Code writtenLeastA lot, mostly customer-specificA lot, shared by every customer
Customer contactMany customers, brieflyOne customer, almost dailyRare
Measured bySales and customer adoptionThe customer's results in productionProduct quality and use
Common failureA design the customer cannot buildA custom system only its author understandsA feature that no real customer needed

Each failure in the last row comes from doing one part of the work without the other roles.

Moving Between Roles

Many FDEs come from one of the other two roles. A software engineer already has coding, testing, and production habits. The new skills are discovery, explaining tradeoffs to people who are not engineers, and accepting a smaller scope, such as a two-queue pilot.

An SA or sales engineer already has discovery and communication skills. The new skills are writing and debugging production code and staying responsible for the system until the handoff. A design could name an extraction step, but the FDE also had to write it, measure it on 2,000 past claims, and fix it when scanned reports read poorly.

Using This in an Interview

Interviewers often ask why you want this role rather than a software engineer or SA role. Answer with the difference in output, supported by one event from your own work:

"As a product engineer, I built features for thousands of users, but I rarely saw whether they solved a customer's problem. The most useful week of my last job was the week I spent with one customer, fixing an import that failed on 1 file in 5. I want to write production code and also see the customer's result. A solutions architect role would give me the customer, but not the code."

Expect two follow-up questions:

  • "Why not stay a software engineer and talk to customers more often?" The FDE is responsible for one customer's result, and talking to customers more does not change what a product engineer is measured by.
  • "Which part of the FDE job do you expect to find hardest?" Name one real gap, such as discovery with people who are not engineers, and say how you are preparing for it.

For a shorter summary, read Forward deployed engineer vs. solutions architect vs. software engineer.

Key Takeaways

  • A solutions architect helps a customer decide how to use a product before the sale and produces designs and estimates.
  • A product software engineer builds the product every customer uses and rarely works with one customer directly.
  • A forward deployed engineer builds the working system for one customer after the sale and is measured by that customer's results.
  • The roles depend on each other, and each role's common failure comes from working without the others.

The next lesson, The Customer Engagement Lifecycle, describes the stages of an FDE engagement.

Practice Questions

1. A customer asks for an architecture and a monthly cost estimate before signing a contract. Which role usually does this work, and why?

<details><summary>Show answer</summary>

A solutions architect, because the work happens before the sale and its output is a design. An FDE usually starts after the contract is signed, when there is a system to build.

</details>

2. The FDE's system already used a separate threshold for each queue. Why did the product team build per-queue thresholds as well?

<details><summary>Show answer</summary>

Because the FDE's version existed only in custom code for one customer. As a product feature, the option was built and tested once, and the next three insurance customers used it without custom code.

</details>

3. An FDE spends six weeks with a customer and delivers a detailed design document, but no working system. Which role did the engineer actually perform?

<details><summary>Show answer</summary>

The engineer acted as a solutions architect or consultant, not as an FDE. The FDE is measured by the customer's results in production, and after six weeks those results have not changed.

</details>

Reading Progress

0%


Vote for new content

On This Page

The Solutions Architect's Answer

The Product Software Engineer's Answer

The Forward Deployed Engineer's Answer

When Each Role Works

Comparing the Three Roles

Moving Between Roles

Using This in an Interview

Key Takeaways

Practice Questions