Learn how FDE, solutions engineer, solutions architect, sales engineer, and implementation roles differ in coding ownership, sales stage, quota, and outcomes.
By The Forward Deployed editorial teamReviewed
Role comparison
| Role | Typical stage | Production-code ownership | Primary measure |
|---|---|---|---|
| Forward Deployed Engineer | Mostly post-sale, sometimes late pre-sale | High | Customer outcome, adoption, uptime |
| Solutions Engineer / Sales Engineer | Pre-sale | Usually demos, proofs, and technical validation | Revenue support, win rate, quota influence |
| Solutions Architect | Pre- or post-sale design | Usually advisory or configuration-heavy | Architecture fit, successful implementation |
| Implementation Engineer | Post-sale | Varies; often integration and configuration | Time to launch, completion, stability |
| Consultant | Project-based | Varies by contract | Deliverables, utilization, client satisfaction |
Where the boundary blurs
Companies regularly reuse these titles for different jobs. The Pragmatic Engineer draws the most useful distinction: solutions architects are normally advisory, while FDEs are expected to write code directly on customer infrastructure and operate with more ambiguity. Some startups call a deeply technical pre-sales role FDE; some call a genuine deployment role solutions engineering. Read the responsibilities, compensation plan, and success metrics rather than the headline. Source.
Questions to ask before accepting the title
- What percentage of the week is hands-on coding, integration, customer meetings, and internal coordination?
- Who owns the code after launch, and does it enter the core product or remain customer-specific?
- Does the role carry quota, commission, utilization targets, on-call responsibility, or adoption targets?
- How many customers does one engineer support at once, and how much travel occurred in the last quarter?
- What did the last successful engagement change for the customer, and how was that measured?
The career implication
FDE experience compounds toward technical leadership, product, founding, applied AI, and customer-facing engineering when the role includes real ownership. Solutions roles compound toward go-to-market architecture, enterprise sales leadership, partnerships, and customer strategy. The best choice is the work you will actually perform, not the prestige attached to a title.