FDE vs Solutions Architect: Design vs Delivery
Updated · Tech checked
A solutions architect designs systems and hands specifications to builders; an FDE designs, builds, deploys, and operates the solution themselves. Architects produce blueprints; FDEs produce working systems.
The short answer
The solutions architect owns the design - diagrams, trade-off documents, integration patterns - and typically hands implementation to delivery teams. The FDE owns the outcome: they design, but also write the code, ship it, and keep it running. If the architect's artifact is a blueprint, the FDE's artifact is a running system plus a runbook.
Practical differences
| Aspect | Solutions architect | FDE |
|---|---|---|
| Coding | Occasional prototypes | Core of the job |
| Deliverable | Architecture docs, decision records | Working, observable, handed-over system |
| Customer contact | Design workshops | Weekly (often daily) operational contact |
| Accountability | Soundness of design | Production outcomes |
| Typical background | Senior eng, consulting | Senior eng with delivery bias |
Why companies blur them
Startups often hire one person to do both; enterprises separate them. When interviewing, ask what artifact your first 90 days must produce - that reveals which role the posting really is.
Continue: FDE vs software engineer · Hiring FDEs