- FDE and solutions engineer are roles, and professional services is a delivery arrangement that can employ either of them.
- The deciding question is how long technical ownership has to last after the customer goes live.
- A phase boundary nobody wrote down falls to whoever is closest to the customer, which is the FDE.
- Compare the models on what you can observe after delivery, not on a return-on-investment claim neither side can check.
- Name what each model needs from you: engineering support and customer access, or scope control, or a way to validate fit honestly.
Start with the work
An FDE fits when the role combines technical delivery with close contact with the operating team: translating an unclear problem, building or adapting software, testing it in the real environment, and staying through production use.
A solutions engineer fits when the main responsibility is helping a prospective customer decide whether the product fits. If someone must own a production system after the sale, the job description should say who, and when the responsibility changes hands.
A professional services team can deliver implementation, engineering or advisory work, internally or through a partner. Databricks lists an FDE role within professional services that combines customer delivery, architecture, production systems and reusable components.
Six questions for the planning meeting
- Is the main work before a purchase decision, during implementation, or after production launch?
- Who can build a durable integration when the standard workflow does not fit?
- Who is accountable for reliability, security, monitoring and rollback after launch?
- Does each customer need a different technical solution, or can one service package cover most cases?
- Who owns feedback about repeated customer problems, and how does it reach product and engineering?
- What must be true before a customer can operate without the original delivery team?
Write the boundary into the plan
| Phase | Primary owner | Required handoff |
|---|---|---|
| Problem definition and technical fit | Solutions engineering or FDE | Written constraints, success measure, open risks |
| Integration and first release | FDE or professional services | Tested configuration or code, runbook, rollback path |
| Production operation | The named product, engineering or customer team | Monitoring, support path, owner for changes |
| Product feedback | The team closest to repeated problems | Specific evidence, affected workflow, proposed decision |
One person can hold several of these in a small company. The risk is leaving the boundary implicit. If a role is expected to sell, design, build, operate and support every customer indefinitely, put that trade-off in the capacity plan.
The measures worth tracking
Track time from discovery to first working release, rework caused by unclear requirements, incidents after handoff, support requests, adoption, and recurring product issues. Define each measure before comparing teams. A posting count cannot show any of them.
Compare the conditions each model needs as well. An FDE role needs engineering support, access to customer systems, travel, and a clear escalation path. A services team needs scope control and delivery management. A solutions engineering team needs a way to validate fit without promising work the delivery team cannot own.