Forward Deployed Engineer roadmap
Engineering done inside someone else's organisation, on their data, against their constraints, next to the people whose problem it is. Half the job is code. The other half is figuring out what to build and getting an organisation to actually use it.
15 stages226 topics
Assumes you can already ship software. The sections marked as prerequisites are the technical floor; the distinctive skills of the role start at section 3, and roughly half of what follows is not code. That ratio is the role, not padding.
Engineering Floor
Speed of Delivery
Discovery and Problem Framing
Their Data
AI and LLM Application Work
Enterprise Integration
Security and Compliance
Domain Immersion
Communication
Stakeholders and Politics
Delivery Management
Commercial Awareness
Product Feedback Loop
Operating in the Field
Professional Practice
How to practise this without a customer
Most of this roadmap can't be learned from a course. Manufacture the conditions instead:
- Find a small business or nonprofit with a real manual process
- Spend a day watching them do it, taking notes
- Write the problem statement and get them to correct it
- Build something crude in a week
- Sit with them while they use it
- Watch where they work around it
- Rebuild, integrate with what they already run on
- Hand it over with documentation and no you
- Check in a month later on whether it's still used
- Write up what you got wrong at the start
That last check - still used a month later, without you - is the only success metric in this role that matters. Almost everything on this roadmap exists to move that number.
The hardest part is not the code. It is being the only technical person in a room of stakeholders who disagree with each other, hearing what the actual problem is underneath what they asked for, and being willing to say the thing they hired you to build is the wrong thing.