FDE vs software engineer: which one fits you?
Updated
Same craft, different seat: product-team depth versus customer-site delivery, and the honest signals for which one fits you.
The two roles share the engineering craft and split on where the work happens and who defines done.
The short answer
Pick software engineering if you want depth in one system with a stable team. Pick FDE work if you want breadth across customer problems with discovery, delivery and handover in the same week.
The decision table
| Axis | Software engineer | Forward deployed engineer |
|---|---|---|
| Defines done | Product manager, roadmap | Customer owner, signed brief |
| Codebase | One product, long-lived | Many customer systems, short slices |
| Discovery | Mostly given | You run the interviews |
| Constraints | Your team's platform | Their security, windows, data rules |
| Handover | Team owns it | You package it for strangers |
| Travel | Rare | Common, sometimes weekly |
Worked example: the same person, two weeks
A fictional engineer (fictional) spends one week on product: a checkout latency fix with profiling, review and staged rollout. Next week on site: two discovery interviews, a lookup page on live labels, a readout with the lookup-time number. Both weeks are engineering. The first rewards depth, the second rewards judgment under constraints. The day-to-day post shows the FDE week in full; the career fit post helps you read your own signals.
Checklist: which fits
- You enjoy talking to users weekly: FDE signal. You prefer specs to arrive written: product signal.
- You like owning incidents end to end at someone else's site: FDE. You like owning one service for years: product.
- Travel energizes you: FDE. A stable desk rhythm matters more: product.
- You write docs strangers can run: both, but FDE tests it weekly.
Related reading
Straight answers
Frequently asked questions
What is the core difference?
A software engineer ships the product from inside the product team; an FDE ships a working outcome inside the customer organization, with discovery and handover attached.
Which one pays more?
Ranges overlap heavily. Travel, on-call at customer sites and breadth move FDE offers; scope ownership and system scale move product offers. Read any range against the actual job, not the title.
Can I switch between them?
Yes, both directions, and many do. Product engineers bring depth; FDEs bring customer judgment. The portfolio post shows how to evidence either move.