I make enterprise software actually land — and I write down how, because when I started doing this work there was nothing to read.
How you run discovery when the stakeholder is hostile. How you scope something you have never seen before. When to build the throwaway version, and when to delete it. That craft gets passed around verbally between people who have done it, and almost never written down.
So I wrote it down: what the role actually is, how it differs from solutions engineering and consulting, what it pays, and how to get in.
Read: what a forward deployed engineer actually isThe book. The deployment playbook, the discovery process, the failure modes, and the organisational politics nobody writes down.
Working FDEs and the people trying to become them. Live breakdowns of real deployments, role referrals, and interview prep from people who ran the loop last month. Average placement is $260K+.
Talks on forward deployed engineering, applied AI in the enterprise, and what a deployment really costs before anyone writes a line of code.
I deploy Notion inside enterprises. That means I spend my time in other companies’ systems — their nine competing sources of truth, their undocumented exceptions, the deadline someone set before anyone checked whether it was possible — and build whatever makes the software actually work there.
Before Notion, Google and Bloomberg. The through-line has always been the same: sitting close enough to the people using the thing to find out quickly whether it survived contact with them.
The writing and the community came out of that. The same questions kept arriving in my inbox, and answering them once in public beats answering them fifty times in private.
Speaking enquiries, deployment questions, or a note about the book — all welcome.