FDE vs solutions architect: the real differences
Updated
Diagrams versus running systems: where the architect role ends, where FDE delivery starts, and how to choose.
Both roles face customers and both design. The split is what each one is measured by: approved diagrams or operating systems.
The short answer
Architects are measured by decisions that many teams follow. FDEs are measured by one customer system that runs, with numbers and a handover package to prove it.
The decision table
| Axis | Solutions architect | Forward deployed engineer |
|---|---|---|
| Main artifact | Architecture decisions, diagrams | Running system plus runbook |
| Time horizon | Quarters, portfolios | Weeks, slices with stop lines |
| Code | Reviews and prototypes | Ships the slice personally |
| Production duty | Advisory | Named owner until handover |
| Success proof | Adoption of the pattern | Outcome metric on a date |
Worked example: the same engagement, two seats
A fictional retailer (fictional) needs returns lookup. The architect produces the target diagram, data rules and review gates used by three teams. The FDE takes one team through discovery, ships the lookup page, survives security review, and hands over the runbook tested by a non-author. The company needs both; the careers reward different proof. The delivery loop post shows the FDE half; the handover post sets the test an architect-turned-FDE must pass.
Checklist: which seat
- You enjoy deciding for many teams: architect. You enjoy delivering for one customer: FDE.
- You prefer reviews and guidance: architect. You prefer owning the pager until handover: FDE.
- Your best artifact is a decision record: architect. Your best artifact is a readout with numbers: FDE.
Related reading
Straight answers
Frequently asked questions
Do solutions architects write code?
Some do, but the role centers on designs, reviews and guidance across teams. FDE work centers on a running system the customer operates.
Which role owns production?
The FDE stays through ship, operate and handover with metrics. Architects often advise many teams and move on before the 3am pages.
Can an architect become an FDE?
Yes, by shipping slices end to end again: discovery notes, code, deployment, runbook. The handover test in the related post is the bar.