# Nasser Ghanemzadeh > Forward Deployed AI Engineer for founder-led B2B SaaS. Ships one narrow AI workflow into your product in 10 business days. Building Vectig in public with Claude Code. Former CEO/CPO at Nivo (acquired, 200K+ users). Nasser Ghanemzadeh has spent 17+ years building products and companies across AI, SaaS, and fintech. As CEO and later CPO at Nivo he built the product organization and shipped AI-powered applications that grew to 200K+ users and 450% revenue growth before the company was acquired. His current commercial focus is the AI Feature Sprint: a 10-business-day engagement for founder-led B2B SaaS teams of 5 to 50 that ships one narrow AI workflow into their product, with fixed scope, fixed price, and a Day-5 prototype guarantee. A focused 2-hour Discovery Day scoping session assesses whether an AI use case is useful, buildable, and worth a Sprint. His live R&D lab is Vectig, an AI-native cash flow forecasting product for pre-seed-to-Series-A founders, built solo with Claude Code, in public. Most workflow patterns he ships into a client codebase have already run in Vectig first. He is the author of three books: Daily Wisdom (366 one-page meditations on mental models, misjudgment, and money for founders, investors, and managers; Kindle pre-order, out October 6, 2026), Forward Deployed AI Engineering (a working guide to the Forward Deployed AI Engineer role: what it is, where it came from, how it is practiced, and how to do it well; 304 pages, first edition May 2026, Version 1.5 August 2026) and Founder Mode (how great founders stay close to product, people, judgment, and execution as companies scale). He writes a weekly newsletter, Nasser Ghanemzadeh’s Newsletter, which runs one real decision through one mental model for founders who invest and investors who build, and his work has been covered in Forbes, TechCrunch, Al Jazeera, and HuffPost. ## The books Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software, by Nasser Ghanemzadeh. Independently published. First edition May 2026; current version 1.5, August 2026. 304 pages, 5 parts, 20 chapters, plus a workbook and annotated references. ISBN 979-8199517683. - Paperback: $19.99 at https://www.amazon.com/Forward-Deployed-AI-Engineering-Software/dp/B0H3VKKG38/ - Kindle: $9.99 (also on Kindle Unlimited) at https://www.amazon.com/dp/B0H3KP9CVH/ Daily Wisdom for Founders, Investors, and Managers: 366 Meditations on Mental Models, Misjudgment, and Money, by Nasser Ghanemzadeh. Independently published. First edition; Kindle release October 6, 2026. 366 one-page meditations in twelve themed months: the latticework, the machinery of misjudgment, guarding the mind, the mathematics of wisdom, lessons from Darwin, systems and second-order effects, the psychology of money, the investor's temperament, the manager's craft, the founder's path, the not-to-do list, and the good life. Each day holds a quotation verified against a primary source, an essay of about 250 words, and one closing question or action. 399 pages in print, about 104,000 words. - Kindle: $11.99, pre-order at https://www.amazon.com/dp/B0HHNNFY6M/ (delivered October 6, 2026) - Paperback and hardcover: follow the Kindle release ## The service The AI Feature Sprint is a 10-business-day engagement that ships one narrow AI workflow into a founder-led B2B SaaS product. Fixed scope, fixed price: $5,000 at beta pricing, $7,500 to $10,000 standard. Working prototype by Day 5, guaranteed. A $500 Discovery Day scoping session assesses whether an AI use case is useful, buildable, and worth a Sprint, credited toward the Sprint if you continue within 14 days. --- # Nasser Ghanemzadeh: Forward Deployed AI Engineer and Author URL: https://ghanemzadeh.com/ Forward Deployed AI Engineer for founder-led B2B SaaS ## Nasser Ghanemzadeh I embed for 10 business days and ship the AI feature your roadmap keeps deferring. [Book a Sprint →](https://ghanemzadeh.com/ai-feature-sprint/) [Get the free chapters](https://ghanemzadeh.com/newsletter/) Built Nivo to 200K users and an acquisition as CEO and CPO. Covered in Forbes, TechCrunch, Al Jazeera, and HuffPost. 02 · Now ### What I'm doing now Everything I do feeds the same operation. Here it is, in priority order. - 01 **[The AI Feature Sprint.](https://ghanemzadeh.com/ai-feature-sprint/)** Ten business days embedded with a founder-led B2B SaaS team, shipping one narrow AI workflow into the product. Fixed scope, fixed price, a working prototype by Day 5. - 02 **[Vectig.](https://vectig.com)** AI-native cash flow forecasting for early-stage founders, built solo with Claude Code, in public. It's also my test bench: most Sprint patterns run here before a client sees them. - 03 **The books.** [Daily Wisdom](https://ghanemzadeh.com/books/daily-wisdom/) is a year of one-page meditations on judgment and money, on Kindle pre-order now. [Forward Deployed AI Engineering](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) explains the role. [Founder Mode](https://ghanemzadeh.com/book/) explains the operating practice underneath it. For the quick version of the FDE book, read [what a Forward Deployed AI Engineer is](https://ghanemzadeh.com/forward-deployed-ai-engineer/), or browse [the best FDE books](https://ghanemzadeh.com/best-forward-deployed-engineer-books/). - 04 **[The newsletter.](https://ghanemzadeh.com/newsletter/)** One letter a week that runs one real decision through one mental model. Better judgment for founders who invest and investors who build. - 05 **Earlier projects.** [Sengi](https://sengi.co), a financial OS for freelancers, built solo as a learning vehicle for AI-native financial tooling. Paused to focus on Vectig and the Sprint. 03 · The books ### Three books from the same desk. One is about judgment, one about the role, one about the operating practice underneath it. The first two chapters of Founder Mode and Forward Deployed AI Engineering are free, and so is a month of Daily Wisdom. [366 meditations · Pre-order #### Daily Wisdom One page a day on mental models, misjudgment, and money, for founders, investors, and managers.](https://ghanemzadeh.com/books/daily-wisdom/) [304 pages · Version 1.5 #### Forward Deployed AI Engineering The working guide to the FDE role: what the job is, how the work is done, how to break in.](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) [From HP to NVIDIA #### Founder Mode The history of calibrated founder involvement, and what the great companies paid for it.](https://ghanemzadeh.com/book/) 04 · Selected work ### Before all this - 01 **Nivo.** CEO, then CPO. Built the product organization and shipped AI-powered applications that grew to 200K+ users and 450% revenue growth before the acquisition. - 02 **Pangouan.** Founding Head of Product until 2026. Joined before there was a product, a team, or a user, and built all three. - 03 **Finnova.** Co-founder. A coworking space and accelerator backing early-stage startups. Seeing the ecosystem from the investor side changes how you think about everything. - 04 **Iran Startups.** Co-founder of a founder community. Earlier, ran [Techly](https://techly.me/), an English-language publication covering the Iranian startup ecosystem from 2014 to 2016, and wrote about The Lean Startup in Persian on the [Business of Software](https://businessofsoftware.ir/) blog when almost no one in Iran was talking about it. 05 · Speaking & media ### Coverage and the podcast Featured in [Forbes](https://www.forbes.com/sites/elizabethmacbride/2016/04/30/seven-reasons-iran-is-likely-to-be-an-entrepreneurial-powerhouse/), [TechCrunch](https://techcrunch.com/2014/09/02/the-next-tech-startup-ecosystem-to-emerge-iran/), [HuffPost](https://www.huffpost.com/entry/ibridges-the-iranian-runa_b_7627470), and [Al Jazeera](https://www.aljazeera.com/gallery/2016/12/1/inside-irans-silicon-valley). Host of [The Great CEO Podcast](https://www.youtube.com/@ghanemzadeh). 06 · FAQ ### Quick answers #### What is Nasser Ghanemzadeh working on? The AI Feature Sprint takes most of my week: a 10-business-day engagement that ships one narrow AI workflow into a founder-led B2B SaaS product. The rest goes to [Vectig](https://vectig.com), an AI-native cash flow forecasting tool I build solo with Claude Code, and to the books and the newsletter. Before this I was CEO and then CPO at Nivo, which grew to 200K+ users and was acquired. #### How do I work with you? Through the [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/) if you have a workflow in mind, through the [newsletter](https://ghanemzadeh.com/newsletter/) if you want to follow the work, or by [email](mailto:ghanemzadeh@gmail.com). 07 · Get in touch ### Email works best. [ghanemzadeh@gmail.com](mailto:ghanemzadeh@gmail.com). For a Sprint, start with the application form on [the AI Feature Sprint page](https://ghanemzadeh.com/ai-feature-sprint/). I'm also on [GitHub](https://github.com/ghanemzadeh), [LinkedIn](https://www.linkedin.com/in/ghanemzadeh/), [Goodreads](https://www.goodreads.com/ghanemzadeh), [AngelList](https://wellfound.com/u/ghanemzadeh), [Crunchbase](https://www.crunchbase.com/person/nasser-ghanemzadeh), [SlideShare](https://www.slideshare.net/Ghanemzadeh/presentations), and [F6S](https://www.f6s.com/member/ghanemzadeh). 08 · The newsletter ### Better judgment for founders who invest and investors who build. One real decision through one mental model, every week. Subscribe and the first two chapters of both books land in your first email. Free. Unsubscribe in one click. --- # Hire a Forward Deployed AI Engineer: 10-Day AI Feature Sprint URL: https://ghanemzadeh.com/ai-feature-sprint/ The AI Feature Sprint ## Forward Deployed AI engineering for founder-led B2B SaaS. OpenAI and Anthropic each launched deployment subsidiaries in May 2026 to embed engineers inside Fortune 500 companies. The AI Feature Sprint is how you hire a Forward Deployed AI Engineer without a $250K procurement process: fixed-price AI development, sized for founder-led SaaS teams. I scope, build, and ship an AI feature, one narrow workflow, into staging, production, or a production-ready pull request in 10 business days. Built by **Nasser Ghanemzadeh**, ex-CEO/CPO of Nivo (acquired, 200K+ users) · building Vectig in public · featured in Forbes, TechCrunch, Al Jazeera Now booking the next Sprint slot · beta capped at 3 teams [Book a $500 Discovery Day](https://ghanemzadeh.com/discovery-day/) [Apply for the $5,000 Sprint](https://tally.so/r/ja5pD6) Beta pricing: $5,000, capped at 3 teams. After beta: $7,500–$10,000. By [Nasser Ghanemzadeh](https://ghanemzadeh.com/). Last updated September 2026. As covered in Forbes · TechCrunch · Al Jazeera · HuffPost 02 · The problem ### Your team knows AI matters. The hard part is shipping the right thing. Most SaaS teams are already experimenting: someone has tried Claude Code, built a prototype, or floated a chatbot. The experiments stall because a useful AI feature needs more than a demo. It needs a clear workflow, the right data, a narrow scope, and an implementation path the team can actually ship. That's what the Sprint produces: one managed AI workflow with a clear use case, a review process, and a handoff your team can run with. 03 · The model ### What is Forward Deployed AI Engineering? Forward Deployed AI Engineering is a delivery model where an engineer embeds inside a customer's team and ships AI capabilities directly into the customer's product and codebase. The deliverable is working code in the customer's repo, not a deck about it. The term comes from Palantir, where it has been the dominant model for two decades. In May 2026, OpenAI launched a $10 billion deployment subsidiary using exactly this title, and Anthropic launched a $1.5 billion deployment subsidiary the same day. Both are aimed at the Fortune 500. The **AI Feature Sprint is the same playbook, sized for founder-led B2B SaaS teams of 5 to 50 people** who can't run a quarter-million-dollar procurement process. More on the role: [what a Forward Deployed AI Engineer is](https://ghanemzadeh.com/forward-deployed-ai-engineer/), and the full guide in the book, [Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/). 04 · Example workflows ### Examples of narrow AI workflows - **Investor update assistant.** Turn monthly metrics, asks, risks, and progress into a clear investor update draft. - **Finance/runway scenario explainer.** Help founders understand how burn, hiring, churn, or revenue changes affect runway. - **Customer summary generator.** Turn scattered account notes, usage data, and history into a concise customer summary. - **Support ticket summarizer.** Summarize long support threads and surface the issue, urgency, and suggested next step. - **Report generator.** Turn structured data or notes into a useful weekly, customer, or internal report. - **Onboarding assistant.** Guide new users or customers through the first important workflow in your product. 05 · Proof ### A concrete example: Investor Update Assistant Here's a workflow I've built into Vectig, the AI-native startup finance product I'm developing in parallel. The Investor Update Assistant pulls structured monthly metrics (MRR, burn, runway, hires, churn, key wins), takes 3–5 sentences of founder-written context, and generates a clean investor update draft. The founder edits, approves, and sends. Average time from open to send: 8 minutes vs. the typical 90+ minutes of blank-page writing. What you'd get in a Sprint: the workflow scoped to your data sources (Stripe, your spreadsheet, your CRM, whatever you use), a working prompt with output quality rubric, integration into your existing product or admin tool, and the handoff document so your team can maintain and iterate. Two weeks. Live by Day 10. ### The numbers I can show you today Every Sprint workflow ships with an output quality rubric, so each engagement produces its own before-and-after numbers. No Sprint has closed yet, so the two rows below come from the one live implementation that exists: the Investor Update Assistant running in Vectig, my own product. | Metric | Before | After | Sample | | --- | --- | --- | --- | | Investor update draft time, open to send | 90+ minutes of blank-page writing | 8 minutes | Live Vectig implementation | | Output quality rubric score | Not measured | 4-of-5 average across accuracy, clarity, honesty, and ask-coverage | First 30 sample runs | The draft-time number measures the founder's full loop: open the workflow, review the generated draft, edit, and send. The rubric score is the average across the four dimensions the workflow is graded on, scored run by run. As Sprints complete, their numbers land here. ### This is not an AI science project. This is not: - A generic AI strategy workshop - A chatbot brainstorm - A 40-page roadmap - An attempt to make your whole product "AI-native" in two weeks - A replacement for your engineering team - A vague exploration of agents, copilots, and buzzwords - A compliance-heavy enterprise AI transformation The sprint is intentionally narrow: one workflow, one clear user problem, one useful shipped outcome. 06 · Day 0 ### Day 0: The readiness check Before we scope a Sprint, we run a 2-hour readiness check on your use case, data, codebase, and team. Below is what a typical founder-led SaaS team looks like at the start. The Sprint begins on Day 1 with these gaps already mapped. ~/sprint-readiness/check.md $ run readiness_check --target founder-saas **use case** vague **data sources** scattered **codebase access** ready **AI provider setup** configured **team availability** partial **success criteria** undefined → recommended path: 2-hour Discovery Day to scope use case and define success criteria. Output simulated. Real diagnostics are generated live during your Discovery Day. 07 · The offers ### Two ways to start Discovery Day is Day 0, and it is optional. If the readiness check above looks like your team, start with the entry offer: it scopes the workflow and tells you whether a Sprint is the right next step. If the workflow is already scoped and the data is in place, start the main offer on Day 1. Day 0 #### Discovery Day Start here if you need help choosing the workflow. $500 for 2 hours ##### What happens - Use-case clarification - Data and API readiness check - Workflow selection - Risk assessment ##### You leave with - Recommended feature scope - Go / no-go memo - Sprint recommendation if there is a strong fit [Book a Discovery Day](https://ghanemzadeh.com/discovery-day/) Continue within 14 days and the **$500 is credited** toward the Sprint. Days 1 to 10 #### AI Feature Sprint Start here if you already know what to build. No Discovery Day required. $5,000 for the first 3 teams, then $7,500 to $10,000 10 business days. One narrow AI workflow shipped into staging, production, or a production-ready pull request. Working prototype by Day 5, or 50% back. **Scope and design** AI use-case selection, feature scope, UX flow, product and technical architecture, prompt and data design. **Build** Claude Code workflow, hands-on implementation of the selected workflow, working prototype by Day 5, staging deployment, production-ready PR, or handoff by Day 10. **Handoff** Team handoff and enablement session, Loom walkthrough, handoff notes, 30-day roadmap, output quality rubric, reusable workflow playbook. [Apply for the $5,000 Sprint](https://tally.so/r/ja5pD6) 08 · How it works ### How the 10-business-day sprint works **Day 1: Scope** Define the workflow, user problem, available data, constraints, and success criteria. **Days 2 to 3: Design** Map the UX flow, architecture, prompt and data structure, and implementation plan. **Days 4 to 5: Prototype** Build the first working version and validate the direction. **Days 6 to 9: Implementation** Refine the workflow, handle edge cases, add error states, improve prompts, prepare for handoff or deployment. **Day 10: Handoff** Staging deployment, production-ready pull request, or implementation handoff, depending on your infrastructure and access. ### How a Sprint gets scoped on Day 1 Every Sprint Brief is written around a single sentence: > *For [user], when [trigger or input] happens, the workflow will [process or action] and produce [output], so that [business value].* **Worked example.** "For the founder, when monthly metrics and 3 to 5 sentences of context are added, the workflow will draft a clean investor update covering metrics, risks, and asks, so that the founder can send consistent updates in 8 minutes instead of 90." If we can't agree on the words that fill those five brackets on Day 1, the Sprint isn't ready to start. ### The output quality rubric Every Sprint ships with a 1 to 5 rubric tuned to its specific dimensions. The scale is fixed; the dimensions change per workflow. | Score | Meaning | | --- | --- | | 1 | Unusable. Output is wrong, incoherent, or unsafe. | | 2 | Needs major rewrite. Shape is right; substance requires substantial editing. | | 3 | Usable with significant edits. Team starts from this draft but invests real time refining. | | 4 | Good with minor edits. Small adjustments only. Usable in roughly the time it takes to read. | | 5 | Ready to use. No edits needed. Ships as-is. | Each workflow's rubric specifies its own dimensions: accuracy, clarity, tone, format, completeness. Each comes with worked examples at every score level. ### What we'll take on as a first Sprint - Low risk Internal-only workflows. Drafts and summaries reviewed by a human before anything leaves the company. Most first Sprints sit here, and they should. - Medium risk Workflows touching customer-facing data (support tickets, CRM notes, sales transcripts, internal financial data) with explicit human review. - High risk Legal, medical, compliance, payments, or anything that takes customer-facing actions autonomously. Declined as a first Sprint. We'll help redefine to a lower-risk scope, or wait until trust and tooling are mature. ### Clear scope. Clear expectations. The sprint timeline begins on the agreed kickoff date, scheduled after contract signing and upfront payment. I take one active sprint at a time. Kickoff dates are scheduled on a first-available basis. Client access, decision-maker availability, and timely feedback are required for the 10-business-day timeline. ### This is for you if… - You run or lead product at a B2B SaaS company - You know AI should be part of your product but do not want vague experimentation - You want one useful AI workflow, not a giant AI transformation - Your team can provide access to relevant product, data, or codebase context - You can make decisions quickly during the sprint - You want product judgment and execution, not just code ### This is not for you if… - You want to "add AI" without a real user workflow - You need a full enterprise AI transformation - Your data is inaccessible or not ready - Your team cannot provide access or feedback during the sprint - You want a general chatbot without a clear product use case - You need guaranteed production deployment regardless of infrastructure constraints 09 · Who's behind it ### Why work with me I'm Nasser Ghanemzadeh, a former CEO/CPO and product leader with 17+ years building and scaling technology products. - Exited Nivo (200K+ users, 450% revenue growth, acquired). Press coverage in Forbes, TechCrunch, Al Jazeera, HuffPost. - Founding Head of Product at Pangouan. Co-founder of Iran Startups. Former accelerator lead at Finnova. - Currently building Vectig (AI-native startup finance), shipped daily with Claude Code and MCP. The Sprint method comes out of shipping these workflows in my own products first. Based in Turkey, available across European, Middle Eastern, and North American business hours. [LinkedIn](https://www.linkedin.com/in/ghanemzadeh/) · [Email](mailto:ghanemzadeh@gmail.com) · [Vectig](https://vectig.com) ### FAQ #### What is a 10-day AI Feature Sprint? A 10-business-day engagement to ship one narrow AI workflow into a B2B SaaS product. Scoping on Day 1, design on Days 2 to 3, prototype by Day 5, implementation on Days 6 to 9, handoff on Day 10. Fixed scope, fixed price. Deliverables include the workflow code committed to your repo, an output quality rubric, a workflow playbook, a Loom walkthrough, and a 30-day post-Sprint roadmap. #### Who is this for? Founder-led B2B SaaS companies with 5 to 50 employees, post-product-market-fit, with paying customers, real data inside their product, and pressure to ship AI features. Not for indie hackers, solopreneurs, or enterprises with formal procurement. #### What does it cost? $500 for a Discovery Day (credited toward the Sprint if you continue within 14 days). $5,000 for the Sprint at beta pricing (first 3 customers). $7,500 to $10,000 after beta. #### What happens if you can't deliver? If by Day 5 there's no working prototype demonstrating the core workflow, you can stop the Sprint and receive 50% back. No subjective judgment, no fine print. Either the prototype runs or it doesn't. #### Why pay you instead of using your own engineers? Speed, mostly: 10 days instead of six weeks of internal roadmap displacement, when pulling two engineers off the roadmap costs roughly $30K in salary before the opportunity cost. The rest is judgment. Knowing which workflow to ship first is harder than building it, and a fixed price on a fixed timeline keeps the scope honest. #### How is this different from an AI consulting firm? AI consulting firms deliver decks and roadmaps. This Sprint delivers a working AI workflow in your codebase by Day 10. The category is "Forward Deployed AI Engineering". The same shape of work OpenAI's Deployment Company and Anthropic's deployment arm sell to Fortune 500 customers, at a different price point. #### What kinds of AI workflows do you build? Investor update assistants. Runway scenario explainers. Customer summary generators. Support ticket summarizers. Report generators. Onboarding assistants. The common shape: narrow input, narrow output, single user, measurable improvement, human-in-the-loop review. #### What if our data isn't ready? Then a Sprint isn't the right starting point. The Discovery Day will say so explicitly and recommend what to do first. About half of Discovery Days end with "this isn't a Sprint yet, here's what to do instead." #### Do you handle compliance, security, GDPR, SOC 2? No. Those are explicitly out of scope. The Sprint can produce a workflow that's ready to deploy through your existing compliance posture, but the compliance review itself is your team's work. #### What stack do you work in? Whatever you already use. The Sprint integrates with your existing product, your existing data sources (Stripe, HubSpot, Linear, Slack, Notion, Intercom, Zendesk, your CRM, your admin), and your existing AI provider (Anthropic, OpenAI, AWS Bedrock, Google Vertex AI). The Sprint is too short to introduce new infrastructure. #### Can you guarantee production deployment? No. Production deployment depends on access, infrastructure, and third-party dependencies that aren't fully under our control. If production release is blocked, the deliverable is a staging deployment or a production-ready pull request your team can merge. #### What happens after Day 10? Three paths. Most teams take the workflow and run with it. The rubric and playbook are designed for self-service maintenance. Some come back for a second Sprint with a different workflow. Some sign an ongoing engagement for governance and iteration. All three are explicit options at handoff. ### Terms used on this page **Forward Deployed Engineer** An engineer who embeds inside a customer's team and ships inside their codebase, rather than delivering an external dashboard or report. Originally Palantir's model; adopted by OpenAI and Anthropic in May 2026. **AI Feature Sprint** This offer. 10 business days, one narrow AI workflow, fixed scope, fixed price. **Workflow** A specific process a user runs with clear inputs and outputs, producing a measurable improvement. The unit of work shipped in a Sprint. Not a "feature." **Sprint Brief** The one-to-two-page document written on Day 1 of a Sprint that defines scope, success criteria, deliverables, and explicit out-of-scope items. Part of the contract. **Output Quality Rubric** A 1 to 5 scoring checklist tuned to a specific workflow, used to evaluate generated outputs consistently after handoff. **MCP** Model Context Protocol, the standard for letting AI models talk to external systems. Many Sprint workflows integrate with customer systems via MCP servers. Full definitions for these and more terms are in the [Forward Deployed AI Engineering glossary](https://ghanemzadeh.com/glossary/). 10 · Get started ### Want to ship one useful AI feature? Start with a Discovery Day if you need help choosing the use case. Apply for the Sprint if you already know what to build and need it shipped. [Book a $500 Discovery Day](https://ghanemzadeh.com/discovery-day/) [Apply for the $5,000 Sprint](https://tally.so/r/ja5pD6) --- # The Best Forward Deployed Engineer Books & Resources (2026) URL: https://ghanemzadeh.com/best-forward-deployed-engineer-books/ [Forward Deployed Engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer/) ## The best Forward Deployed Engineer books & resources (2026) There is exactly one book written specifically about the Forward Deployed Engineer role, so a useful FDE reading list pairs it with the best books on the skills the role is made of: AI engineering, data systems, product discovery, and the customer room. These five books, plus five free essays and talks, cover the territory. By [Nasser Ghanemzadeh](https://ghanemzadeh.com/). Last updated August 2026. ### The five books #### 1. Forward Deployed AI Engineering, by Nasser Ghanemzadeh The working guide to the role itself: what an FDE is, where the model came from, how the work is practiced phase by phase, and how to break in. 304 pages across five parts and 20 chapters, with a workbook and annotated references at the back. It is the only book on this list written specifically about the Forward Deployed Engineer job. Full disclosure: I wrote this one. [Read about the book](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/), including the full structure and sample chapters. #### 2. AI Engineering, by Chip Huyen The technical complement. Huyen covers building applications with foundation models: evaluation, prompt engineering, retrieval, finetuning decisions, and inference. If the FDE book is about the job, this is the deepest treatment of the engineering underneath it. For readers who want the model-layer fundamentals before their first engagement. #### 3. Designing Data-Intensive Applications, 2nd edition, by Martin Kleppmann and Chris Riccomini The systems substrate of enterprise integration work. Most FDE engagements are won or lost on data plumbing, and this is the standard text on the storage, replication, and pipeline machinery inside every enterprise stack you will integrate with. Read it slowly. It pays off for years. #### 4. Inspired, 2nd edition, by Marty Cagan The product-discovery half of the craft. An FDE decides what to build under pressure, in front of the customer, and Cagan's book is the standard text on discovering what is worth building before you build it. Written for product teams, but the discovery discipline maps directly onto scoping an engagement. #### 5. Impro, by Keith Johnstone The odd one out, deliberately. Johnstone's book on improvisational theatre appears on Palantir's FDE onboarding reading list because customer-room work is improvisation: status, listening, and responding honestly to what is actually happening. It teaches the temperament of the work rather than the technique. ### Essential essays and talks (free) - [How Palantir built the ultimate founder factory](https://www.lennysnewsletter.com/p/inside-palantir-nabeel-qureshi). Nabeel Qureshi with Lenny Rachitsky, Lenny's Newsletter, May 2025. Reflections on nearly eight years as a Palantir forward deployed engineer, and why the role keeps producing founders. - [The FDE Playbook for AI Startups](https://www.ycombinator.com/library/Mt-the-fde-playbook-for-ai-startups-with-bob-mcgrew). Bob McGrew on Y Combinator's Lightcone podcast, September 2025. The person who helped pioneer the model at Palantir, and later led research at OpenAI, explains why it is at the heart of the AI boom. - [The Sales Strategy Conquering the AI Market](https://tomtunguz.com/fde-cs/). Tomasz Tunguz, July 2025. The go-to-market economics of forward deployed engineering, from the investor side. - [Forward Deployed Engineering 101](https://www.youtube.com/watch?v=KwhgfwOSToQ). Kevin Bai at the AI Engineer World's Fair, June 2026. A 17-minute framework for when FDE is necessary and how to structure it, from someone who did the work at Palantir, Rippling, and Anthropic. - [Software Is Changing (Again)](https://www.ycombinator.com/library/MW-andrej-karpathy-software-is-changing-again). Andrej Karpathy at YC's AI Startup School, June 2025. The wider shift the FDE role sits inside: LLMs as a new kind of computer, programmed in English. ### Where to start If you are deciding whether the role is for you, start with the [explainer on what a Forward Deployed Engineer is](https://ghanemzadeh.com/forward-deployed-ai-engineer/), then the Qureshi and McGrew conversations. If you have decided and want the map, start with [the Forward Deployed Engineer book](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) and follow the path in [how to become an FDE](https://ghanemzadeh.com/how-to-become-a-forward-deployed-ai-engineer/). --- # The Founder Mode Book: From HP to NVIDIA | Nasser Ghanemzadeh URL: https://ghanemzadeh.com/book/ **Brian Chesky just reopened the AI Founder Mode conversation for the AI Era.** This book turns the idea into an operating lens. A practical book on how founders stay close to product, people, judgment, and execution as companies scale. ## Founder Mode *How the Great Companies Are Actually Built* In 2024, Paul Graham named "Founder Mode" after Brian Chesky's talk at a YC alumni dinner. The practice is older than the name. HP, Disney, Apple, Pixar, Amazon, NVIDIA, and Costco built their best work this way. This book traces how, and is honest about the costs. Sign up to be notified when the book ships. The first two chapters are yours to read now. You'll also get the newsletter. One email a week, easy unsubscribe. ### Why this book, now Founder Mode is back in the conversation because Brian Chesky is again explaining how great founders operate differently. But the idea is still easy to misunderstand. Founder Mode is not micromanagement. It is not founder ego. It is calibrated involvement: staying close to the decisions, standards, customers, products, and people that shape the company. 02 · What's inside ### Four parts **Foundations** lays out what Founder Mode actually is, separating the practice from the personality around it. **Practices** is the operating manual. The small group of trusted operators. The meetings the founder still runs personally. The decisions the founder still owns. The handoffs that have to happen anyway. **Anchors** is the case-study core. Eight companies, eight chapters, and the specific moves that made each one work. **Returns, Costs, Coda** is the part most books skip. Founder Mode works, and it costs the founder things. The book is honest about both. 03 · Anchor chapters ### Eight companies, eight chapters #### HP Bill and Dave still walking the lab decades after founding, and the practice that institutionalized it. #### Walt Disney The *Snow White* production and a $1.5M bet on feature animation when nobody believed it would work. #### PayPal The small group, the relentless iteration, and the alumni network it produced. #### Apple Jobs in the Newton era. The products that almost shipped, the ones that did, and what he refused to delegate. #### Pixar Ed Catmull's Brain Trust as a structured, durable form of involvement. #### Amazon Bezos's Day 1 doctrine and the six-page memos that enforced it. #### NVIDIA Jensen Huang at Denny's, then thirty years of the same direct-report meetings. #### Costco The buying-club discipline that survived Sinegal's retirement. 04 · About ### About the author I'm Nasser Ghanemzadeh. 17+ years building products and companies across AI, SaaS, and fintech. Previously CEO/CPO at Nivo (acquired). Currently building Vectig solo with Claude Code, and running a 10-business-day [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/) for B2B SaaS teams. Also by Nasser: [Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) and [Daily Wisdom](https://ghanemzadeh.com/books/daily-wisdom/). More on the [home page](https://ghanemzadeh.com/). 05 · Start reading ### Read the first two chapters Join the launch list and I'll send you the first two chapters now. You'll also be notified when the Kindle version ships. You'll also get the newsletter. One email a week, easy unsubscribe. This book is independent and is not affiliated with Airbnb, Brian Chesky, Paul Graham, Y Combinator, or Invest Like the Best. --- # Books | Nasser Ghanemzadeh URL: https://ghanemzadeh.com/books/ Books ## Three books, one author Different topics, same operating lens. Daily Wisdom is a year of one-page meditations on judgment, misjudgment, and money. Founder Mode is about how great companies are actually built. Forward Deployed AI Engineering is about the job that has become the default way to ship AI into the real world. [2026 · Pre-order ### Daily Wisdom 366 Meditations on Mental Models, Misjudgment, and Money 366 meditations. 399 pages in print. Kindle pre-order, out October 6, 2026. One bad hire costs a year. One bad acquisition costs a decade. One bad partner can cost you the company. A year-long course in not fooling yourself, for founders, investors, and managers: a verified quotation, a short essay, and one question for every day of the year. Read a month free →](https://ghanemzadeh.com/books/daily-wisdom/) [2026 ### Forward Deployed AI Engineering A Working Guide to the Hottest Job in Software 304 pages. First edition, May 2026. Version 1.5, August 2026. On May 4, 2026, OpenAI and Anthropic each launched deployment subsidiaries on the same day, both built around the title Forward Deployed Engineer. This book is for the person who wants to do that work. Five parts: the landscape, the mindset and the method, the craft, becoming an FDE, and the economy and future. Read the first chapters →](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) [2026 ### Founder Mode How the Great Companies Are Actually Built 254 pages. First edition. In 2024, Paul Graham named "Founder Mode" after Brian Chesky's talk at a YC alumni dinner. The practice is older than the name. HP, Disney, Apple, Pixar, Amazon, NVIDIA, and Costco built their best work this way. This book traces how, and is honest about the costs. Read the first two chapters →](https://ghanemzadeh.com/book/) 02 · Why three books ### Why three books The three books are about the same thing seen from different angles. Daily Wisdom is about judgment: the models, the misjudgments, and the money, one page a day. Founder Mode is about the people who choose to stay close to the work that matters as their companies scale. Forward Deployed AI Engineering is about the work itself, in a specific form, in a specific moment. Start with whichever is closer to the problem on your desk. 03 · About the author ### About the author I'm Nasser Ghanemzadeh, a [Forward Deployed AI Engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer/) for founder-led B2B SaaS. 17+ years building products and companies across AI, SaaS, and fintech. Former CEO and CPO at Nivo (acquired, 200K+ users, 450% revenue growth), Founding Head of Product at Pangouan, and co-founder of Finnova and the Iran Startups community. My work has been covered in Forbes, TechCrunch, Al Jazeera, and HuffPost. Today I run the [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/) and build [Vectig](https://vectig.com) in public with Claude Code. More on the [home page](https://ghanemzadeh.com/). --- # Daily Wisdom: 366 Meditations on Mental Models | Nasser Ghanemzadeh URL: https://ghanemzadeh.com/books/daily-wisdom/ **Kindle edition open for pre-order.** It lands on your Kindle on October 6, 2026. Paperback and hardcover follow. A year-long course in not fooling yourself: a verified quotation, a three-minute essay, and one question, for every day of the year. ## Daily Wisdom *for Founders, Investors, and Managers: 366 Meditations on Mental Models, Misjudgment, and Money* First edition · Kindle pre-order, out October 6, 2026 · 366 meditations · 399 pages in print One bad hire costs a year. One bad acquisition costs a decade. One bad partner can cost you the company. Avoided mistakes compound like invested money, and almost nobody studies avoidance. The standard stupidities never go out of style: people overpaid for glamour stocks in 1720, in 1999, and in 2021, and founders ran out of cash in every decade on record. The names change. The errors are reruns. This book studies the reruns, one page a day, until you recognize them from the opening scene. [Pre-order on Kindle](https://www.amazon.com/dp/B0HHNNFY6M/) Paperback and hardcover editions follow the Kindle release. Or read a whole month now: sign up and the October sample, 54 pages, lands in your inbox. You'll also get the newsletter. One email a week, easy unsubscribe. 02 · What it is ### One page a day Start on today's date, or on January 1, or anywhere. The year is a circle; you will pass every page eventually. Each page has three parts: a quotation, verified and attributed; a short essay; and a closing prompt, a question to sit with or a small action to take. The prompt is the point. Reading the page takes three minutes; the page only pays if the prompt survives into your day. The months are themed, and later pages assume earlier ones the way a course assumes its prerequisites. Cross-references like "February 14" point back to the day where an idea was built. Ignore them on a first pass; they are for the second. At the back, Sources by Day lists where every quotation comes from, and Further Reading lists the books behind each month, in the order I would hand them to a friend. Two habits multiply the book's value. Keep a notebook; many prompts ask you to write, and the writing is where the thinking happens. And reread. The same page reads differently in a bull market and a bear market, before a decision and after one. 03 · Who it's for ### Three readers The pages rotate among three readers, because the three jobs share one underlying craft: making decisions under uncertainty, with other people's trust at stake. Most days speak to all three. All days speak to the person underneath the job. - **The founder** watching runway. October is your month, but the base rates, the cash arithmetic, and the partner problems are spread across the year. - **The investor** watching yourself. Temperament, not IQ, is the scarce input, and the barriers were never intellectual. - **The manager** building a machine that runs without you. Design the incentives, deserve the trust, tell the truth fast, delegate to the edge, protect the standards. And anyone who suspects the expensive mistakes are more avoidable than the successes are copyable. 04 · The year ### Twelve months, one argument The content follows Peter Bevelin's map and the thinkers he drew on. The first half builds the frame and studies how the mind fails. The second half turns outward: money, investing, management, founding, and what all of it is for. #### January · The Latticework Knowledge only works when it hangs together. A fact you cannot connect is a fact you will forget. This month builds the frame the other eleven hang on. #### February · The Machinery of Misjudgment Your brain is legacy hardware. Bevelin, following Munger, cataloged twenty-eight psychological reasons we misjudge. One per day, with the leap day for what happens when several fire at once. #### March · Guarding the Mind February cataloged the bugs. March installs the patches: procedures, questions, and habits that catch the error before it ships. None of them are clever. All of them work because they don't depend on you being at your best. #### April · The Mathematics of Wisdom About ten ideas, held firmly: compounding, probability, expected value, regression, ruin. Most expensive errors are not calculation failures. They are failures to see that a calculation applies. #### May · Lessons from Darwin Markets are ecosystems with quarterly reporting. Variation and selection, niches and predators, signals and mimicry, extinction and adaptation. Where the analogy breaks, the book says so. #### June · Systems and Second-Order Effects A company is not a machine with levers. It is a system, and it answers every intervention with consequences you did not order. The fix is almost never "try harder." #### July · The Psychology of Money Money decisions are made in minds, by people with histories, fears, and neighbors. Morgan Housel's territory: why keeping wealth is a different skill from making it. Less math than April. More mirrors. #### August · The Investor's Temperament Everything you need to know about investing fits in a pamphlet, and the pamphlet has been public for ninety years. Almost nobody can follow it. The barriers are temperamental, not intellectual. #### September · The Manager's Craft Design the incentives, deserve the trust, tell the truth fast, delegate to the edge, protect the standards, build a machine that runs without you. None of it requires charisma. All of it requires spine. #### October · The Founder's Path Survival, focus, customers, cash, partners, pricing, and the long game, with the base rates in view and the romance left at the door. The failures cluster around a short list of preventable causes. This month is that list. #### November · The Not-To-Do List Munger's 1986 commencement trick: prescribe guaranteed misery and let the audience invert. The reliable roads to failure, then a week in Sherlock Holmes's company. Wisdom, this month insists, is mostly subtraction. #### December · The Good Life What is all this optimization for? The Stoics, whom Munger read and quoted; the virtues that outlast portfolios; the arithmetic of enough. Wisdom's last application is not a better decision. It is a life you would re-choose. 05 · Two pages from the book ### Two pages, unabridged Every page in the book looks like these two. The first opens the year. The second opens November. #### January 1 · Why Wisdom > *"When you have faults, do not fear to abandon them."* > CONFUCIUS, *Analects* (trans. James Legge) Start with uncomfortable arithmetic. One bad hire costs a year. One bad acquisition costs a decade. One bad partner can cost you the company. Avoided mistakes compound like invested money. Almost nobody studies avoidance. We study success stories instead. They flatter us. Failures instruct us, and we skip them. Wisdom, as this book uses the word, is not brilliance. It is a working knowledge of how things fail, held firmly enough that you fail less often than the people around you. That is a real competitive advantage, because the standard stupidities never go out of style. People overpaid for glamour stocks in 1720, in 1999, and in 2021. Founders ran out of cash in every decade on record. The names change. The errors are reruns. Confucius stated the entry fee twenty-five centuries ago. You will commit faults. The question is what happens next. Most people defend the fault, because admitting it stings. So they pay for the same lesson twice, then a third time, at rising prices. The second bill is rarely denominated in money alone. It comes in years, in partners, in the chance that does not come back. This year, one page a day, we study the reruns until you recognize them from the opening scene. **Ask yourself:** What mistake have I already paid for more than once? What would it take to actually abandon it? #### November 1 · Consistently Not Stupid > *"It is remarkable how much long-term advantage people like us have gotten by trying to be consistently not stupid, instead of trying to be very intelligent."* > CHARLIE MUNGER Munger is *not* claiming that brilliance is worthless, or that Berkshire won by accident. He is observing where the returns actually came from, and his answer is avoidance. Not the genius trades made, but the standard stupidities not committed: the leverage not taken, the manias not joined, the reputations not gambled. Buffett put it the same way in the 1989 letter, after twenty-five years of buying businesses. He and Munger had not learned to solve difficult business problems. They had learned to avoid them, by looking for one-foot hurdles to step over rather than seven-foot ones they might clear. The arithmetic runs through this book. Errors are asymmetric. Losses require outsized gains to repair (April 20), and some end the game entirely; no accumulated brilliance survives one act of terminal stupidity. Errors are also more *predictable* than successes. Nobody can list next decade's winning ideas, but February's twenty-eight failure modes have been constant for centuries. Avoiding the known and recurring beats predicting the unknown, on reliability alone. And the competition is thinner. The pursuit of brilliance is crowded with ambitious people bidding up the price of cleverness. The pursuit of non-stupidity is nearly deserted, because it is unglamorous, invisible when it works (January 29), and pays in disasters that never happened. Munger's folk saying completes the thought: it's the strong swimmers who drown. The confident, the brilliant, the credentialed swim out too far. **Ask yourself:** Will this year's results improve more from one brilliant addition, or from deleting my two most repeatable stupidities? Name the two. 06 · The quotations ### Checked, not copied Every epigraph in the book was checked against a primary source before inclusion: the original text, the original letter or speech, the shareholder letter on the company's own site, or a scholarly edition. Where a beloved quotation could not be verified, it was left out rather than hedged. Proverbs and sayings are labeled as what they are, the property of nobody in particular. Five famous lines you may expect to find are corrected instead of repeated. - The line about the survival of "the most adaptable to change," universally attributed to Darwin, appears nowhere in Darwin. It is a 1963 paraphrase by management professor Leon Megginson. - "It is not enough to be busy; so are the ants" is a misquotation. Thoreau's 1857 sentence to H. G. O. Blake reads "It is not enough to be industrious; so are the ants. What are you industrious about?" - "It is better to be vaguely right than exactly wrong" belongs to Carveth Read (1898), not Keynes. - "Price is what you pay; value is what you get" is credited to Ben Graham, because that is how Buffett presents it in his 2008 shareholder letter. - "Lies, damned lies, and statistics" is given as what it is: a line Mark Twain attributed to Disraeli, with no Disraeli source ever found. Charlie Munger is quoted twenty times and Warren Buffett fifteen, both at a deliberate cap. Benjamin Franklin, Charles Darwin, Francis Bacon, Seneca, Marcus Aurelius, and Aesop follow. Howard Marks, Ben Graham, and Morgan Housel appear a few times each. Almost everything else is public domain, quoted from public-domain translations, and Sources by Day at the back lists where all 366 come from. 07 · Where it came from ### A daily dose In 2003, a Swedish businessman named Peter Bevelin published a strange and wonderful book called *Seeking Wisdom: From Darwin to Munger*. He wrote it, he said, to learn: collecting in one place what Darwin, Munger, Buffett, and a hundred scientists and philosophers had figured out about why we misjudge, and how to do better. It became an underground classic among investors and founders, passed hand to hand like a map. I have read many books on this subject and will read more. This one was born when I asked myself whether there was a book that would provide a daily dose of wisdom, the way a supplement provides a daily dose of vitamins. I could not find one, and in February 2024 I started writing it. The daily format is old. Tolstoy spent his last years assembling *A Calendar of Wisdom*; a century later, Ryan Holiday's *The Daily Stoic* and Robert Greene's *The Daily Laws* proved the form still works. It works because wisdom is not a download. It is a practice, and practices run on repetition. You cannot read your way into better judgment in a weekend. You might, page by page, over a year, train your way into it. Three promises. Every quotation was verified against a primary source before it went in. The ideas are credited: where a framing belongs to Munger, Buffett, Housel, Bevelin, or anyone else, their name is on it, and the connective tissue and the mistakes are mine. And nothing here is theory I haven't needed. I have spent my working life building software and companies, and every page is something I learned the expensive way or watched someone else pay for. 08 · About the author ### About the author I'm Nasser Ghanemzadeh. 17+ years building products and companies across AI, SaaS, and fintech. Former CEO and CPO at Nivo (acquired, 200K+ users), Founding Head of Product at Pangouan, and co-founder of Finnova and the Iran Startups community. Currently building [Vectig](https://vectig.com) solo with Claude Code and running the [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/) for founder-led B2B SaaS teams. I have been the founder watching runway and the manager building the machine. Finnova, a coworking space and accelerator, showed me the ecosystem from the investor side. The three readers in this book are three jobs I have held or sat across the table from. More on the [home page](https://ghanemzadeh.com/). Also by Nasser: [Forward Deployed AI Engineering](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) and [Founder Mode](https://ghanemzadeh.com/book/). 09 · Read it ### Read October free Join the newsletter and the October sample lands in your inbox: the introduction, all thirty-one days of The Founder's Path, and the sources at the back. The Kindle edition is on pre-order and arrives October 6, 2026. You'll also get the newsletter. One email a week, easy unsubscribe. ### FAQ #### What is Daily Wisdom? A year-long course in not fooling yourself. 366 one-page meditations for founders, investors, and managers, in the mental-model tradition of Charlie Munger and Peter Bevelin. Each page holds a verified quotation, a short essay, and one question or action to carry into the day. #### Who is it for? Operators who decide for a living: founders watching runway, investors watching themselves, managers building machines that run without them. The three jobs share one craft, making decisions under uncertainty with other people's trust at stake, and the pages rotate among them. #### How is each day structured? Three parts on one page. A quotation, checked against its primary source. An essay of about 250 words. A closing prompt, either a question to sit with (Ask yourself) or a small action to take (Try this). Reading the page takes three minutes. #### What do the twelve months cover? January builds the latticework of mental models. February and March cover the psychology of misjudgment and its antidotes. April is the mathematics of wisdom. May reads business through Darwin. June is systems and second-order effects. July is the psychology of money, August the investor's temperament, September the manager's craft, October the founder's path. November is the not-to-do list. December asks what all of it is for. #### When is it out, and in what formats? The Kindle edition is on pre-order now and is delivered on October 6, 2026. Paperback and hardcover editions follow the Kindle release. A free sample, the whole month of October, goes to anyone who joins the newsletter. #### How long is it? 366 meditations, one per page, about 104,000 words. The print edition runs 399 pages at 6 by 9 inches. Read one page a day, or raid it before a decision. #### Are the quotations real? Yes. Every epigraph was checked against a primary source: the original text, letter, or speech, or the shareholder letter on the company's own site. Where a beloved quotation could not be verified, it was left out. Five famous misattributions are corrected in the book rather than repeated. #### Do I have to start on January 1? No. Start on today's date, or anywhere. The year is a circle and you will pass every page eventually. Cross-references point back to the day where an idea was built; ignore them on a first pass. #### Is this investment advice? No. The book is for general education. It is not investment, legal, tax, or medical advice, and no reader should act on it without consulting qualified professionals. ### Keep reading - [All three books](https://ghanemzadeh.com/books/). Daily Wisdom, Forward Deployed AI Engineering, and Founder Mode on one page. - [Forward Deployed AI Engineering](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/). The working guide to the FDE role. - [Founder Mode](https://ghanemzadeh.com/book/). How the great companies are actually built. - [The newsletter](https://ghanemzadeh.com/newsletter/). One email a week from the same desk. Independent publication. This book is for general education and entertainment. It is not investment, legal, tax, or medical advice, and no reader should act on its contents without consulting qualified professionals. It is inspired by, but not affiliated with or endorsed by, any of the authors discussed in it. Book titles and company names are the property of their respective owners. Views are the author's alone. --- # Forward Deployed AI Engineering: The FDE Book | Nasser Ghanemzadeh URL: https://ghanemzadeh.com/books/forward-deployed-ai-engineering/ **May 4, 2026: OpenAI and Anthropic each launched deployment subsidiaries on the same day, both using the title Forward Deployed Engineer.** This book is for the person who wants to do that work. The Forward Deployed Engineer book: a working guide to the role OpenAI and Anthropic just put on the map. ## Forward Deployed AI Engineering *A Working Guide to the Hottest Job in Software* First edition, May 2026 · Version 1.5, August 2026 · 304 pages · ISBN 979-8199517683 What's new in Version 1.5: coverage updated through August 2026, including the AWS $1 billion FDE program and Microsoft's $2.5 billion Frontier initiative. For eighteen months before May 4, 2026, the Forward Deployed Engineer was already the most-discussed engineering role in the industry. Then the two most valuable private AI companies announced, on the same day, that they were creating new entities to put their engineers inside their customers' offices and ship working AI systems. OpenAI capitalized its vehicle at $10 billion. Anthropic at $1.5 billion. Same title. Same playbook. This book is for the person who wants to do that work. [Order on Kindle](https://www.amazon.com/dp/B0H3KP9CVH/) [Order Paperback](https://www.amazon.com/Forward-Deployed-AI-Engineering-Software/dp/B0H3VKKG38/) Or read the sample chapters (PDF) now. Sign up and they land in your inbox. You'll also get the newsletter. One email a week, easy unsubscribe. 02 · Who this is for ### Three readers The book is written for three people specifically. The chapters are ordered for each of them in turn. - **The early-career engineer.** Three to five years into your career. You have read some of the job postings. You recognize something in the description that fits how you want to work. You want a map. - **The mid-career switcher.** Consultant, solutions architect, product manager, ex-founder. You suspect you already have most of the skills. You want to know what is missing. - **The founder or hiring manager.** Building an FDE function for the first time. Needs a primer before going to market. 03 · What you'll be able to do ### By the last chapter The book is the FDE playbook, engineered around four working outcomes. Finish it and a reader should be able to do all four. - Explain the role to a hiring manager in your own words, without using "forward deployed" as a magic incantation. - Describe an end-to-end FDE engagement, from the first customer conversation through the production deployment and the synthesis review that turns the engagement into product. - Execute the first week of a real engagement using the templates in the workbook at the back of the book. - Plan a credible path from your current role to a first offer, with a portfolio you can defend and an interview loop you can prepare for. 04 · Structure ### Five parts **Part I. The Landscape.** What the role is, where it came from, and why the AI moment has made it the default operating model of the industry. **Part II. The Mindset and the Method.** The four traits that distinguish people who succeed at this work. The Echo and Delta split that organizes the work into two halves of one craft. The three-phase engagement that gives the work its rhythm. The gravel-road-to-highway pattern that makes the work compound into product. **Part III. The Craft.** Discovery, evaluation, shipping the first slice, integrating with the enterprise stack, and closing the loop. **Part IV. Becoming an FDE.** The paths in. The portfolio. The interview loop. The first year on the inside. **Part V. Economy and Future.** Pricing, outcomes, contracts. Cargo cults and failure modes. The FDE diaspora the labs are producing whether they want to or not. A closing note for the buyer. 05 · Anchor chapters ### Selected chapters #### The Pilot-to-Production Gap Why 95% of enterprise AI pilots produce zero measurable return, and why the gap isn't closed by buying more tokens. #### A Brief History: From Palantir to the Frontier Labs Two decades of FDE practice at Palantir. How it escaped that niche and became the default model for OpenAI, Anthropic, and the labs that followed. #### Echo and Delta: Two Halves of One Craft Echo is the deployment that's working now. Delta is the change that makes the next one work better. Most engineers are good at one. FDEs do both. #### Scope, Validate, Deliver: The Three-Phase Engagement The rhythm every FDE engagement follows, and the specific moves at each phase that separate the engagements that ship from the ones that drift. #### Evals as Specification In FDE work the eval is the spec. How to write one that customers will sign, engineers can build against, and the model can be measured on. #### The FDE Interview Loop What the loop actually tests. The case study, the writing sample, the customer simulation. How to prepare for each, with worked examples. #### Pricing, Outcomes, and Contracts Day rates, project rates, outcome rates, and equity. When each works. The contractual language that protects both sides. #### Cargo Cults and Failure Modes The five ways FDE engagements fail. Each one is recoverable if you catch it by the second week. 06 · Why now ### A snapshot in motion Most of the canonical literature on the role was written between September 2025 and April 2026. Some of it was written while this book was being drafted. The Anthropic and Blackstone joint venture, the OpenAI Deployment Company, the Google Cloud hires, the Big Four repositionings were news, not history, when the manuscript was working through draft. The book is written to still be useful three years from now, but the snapshot dimension is real, and a reader picking it up in 2029 will need to interpret the contemporary references through whatever has happened by then. One principle is most likely to outlast the specific organizations and titles around it. **The artifact is the truth. The code shipping is the substance. The document is the imitation.** Everything else in the book is an unpacking of that. 07 · About the author ### About the author I'm Nasser Ghanemzadeh. 17+ years building products and companies across AI, SaaS, and fintech. Previously CEO/CPO at Nivo (acquired). Currently building Vectig solo with Claude Code. I'm not a Palantir alumnus. I did not invent the FDE motion and I make no claim to having shaped it. What I have done is seventeen years of customer-side software work with the particular intensity that comes from having most often been the one ultimately accountable for whether the software shipped, worked, and earned its keep. I also run a 10-business-day [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/) for founder-led B2B SaaS teams: ship one narrow AI workflow into their product. Same playbook, sized for teams that don't have a $250K procurement process. More on the [home page](https://ghanemzadeh.com/). Also by Nasser: [Founder Mode](https://ghanemzadeh.com/book/) and [Daily Wisdom](https://ghanemzadeh.com/books/daily-wisdom/). 08 · Read it ### Read the first chapters Join the launch list and the first chapters land in your inbox now. The full Kindle and paperback editions are available on Amazon today. You'll also get the newsletter. One email a week, easy unsubscribe. ### FAQ #### Who is this book for? Three readers in particular. Early-career engineers (3 to 5 years in) who recognize something in the FDE job description that fits how they want to work. Mid-career switchers (consultants, solutions architects, PMs, ex-founders) who suspect they already have most of the skills. Founders and hiring managers building an FDE function for the first time. If none of those descriptions fits you, the book has failed at scoping. #### How long is it and how is it organized? 304 pages, organized into five parts and 20 chapters: the landscape, the mindset and method, the craft, becoming an FDE, and the economy and future. Plus a workbook and annotated references at the back. #### Why this book instead of the other AI books? Most AI books are about the models. This one is about the practice of deploying them inside someone else's company, with all the customer-side friction that implies. It is also written from inside that work, not from the bench. #### When is it available? First edition, May 2026. The current version is 1.5, August 2026. The full Kindle and paperback editions are available now on Amazon, and you can subscribe to the launch list above to read the first chapters. #### What formats? Kindle and paperback are both available now on Amazon. You can also read the first chapters by subscribing to the launch list. #### Is this affiliated with Palantir, OpenAI, or Anthropic? No. Independent publication. The book discusses these organizations because they shape the role, but the author is not affiliated with any of them. Views are the author's alone. ### Keep exploring the role - [What is a Forward Deployed Engineer?](https://ghanemzadeh.com/forward-deployed-ai-engineer/) The definition, the salary data, and how the role works. - [How to become an FDE](https://ghanemzadeh.com/how-to-become-a-forward-deployed-ai-engineer/). The backgrounds that transfer and the step-by-step path in. - [FDE vs Solutions Engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer-vs-solutions-engineer/). The closest neighboring role, compared side by side. - [Hire a Forward Deployed AI Engineer](https://ghanemzadeh.com/ai-feature-sprint/). The 10-business-day AI Feature Sprint for founder-led B2B SaaS. - [The best Forward Deployed Engineer books and resources](https://ghanemzadeh.com/best-forward-deployed-engineer-books/). What to read around this book, including the free essays and talks. Independent publication. Not affiliated with Anthropic, OpenAI, Google, Palantir, Y Combinator, Andreessen Horowitz, or any other organization mentioned in this book. Product and company names are trademarks of their respective owners. Views are the author's alone. --- # AI Discovery Day: 2-Hour Use-Case Scoping Session ($500) URL: https://ghanemzadeh.com/discovery-day/ Discovery Day ## Before we scope a Sprint, we scope the problem. A 2-hour working session with Nasser Ghanemzadeh. We look at your use case, your data, your codebase, and your team. By the end you have either a clean Sprint Brief or an honest "this isn't a Sprint yet, here's what to do first" memo. $500. Credited toward your Sprint if you continue within 14 days. [Book a Discovery Day →](https://cal.com/ghanemzadeh/discovery) Next available slot: visible on the booking page. One Discovery Day per week max. As covered in Forbes · TechCrunch · Al Jazeera · HuffPost 02 · The document ### What you walk away with By the end of the 2 hours you have a working document with all of the following, written on the call and ready to forward to your team. - Use-case clarification, written in a single sentence using the Sprint Brief template. - Data and API readiness assessment for the candidate workflow. - Recommended workflow scope (or a recommended deferment, with reasoning). - A go / no-go memo on whether a Sprint is the right next step. - A Sprint Brief draft if there's a strong fit, including success criteria and out-of-scope items. - Honest answers about what fits in 10 business days and what doesn't. 03 · Fit ### Who this is for - B2B SaaS founders or product leaders considering shipping an AI feature. - Teams that have tried building AI features and gotten stuck somewhere between prototype and production. - Teams that know AI should be part of their product but want a second opinion before committing engineering time. - Teams comparing Sprint vendors and wanting to validate fit before signing. ### Who this is not for - Teams looking for a generic AI strategy consultation. - Solo indie hackers without a B2B SaaS product. - Enterprise teams with formal procurement or RFP processes. - Anyone looking for a free 30-minute consultation. This is a paid scoping session, not a sales call. 04 · The two hours ### How a Discovery Day works The 2 hours are structured but not rigid. Rough shape: **Minutes 0–30: Your context.** Current product, team, AI experiments to date, what's worked and what hasn't, what's pulling the AI conversation forward inside your company. **Minutes 30–75: The candidate workflow.** Inputs, outputs, users, data sources, current manual process, what good output looks like, who reviews it before it ships. **Minutes 75–105: Feasibility.** What fits in a 10-day Sprint and what doesn't. Risk classification (low / medium / high). Integration complexity. Where the Day-5 prototype likely lands. **Minutes 105–120: The memo.** Go / no-go recommendation, Sprint Brief draft (if applicable), scoping language, next-step recommendation. Shared as a Google Doc you keep. About half of Discovery Days end with a Sprint recommendation. The other half end with "here's what to do first, come back when X is in place." Both are valid outcomes. The point of a Discovery Day is to find out which one you are, not to convince you to buy a Sprint. 05 · The credit ### The credit toward Sprint If you continue to a full Sprint within 14 days of your Discovery Day, the $500 is credited against the Sprint price. So a Discovery Day → Sprint path costs $5,000 total at beta pricing, not $5,500. If we agree the Sprint isn't the right next step, the $500 covers the working document and the 2 hours. No upsell, no follow-up sequence, no retainer pitch. 06 · Before the call ### What I need from you before the call A short pre-call form, sent after booking. Three things: - **The workflow you're considering.** One paragraph is enough. Examples I've worked through with other founders: investor update assistant, runway scenario explainer, customer summary generator, support ticket triage, onboarding assistant. - **Your stack and data access.** What's your product built in, where does the relevant data live (Stripe, your DB, HubSpot, Linear, Notion, your CRM, your admin), and what AI provider you already use (Anthropic, OpenAI, Bedrock, Vertex) if any. - **The decision-maker question.** Who needs to approve a Sprint, and are they on the call. If they're not, a Discovery Day is fine, but the Sprint recommendation will be harder to act on. That's it. No data dumps, no NDAs to sign before the call. We sign a mutual NDA on the call itself if either side wants one. 07 · Who's behind it ### Why work with me I'm Nasser Ghanemzadeh. I've spent 17+ years on the customer side of software, as CEO, CPO, and product lead. I built and exited Nivo (200K+ users, 450% revenue growth, acquired), led product at Pangouan, co-founded Iran Startups, and ran the Finnova accelerator. These days I build Vectig, an AI-native startup finance product, shipped daily with Claude Code and MCP. **Speaking on AI-native product development:** OMR Festival, re:publica, GITEX EUROPE. A Discovery Day points that experience at your roadmap for two hours. Based in Turkey, available across European, Middle Eastern, and North American business hours. [LinkedIn](https://www.linkedin.com/in/ghanemzadeh/) · [Email](mailto:ghanemzadeh@gmail.com) · [Vectig](https://vectig.com) ### FAQ #### What if we decide not to do a Sprint after the Discovery Day? Then you walk away with the working document, the go / no-go memo, and 2 hours of focused outside-perspective on your AI roadmap. No follow-up sales sequence. You're free to take the memo to another vendor, to your internal team, or to nobody at all. #### Do you sign an NDA? If either side wants a mutual NDA, we sign one on the call itself before getting into specifics. I don't ask for NDAs to be signed before booking, and I don't expect you to. #### What if our data isn't ready? That's one of the most common Discovery Day outcomes: "the workflow makes sense, but the data foundation isn't there yet." The memo will say exactly what to do first, usually a 2 to 4 week data-readiness project that you can run internally, and we revisit Sprint readiness when it's done. #### How is this different from a free consultation call? A free call is sales discovery. This is a paid working session. The $500 buys two things: focused 2-hour attention with no agenda except your problem, and a written document you keep regardless of outcome. The economics force both sides to take it seriously. #### What if I'm not sure I want a Sprint yet? Then a Discovery Day is exactly the right starting point. About half of them end with a deferment recommendation. That's a feature, not a failure mode. #### Can a co-founder or technical lead join? Yes. Up to three people from your side on the call. Beyond three the conversation slows down. If you want broader team alignment, the right pattern is: founder + tech lead on the Discovery Day, then I record a Loom walkthrough of the memo for everyone else. #### What if our use case is in a high-risk category (legal, medical, compliance, payments)? The Discovery Day still works, but the Sprint recommendation will likely be "not yet" or "redefine scope to a lower-risk adjacent workflow." High-risk first Sprints don't make sense for teams new to AI deployment. The memo will explain what does. #### Do you work with companies outside B2B SaaS? Mostly no. The methodology, examples, and Sprint structure are built around founder-led B2B SaaS at 5 to 50 people, post-product-market-fit. If you're outside that, the Discovery Day may still be useful but the Sprint may not be the right vehicle. 08 · Book it ### Two hours, one document, a clear next step. Book a Discovery Day for a focused outside read on whether the AI feature you're considering is ready to ship in 10 business days. Or start with the full breakdown of the [10-day AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/). [Book a Discovery Day →](https://cal.com/ghanemzadeh/discovery) [Read the Sprint details](https://ghanemzadeh.com/ai-feature-sprint/) --- # Forward Deployed Engineer vs Solutions Engineer: Key Differences URL: https://ghanemzadeh.com/forward-deployed-ai-engineer-vs-solutions-engineer/ [Forward Deployed AI Engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer/) ## Forward Deployed AI Engineer vs solutions engineer A Forward Deployed AI Engineer and a solutions engineer share the same technical, customer-facing instinct, but they work for different sides and ship different things. The Forward Deployed AI Engineer builds an AI workflow into the customer's own product and owns the result. The solutions engineer sells, demos, and integrates a vendor's product on the vendor's behalf. By [Nasser Ghanemzadeh](https://ghanemzadeh.com/). Last updated August 2026. ### The short answer If the code you ship lives in the customer's repository and the win is the customer's outcome, that is forward deployed work. If the code you ship is a demo or integration that helps close and onboard a customer onto your employer's platform, that is solutions engineering. The two roles look similar from the outside because both put a technical person in front of a customer. The forward deployed engineer vs solutions engineer question comes down to whose product gets built and who you answer to. ### Side by side | Dimension | Forward Deployed AI Engineer | Solutions engineer | | --- | --- | --- | | Works for | The customer's outcome, via a deployment company or a direct engagement | The software vendor selling the product | | Primary deliverable | A production AI workflow in the customer's codebase | Demos, proofs of concept, and integrations | | Where the code lives | The customer's product and repository | The vendor's platform and demo environments | | Measured on | A shipped workflow the customer's team can run and maintain | Pipeline, deals closed, and successful onboarding | | AI focus | Prompt and context design, data integration, evaluation rubrics | Showing how the vendor's AI features fit the customer's stack | | Compensation | Median base $174,000; median package $238,000; senior frontier packages above $500,000 (public data, 2026) | Varies by vendor; typically base plus commission (OTE), tied to sales and onboarding outcomes. | ### Where they overlap Both roles need to read a customer's real environment quickly, translate a business problem into a technical plan, and stay credible in a room with engineers and executives at the same time. Both live with ambiguity and incomplete data. The instincts transfer cleanly, which is why solutions engineers are one of the most common backgrounds for people moving into forward deployed AI work. ### How to choose between them Choose by what you want to own. If you want to close deals and help many customers adopt one product, solutions engineering fits. If you want to build the actual feature and own whether it works in production, the Forward Deployed AI Engineer role fits. One more practical signal: seen as solutions engineer vs forward deployed engineer, the trade is breadth against depth. Solutions engineering rewards breadth across a pipeline; forward deployed work rewards depth on one customer at a time. Neither is more senior than the other. They optimize for different outcomes. ### Applied AI Engineer vs Solutions Engineer Applied AI Engineer is Anthropic's title for the FDE-shaped role, the same job this page describes under a different name. So the same contrast applies: the applied AI engineer builds a production AI workflow inside the customer's systems and is measured on whether it ships, while the solutions engineer sells and integrates the vendor's product and is measured on the deal. If a posting says Applied AI, read it as forward deployed. ### Related - [What is a Forward Deployed AI Engineer?](https://ghanemzadeh.com/forward-deployed-ai-engineer/) - [How to become a Forward Deployed AI Engineer](https://ghanemzadeh.com/how-to-become-a-forward-deployed-ai-engineer/) - [The book: Forward Deployed AI Engineering](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) ### Frequently asked questions #### Can a solutions engineer become a Forward Deployed AI Engineer? Often, yes. Solutions engineers already have the customer-facing instinct and the integration skills. The shift is from selling and configuring a vendor's product to building and owning a production AI workflow inside the customer's codebase, plus the evaluation discipline to prove it works. #### Who does each role work for? A solutions engineer almost always works for the software vendor and is measured on sales and onboarding. A Forward Deployed AI Engineer works on the customer's outcome, whether employed by a deployment company or engaged directly, and is measured on shipping a workflow the customer's team can run. #### Does a solutions engineer write production code? Sometimes, but usually demos, proofs of concept, and integrations rather than features that live permanently in the customer's product. A Forward Deployed AI Engineer's main deliverable is production code in the customer's repository, with edge cases, logging, and a handoff. --- # What Is a Forward Deployed Engineer (FDE)? Definition, Salary, Role URL: https://ghanemzadeh.com/forward-deployed-ai-engineer/ The role ## What Is a Forward Deployed Engineer? **A Forward Deployed Engineer (FDE) is a software engineer who sits at the customer's site and fills the gap between what the product does and what the customer needs, shipping working software, today usually an AI workflow, directly into the customer's systems.** That definition comes from Bob McGrew, who spent 11 years at Palantir, where the role was invented, and later led research at OpenAI. This page covers what the work looks like, what it pays, who hires for it under which titles, and how to get in. [Read the book →](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) [See it as a service](https://ghanemzadeh.com/ai-feature-sprint/) By [Nasser Ghanemzadeh](https://ghanemzadeh.com/). Last updated August 2026. ### What does a Forward Deployed Engineer do? An FDE takes one narrow use case from a vague idea to a working AI feature inside the customer's product, end to end, and owns every step in between. The deliverable is code in the customer's repository. A typical engagement runs through: - **Scoping.** Turn "we should add AI" into one workflow with a named user, a clear input, and a clear output. - **Architecture and UX.** Decide where the workflow lives in the product and how a person actually triggers and reviews it. - **Prompt and context design.** Build the model interaction, including the system prompt, the retrieved context, and the guardrails. - **Data integration.** Connect the workflow to the customer's real data and systems, often through the Model Context Protocol. - **Implementation.** Write production code in the customer's repository, with edge cases, fallbacks, error states, and logging. - **Evaluation.** Ship a written rubric that defines what good output looks like and how the team scores it over time. - **Handoff.** Hand the team code they can maintain, plus the rubric and a short playbook, so the workflow survives without the engineer. The output is code in the customer's repo. Not a dashboard. Not a report. Not a Loom. ### Why is it called "forward deployed"? The phrase is military language. Forward deployed units are stationed at the edge, close to the situation, with the autonomy to act without calling headquarters first. Applied to engineers, it means the same thing: you work inside the customer's organization, and you decide on the spot. Palantir made the term a job. It built its business on engineers who deploy into a customer's organization and deliver outcomes inside that customer's systems. The model spread because it solved a specific failure: software that works in a demo and dies in the customer's real environment. In May 2026 the term went mainstream. OpenAI and Anthropic each launched a deployment subsidiary within a day of each other, both using the title Forward Deployed Engineer, both aimed at getting frontier models into enterprise products rather than selling API access and hoping. The AI in some job titles marks the shift: the capability being deployed is no longer just software, it is an AI workflow. ### What does a Forward Deployed Engineer earn? The median FDE total package is $238,000, on a median base salary of $174,000, per public compensation data from 2026. Senior packages at the frontier labs go above $500,000. | Compensation measure | Figure (2026) | | --- | --- | | Median base salary | $174,000 | | Median total package | $238,000 | | Senior frontier-lab packages | Above $500,000 | Figures are from public compensation data collected in 2026. Individual offers vary with seniority, location, and equity. ### FDE titles by company Almost nobody posts this job under one name. The same customer-embedded, ship-into-production role is hired under different titles at different companies, so searching for one string misses most of the market. | Company | What they call the role | | --- | --- | | Palantir | Echo and Delta, the two halves of its forward deployed practice | | OpenAI | Forward Deployed Engineer | | Anthropic | Applied AI | | Sierra | Agent Engineer | | Harvey | Implementation Engineer | | Decagon | Agent builder / agent SWE | Echo and Delta are defined in the [glossary](https://ghanemzadeh.com/glossary/), and the split between them is a core chapter of [the book](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/). ### How is an FDE different from a solutions engineer? A solutions engineer works for the vendor and is measured on the sale; an FDE works on the customer's outcome and is measured on what ships. Both are technical and customer-facing, which is why the two roles are so often confused. | Role | What they ship | Where the work lives | Optimizes for | | --- | --- | --- | --- | | Forward Deployed AI Engineer | A working AI workflow built into the customer's product | The customer's codebase and product | A shipped outcome the customer's team can run and maintain | | Solutions engineer | Integrations, demos, and configuration of a vendor's product | The boundary between vendor and customer | Closing and onboarding the customer onto the vendor's platform | | ML engineer | Models, training pipelines, and inference infrastructure | The model and data platform | Model performance, scale, and reliability | | AI consultant | Strategy, roadmaps, and recommendations | Documents and meetings | Advice and direction, with execution left to others | For a side-by-side that goes deeper on the closest comparison, see [Forward Deployed AI Engineer vs solutions engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer-vs-solutions-engineer/). ### Why did the FDE role explode in 2026? Because enterprises learned that buying AI is not the same as deploying it. An MIT study cited in the book found that 95% of enterprise AI pilots produce no measurable return. The FDE is the industry's answer to that gap, and in 2026 the money followed. - **May 4, 2026.** OpenAI launched a $10 billion deployment subsidiary and Anthropic a $1.5 billion one, on the same day, both hiring under the title Forward Deployed Engineer. - **May 16, 2026.** Business Insider reported that Indeed postings for the role grew from 643 in April 2025 to 5,330 in April 2026, more than 700% in a year. The same month, the title returned 55,000+ LinkedIn results in the US and over 100 postings on the YC job board. - **June 30, 2026.** AWS announced a $1 billion FDE program. - **July 2, 2026.** Microsoft launched Frontier: $2.5 billion and 6,000 embedded experts. - **July 30, 2026.** [TechCrunch reported](https://techcrunch.com/2026/07/30/forward-deployed-engineers-are-the-ai-industrys-latest-talent-obsession/) a C&T study projecting demand for FDEs to surge 2,100% by the end of 2026, against an estimated 2,000 qualified FDEs in total. ### What skills does the role require? Less model research, more product engineering and judgment. The hard part is usually deciding what to build and proving it works, not calling the API. - **Product engineering.** Shipping real features into a real codebase, with the discipline that production demands. - **Prompt and context design.** Getting reliable output from frontier models, including retrieval and structured context. - **Data integration.** Connecting models to messy customer systems and APIs, often via [MCP](https://ghanemzadeh.com/glossary/#mcp). - **Evaluation.** Defining what good output is and scoring it, so quality is measured rather than asserted. - **Customer-facing judgment.** Scoping under pressure, saying no to the wrong workflow, and protecting a fixed timeline. ### How do you become a Forward Deployed Engineer? Most people who do this well arrive from product engineering, solutions or consulting, or a founder background, then prove they can ship one narrow AI workflow end to end. The fastest credible path is to build and ship a real workflow, write the evaluation rubric for it, and be able to walk someone through the code. For a step-by-step version, see [how to become a Forward Deployed AI Engineer](https://ghanemzadeh.com/how-to-become-a-forward-deployed-ai-engineer/). ### Forward Deployed AI Engineering for founder-led B2B SaaS The enterprise version of this role is built for Fortune 500 procurement. The same work, sized for a 5-to-50-person founder-led SaaS team, is the AI Feature Sprint: one narrow AI workflow shipped into the product in 10 business days, fixed scope and fixed price. That's the work I do. Most patterns I ship into a customer's codebase have already run in [Vectig](https://vectig.com), my own AI-native product and live R&D lab. If you want to see the engagement, start with the [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/) or a [Discovery Day](https://ghanemzadeh.com/discovery-day/). The book ### A working guide to the role [Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) is the long-form version of this page: what the role is, where it came from, how it is practiced, and how to do it well. Written from inside the work, in the months after OpenAI and Anthropic put the title on the map. For the wider reading list around the role, see [the best Forward Deployed Engineer books](https://ghanemzadeh.com/best-forward-deployed-engineer-books/). ### About the author I'm Nasser Ghanemzadeh, a Forward Deployed AI Engineer for founder-led B2B SaaS. 17+ years building products and companies across AI, SaaS, and fintech. Previously CEO/CPO at Nivo (acquired, 200K+ users, 450% revenue growth). Work covered in Forbes, TechCrunch, Al Jazeera, and HuffPost. I run the [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/), build [Vectig](https://vectig.com) in public with Claude Code, and wrote the book on this role. More on the [home page](https://ghanemzadeh.com/). ### Frequently asked questions #### Do Forward Deployed Engineers write production code? Yes. The defining deliverable is working code in the customer's repository, with edge cases, fallbacks, error states, logging, and a handoff the customer's team can maintain. Demos and decks are what the role exists to replace. #### Is Forward Deployed Engineer a good career in 2026? The demand data is unusually one-sided. Indeed postings grew more than 700% in a year per Business Insider, TechCrunch reports projected demand growth of 2,100% by the end of 2026 against an estimated 2,000 qualified FDEs, and the median package is $238,000. The constraint is proving you can do the work, not finding openings. #### Do you need a machine learning background to become an FDE? No. The role applies existing models rather than training them. The core skills are product engineering, prompt and context design, data integration, evaluation, and customer-facing judgment. A research or MLOps background helps in some engagements but is not the entry requirement. #### How much travel does the role involve? More than most software roles. Anthropic's listing puts travel at 25 percent. OpenAI expects its FDEs on customer sites a few days a week during an engagement. At Palantir, Nabeel Qureshi describes four to five days a week at the customer's office as the high end; two to three is more typical. #### Is a Forward Deployed Engineer the same as an applied AI engineer? Functionally, yes. Applied AI is Anthropic's title for the FDE-shaped role, the same way Sierra says Agent Engineer and Harvey says Implementation Engineer. The employer's label changes; the work of shipping AI into a customer's production systems does not. ### Sources - TechCrunch, "Forward deployed engineers are the AI industry's latest talent obsession," July 30, 2026. [techcrunch.com](https://techcrunch.com/2026/07/30/forward-deployed-engineers-are-the-ai-industrys-latest-talent-obsession/) - Business Insider, reporting on Indeed job-posting data for Forward Deployed Engineer roles, May 16, 2026. - Public compensation data for Forward Deployed Engineer roles, 2026. - MIT study on enterprise AI pilot outcomes, as cited in *Forward Deployed AI Engineering*. - Bob McGrew on the Forward Deployed Engineer role. McGrew spent 11 years at Palantir and later led research at OpenAI. - Anthropic and OpenAI job listings for the role (travel expectations). - Nabeel Qureshi on Palantir's forward deployed model, Lenny's Newsletter, May 2025. [lennysnewsletter.com](https://www.lennysnewsletter.com/p/inside-palantir-nabeel-qureshi) Newsletter ### Better judgment for founders who invest and investors who build. One letter a week that runs one real decision through one mental model. Subscribing also gets you the first two chapters of both my books. Free. Unsubscribe in one click. --- # Forward Deployed AI Engineering Glossary | Nasser Ghanemzadeh URL: https://ghanemzadeh.com/glossary/ [Forward Deployed AI Engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer/) ## Forward Deployed AI Engineering glossary The working vocabulary of Forward Deployed AI Engineering for founder-led B2B SaaS. Plain definitions of the role, the offer, the deliverables, and the tools, written the way they are actually used. By [Nasser Ghanemzadeh](https://ghanemzadeh.com/). Last updated August 2026. **Forward Deployed AI Engineer (FDE)** An engineer who embeds inside a customer's team and ships AI capabilities directly into the customer's product and codebase, rather than delivering a deck, a dashboard, or a demo. The delivery model comes from Palantir. OpenAI and Anthropic both launched deployment subsidiaries using it in May 2026. See the full explainer: [what is a Forward Deployed Engineer?](https://ghanemzadeh.com/forward-deployed-ai-engineer/) **Echo (Palantir)** At Palantir, the embedded analyst with deep domain expertise who owns the customer relationship, one half of its two-role FDE model. In [Forward Deployed AI Engineering](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/), Echo also names one half of the craft: the deployment that is working now. **Delta (Palantir)** At Palantir, the deployed engineer who ships code inside the customer's environment; the company describes the responsibilities as similar to a startup CTO's. In *Forward Deployed AI Engineering*, Delta also names the other half of the craft: the change that makes the next deployment work better. **AI Feature Sprint** A ten-business-day engagement that ships one narrow AI workflow into a customer's product. Fixed scope, fixed price, end-to-end delivery and handoff. See the [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/). **Discovery Day** A two-hour paid working session, priced at $500, to assess whether an AI use case is useful, buildable, and worth a Sprint. The output is a go/no-go memo written on the call, credited toward a Sprint if the customer continues. See [Discovery Day](https://ghanemzadeh.com/discovery-day/). **Workflow** A specific process a user runs, with a clear input and a clear output, that produces a measurable improvement. It is the unit of work shipped in a Sprint. Not a feature, and not a platform. **Output Quality Rubric** A practical checklist, usually on a 1-to-5 scale, that defines what good output from an AI workflow looks like, how the customer's team reviews it, and how the workflow improves over time. It ships as a deliverable with every Sprint. **Sprint Brief** The one-to-two-page document written on Day 1 of a Sprint and signed off by the customer's decision-maker, defining scope, success criteria, deliverables, and what is explicitly out of scope. It is part of the contract. **Workflow Playbook** A short handoff document covering a workflow's purpose, inputs, expected outputs, review steps, edge cases, and maintenance guidance, so the customer's team can run and improve it without the engineer. **Model Context Protocol (MCP)** The open standard Anthropic introduced for letting AI models talk to external systems and data. Many AI workflows connect to a customer's tools and data through MCP servers. **Claude Code** Anthropic's command-line tool for agentic coding. A primary delivery tool for shipping AI workflows directly into a codebase. **AI-native product** A product built around AI workflows from the start, rather than a traditional product with an AI feature added on later. **Vectig** Nasser Ghanemzadeh's AI-native startup finance product: cash-flow forecasting, runway scenarios, and investor update drafting. It serves as the live R&D lab where workflow patterns are proven before they ship to customers. See [vectig.com](https://vectig.com). ### Related - [What is a Forward Deployed AI Engineer?](https://ghanemzadeh.com/forward-deployed-ai-engineer/) - [How to become a Forward Deployed AI Engineer](https://ghanemzadeh.com/how-to-become-a-forward-deployed-ai-engineer/) - [The book: Forward Deployed AI Engineering](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) --- # How to Become a Forward Deployed Engineer (FDE) in 2026 URL: https://ghanemzadeh.com/how-to-become-a-forward-deployed-ai-engineer/ [Forward Deployed AI Engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer/) ## How to become a Forward Deployed AI Engineer You become a Forward Deployed AI Engineer by proving you can take one narrow AI use case from a vague idea to a working feature in a real product, then explain every decision behind it. The fastest credible path is to build and ship one workflow end to end, evaluation rubric included, and be able to walk someone through the code. By [Nasser Ghanemzadeh](https://ghanemzadeh.com/). Last updated August 2026. ### Who already has a head start Most people who do this well arrive from one of three backgrounds: product and software engineering, solutions engineering or consulting, or a founder background. Product engineers bring the ability to ship into a real codebase. Solutions engineers and consultants bring the customer-facing instinct. Founders bring judgment about what is worth building. You do not need all three. You need to be honestly strong in one and willing to build the others. ### The path, step by step - **Get genuinely good at shipping software.** The role is product engineering first. If you cannot ship a feature into a real codebase with edge cases and error states, start there. - **Use frontier models every day.** Work with the current Anthropic and OpenAI models until their behavior is intuitive. Adopt an agentic coding tool like Claude Code as your default way of building. - **Learn prompt and context design.** Reliable output is an engineering problem: system prompts, retrieved context, structured outputs, and guardrails. Treat it like code, not like magic words. - **Learn to connect models to real systems.** Understand the [Model Context Protocol (MCP)](https://ghanemzadeh.com/glossary/#mcp) and how to wire a model into a customer's data and tools safely. - **Build one narrow workflow, end to end.** Pick a real use case with a named user, a clear input, and a clear output. Ship it inside a real product or a convincing clone. Narrow beats ambitious. - **Write the evaluation rubric.** Define what good output looks like on a simple scale and score against it. This discipline is what separates an engineer from someone who got one lucky demo. - **Develop customer-facing judgment.** Practice scoping under pressure, saying no to the wrong workflow, and protecting a fixed timeline. The hardest skill is resisting the pull of a vague request. - **Show the work.** Record a short walkthrough of the code, the prompts, and the rubric. Being able to defend every decision out loud is the real credential. ### What to study, and what to skip Study product engineering, prompt and context design, data integration, and evaluation. You can skip the machine learning research track. The role applies existing models; it does not train them. A research or MLOps background is useful in some engagements, but it is not the entry requirement, and chasing it first is the most common way to delay the thing that actually gets you hired: a shipped workflow. Go deeper ### The book [Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) covers the full path in depth, including a part on becoming an FDE, plus a workbook. It is written from inside the work. ### Related - [What is a Forward Deployed AI Engineer?](https://ghanemzadeh.com/forward-deployed-ai-engineer/) - [Forward Deployed AI Engineer vs solutions engineer](https://ghanemzadeh.com/forward-deployed-ai-engineer-vs-solutions-engineer/) - [Forward Deployed AI Engineering glossary](https://ghanemzadeh.com/glossary/) ### Frequently asked questions #### What background do most Forward Deployed AI Engineers come from? Three backgrounds are most common: product or software engineers who can ship into a real codebase, solutions engineers and consultants who already work with customers, and ex-founders who have built and sold something. The shared trait is the ability to ship and to make decisions in front of a customer. #### How long does it take to become a Forward Deployed AI Engineer? If you can already ship software, the AI-specific layer (prompt and context design, model integration, evaluation) takes weeks of focused practice, not years. The honest gate is not study time. It is whether you have shipped one real AI workflow end to end and can defend every decision in it. #### What should I build to prove I can do the work? Build one narrow workflow with a named user, a clear input, and a clear output, inside a real product or a convincing clone. Ship it, write an evaluation rubric for it, and record a short walkthrough of the code and prompts. That single artifact is more persuasive than any certificate. --- # Free Chapters: Two Books in Your First Email | Nasser Ghanemzadeh URL: https://ghanemzadeh.com/newsletter/ Two books · Four chapters · Free ## Read the first two chapters of both my books. Free. Subscribe to my weekly newsletter and I'll send you the opening chapters of *Forward Deployed AI Engineering* and *Founder Mode* in your first email. After that, one short letter a week: one real decision, run through one mental model. Free. The chapters arrive in your first email. Unsubscribe in one click. 02 · What's inside ### Your first email Two books, four opening chapters, one email. This is what lands in your inbox the moment you subscribe: [Chapters 1 and 2 #### Forward Deployed AI Engineering The first two chapters of the 304-page working guide to the role OpenAI and Anthropic put on the map.](https://ghanemzadeh.com/books/forward-deployed-ai-engineering/) [Chapters 1 and 2 #### Founder Mode The first two chapters on how the great companies are actually built.](https://ghanemzadeh.com/book/) There's no checkout and no download page to dig through. The chapters are just there, in the first email. 03 · Then, every week ### One decision, one mental model The letter is written for founders who invest and investors who build, and it has one job: better judgment. Each week takes one real decision and runs it through one mental model, the same tools *Daily Wisdom* works through a page at a time. No frameworks borrowed from Twitter threads. No promises of overnight scale. Just the decision, the model, and what the model says to do. Get the free chapters - 01 **One real decision.** A hire, a raise, a price, a term sheet, a pivot. Something with money or trust on the line, not a hypothetical. - 02 **One mental model.** Base rates, incentives, inversion, margin of safety. One per letter, in plain words, from the latticework *Daily Wisdom* builds over a year. - 03 **Where the judgment slips.** The misjudgment the model catches, and why it is so easy to miss in the moment. - 04 **What to do on Monday.** The same decision, re-run with the model in hand. Short enough to read in one sitting. 04 · The receipts ### I publish every week [All posts on Substack →](https://ghanemzadeh.substack.com/archive?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [September 15, 2026 #### The book I wished someone else had written Three books in last several years, and why the first one I started is the last one out.](https://ghanemzadeh.substack.com/p/the-book-i-wished-someone-else-had?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [September 9, 2026 #### Cargo Cults: How to Spot a Fake FDE Motion Before You Join It (or Buy It) Anyone can adopt the title and redraw the org chart. The substance is harder to fake, and one test separates the two.](https://ghanemzadeh.substack.com/p/cargo-cults-how-to-spot-a-fake-fde?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [September 2, 2026 #### Breaking Into the Hottest Job in Software Four paths in, a three-project portfolio, and the interview stage everyone underestimates.](https://ghanemzadeh.substack.com/p/breaking-into-the-hottest-job-in?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [August 26, 2026 #### Ship the First Slice The smallest end-to-end system, on real data, with the customer holding the keyboard. And why your first version should be three Python files, not an agent framework.](https://ghanemzadeh.substack.com/p/ship-the-first-slice?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [August 19, 2026 #### Evals Are the New Spec In AI engineering, the evaluation set is the specification, and building the right one is the highest-leverage activity in any engagement.](https://ghanemzadeh.substack.com/p/evals-are-the-new-spec?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [August 12, 2026 #### Validation Is Not Optional: The Three-Phase Engagement Scope, validate, deliver. The middle phase is the one everyone wants to skip, and the one that decides whether the engagement is worth attempting at all.](https://ghanemzadeh.substack.com/p/validation-is-not-optional-the-three?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [August 6, 2026 #### I Fact-Checked My Own Book. It Did Not Go Perfectly. What re-verifying every number in FDE revealed, what the $9 billion summer of forward deployment means, and what version 1.5 adds.](https://ghanemzadeh.substack.com/p/i-fact-checked-my-own-book-it-did?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [August 5, 2026 #### Echo and Delta: The Two Modes of One Craft Palantir split the role in two for a reason. Most AI startups compress it into one person, and the discipline is knowing which mode you're in at any given moment.](https://ghanemzadeh.substack.com/p/echo-and-delta-the-two-modes-of-one?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [July 31, 2026 #### The $29 question Pieter Levels, Fireship, and the end of the micro-SaaS playbook.](https://ghanemzadeh.substack.com/p/the-29-question?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [July 29, 2026 #### The FDE Arbitrage: Why Failed Founders Are the Most Undervalued Talent in AI The labor market discounts failed founders heavily. FDE hiring managers who know better are quietly capturing the spread.](https://ghanemzadeh.substack.com/p/the-fde-arbitrage-why-failed-founders?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [July 23, 2026 #### Gravel Roads and Paved Highways: The Palantir Pattern That Runs the AI Industry For twenty years the industry dismissed Palantir's operating model as a curiosity. Then it became the consensus in about eighteen months.](https://ghanemzadeh.substack.com/p/gravel-roads-and-paved-highways-the?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) - [July 17, 2026 #### The great software rewrite AI coding agents are making it cheaper to rebuild software in Rust, Go, C, and C++. But faster code is only part of the story.](https://ghanemzadeh.substack.com/p/the-great-software-rewrite?utm_source=ghanemzadeh.com&utm_medium=newsletter_page) 05 · Who's writing this ### About I'm Nasser Ghanemzadeh. 17+ years building products and companies across AI, SaaS, and fintech. As CEO and later CPO at Nivo, I shipped AI-powered applications that grew to 200K+ users and 450% revenue growth before the company was acquired. These days I build Vectig solo with Claude Code and run a 10-business-day [AI Feature Sprint](https://ghanemzadeh.com/ai-feature-sprint/) for B2B SaaS teams. The books came out of that work. More on the [home page](https://ghanemzadeh.com/). Forbes · TechCrunch · Al Jazeera · HuffPost 06 · Get the chapters ### Your first email has the chapters in it. Then one letter a week: one real decision through one mental model, for founders who invest and investors who build.