FDE vs solutions architect
Same customer hallway, different job. Here’s the practical split if you’re choosing a title — or writing a job post.
Forward deployed engineer
An FDE is a product engineer who ships with the customer. You embed on-site or hybrid, own integrations, debug production, and feed what you learn back into the product. The bar is writing code and making the deployment stick — not only slides.
Common titles on this board: forward deployed engineer, deployment engineer, field engineer, forward deployed software engineer. See the FDE hub and deployment engineer filter.
Solutions architect
A solutions architect designs how the product fits the customer’s stack and process. More architecture reviews, RFPs, and technical win strategy; less day-to-day ownership of the running system than a classic FDE. Many SA roles are pre-sales or partner-facing; some are post-sale and look a lot like FDE under another name.
Browse solutions engineer listings when the title skews implementation-heavy.
Quick comparison
| FDE | Solutions architect | |
|---|---|---|
| Primary output | Working deployment + product feedback | Architecture, design, technical win |
| Where you sit | Often embedded with the customer | Customer-facing; may travel or remote |
| Code expectation | High — you ship and debug | Varies — often prototypes / reference code |
| Closest cousins | Deployment / field engineer | Solutions engineer, partner engineer |
Which should you apply to?
Want to stay close to the codebase and own outcomes in production? Start with FDE and deployment titles. Prefer systems design, stakeholder alignment, and technical sales motion? Solutions architect / solutions engineer fits better. Plenty of companies blur the labels — read the description for “on-site,” “embed,” and “write code,” not just the title.
For a live market snapshot, see the State of FDE Hiring report.