By the end of this lesson you will be able to tell the FDE role apart from product SWE, solutions engineering and consulting, and spot the consultant trap.
By the end of this lesson you will be able to tell the FDE role apart from product SWE, solutions engineering and consulting, and spot the consultant trap.
Every deployment is hand-built. Ask: "How do I make this the last time anyone builds this by hand?"
At Brightline, Dana Ruiz will ask you to build things no other customer needs. Whether you say yes, and how, depends on which job you're actually doing.
Four roles sit close to the customer and all of them write some code, so the titles blur. What separates them is what each is measured on, and that decides how you'd answer Dana.
| Product SWE | Solutions / Sales Engineer | Consultant | FDE | |
|---|---|---|---|---|
| Primary goal | Product for all customers | Win the deal | Deliver a statement of work | Make this customer successful, and improve the product |
| Who sets the work | Roadmap | Sales cycle | Contract | Customer outcome + company strategy |
| Production code? | Yes | Mostly demos | Sometimes | Yes, in the customer's environment |
| Time horizon | Quarters | Weeks (pre-sale) | Fixed project | Months, through and after go-live |
| Success metric | Features, reliability | Revenue closed | Delivered on time | Customer metric moved, expansion, product insight |
vs. product SWE. They build for everyone; you build what this customer needs by Friday, then hand them the pattern ("five customers built the same CSV importer"). A product engineer who ships a feature one customer needs has made the product worse for everyone else. You ship it at the customer, in their environment, and then decide whether it belongs in the product.
vs. solutions engineer. SEs work before the contract, proving the product can solve the problem. FDEs work after, proving it does, in production. A demo can cut corners a deployment can't. The SE's demo of fax extraction used ten clean sample faxes. Your deployment meets the handwritten ones, the stapled packets and the 2 a.m. outage.
vs. consultant. Consultants deliver the contract and leave. FDEs represent a product company: the goal is renewal, expansion, and lessons that make the next deployment faster. A bespoke system only you understand is a failure, even if the customer is happy today.
The consultant trap: if every deployment needs custom code that never reaches the product, your company becomes a services business. Ask, "How do I make this the last time anyone builds this by hand?"
The diagram shows why this matters commercially. At 0% fed back, deployment eight costs as much as deployment one, so headcount grows with every customer. Feed even half the repeated work back and later deployments get noticeably cheaper. That gap is the difference between a software margin and a services margin.
Dana asks for a custom export of reviewed referrals in her billing team's spreadsheet format. A consultant builds it and bills for it. A product SWE says it's not on the roadmap. An FDE does three things:
PRODUCT FEEDBACK — <date>
Pattern: <what customers keep needing, in one line>
Seen at: <customer 1>, <customer 2>, <customer 3>
Workaround: <what the FDE built, where it lives>
Cost: <engineer-days per deployment>
Ask: <the smallest product change that removes the workaround>
For this customer, probably yes: copy it and keep the date. But stopping there is the consultant trap. The FDE move is to also file the pattern with the cost ("three deployments, about four days each") and push for it to become a product feature or a supported template, so the fourth deployment doesn't need you at all. Doing the work and never feeding it back makes every future deployment as expensive as this one.
You will do some of each job. In week one you may run a demo on sample faxes, which is solutions-engineer work. In week three you may write a statement of work for phase 2, which looks like consulting. Late in an engagement you may pair with a product engineer to turn your workaround into a feature. That's fine. The test is what you're accountable for at the end: if it's Brightline's intake time and the lessons your product team took away, you're doing the FDE job, whatever the task on a given afternoon.
Engineering, customer success (risk: a ticket queue) or a dedicated deployment org (often healthiest). Reporting line shapes what you're rewarded for. Under customer success, you may be measured on tickets closed; under engineering, on code shipped; in a deployment org, on customer outcomes and product insight, which is the job.
In interviews ask: "How does deployment feedback reach the roadmap? Give me a recent example." A strong answer names a feature that started as an FDE workaround. A weak answer ("we have a Slack channel") tells you the consultant trap is likely.
Something like: "I want to be accountable for the result in production, not just for showing it's possible. I want to be the person who finds out what breaks on real data and turns that into product." It names the after-the-sale ownership and the feedback loop, the two things that separate the roles.
Cheat card
- Product SWE builds for all customers; SE proves the product can work before the sale; consultant delivers a contract; FDE makes this customer succeed after the sale and improves the product.
- The consultant trap: custom work that never reaches the product turns a software company into a services business.
- Before taking an FDE job, ask how deployment feedback reaches the roadmap, with a recent example.
Pattern / Seen at (3 customers) / Workaround / Cost in engineer-days / Smallest product changeInterview line "I'll build what this customer needs by Friday, and I'll write down the cost so the third time we see it, it becomes a product feature instead of my weekend."