Skip to Content
View all events

The Forward Deployed Engineer (FDE)

Published by O'Reilly Media, Inc.

Intermediate content levelIntermediate

A one-hour overview of the newest role in software development

What you’ll learn and how you can apply it

  • Describe what a forward deployed engineer owns across a customer engagement, and what belongs to other roles
  • Distinguish genuine FDE work from AI engineering, solutions architecture, and consulting when evaluating a role, course, or job posting
  • Map your own experience against the role’s core demands and identify where your background translates and where it doesn’t

Course description

Forward deployed engineer is one of the fastest-growing job titles in AI, and one of the least well defined. The role asks a single engineer to own an entire customer engagement: discovery, scoping, build, deployment, verification, and the customer relationship itself, all inside a company that isn’t their own. Because the definition is still unsettled, a lot of content labeled FDE is really AI engineering under a different name, which makes it hard to evaluate roles, job postings, and training with any confidence.

Paden Gayle, who’s already working in the role, gives you a grounded picture of what it involves. You’ll follow a real engagement from ask to shipped result, making your own calls at key decision points and comparing them with what actually happened. You’ll see how the role differs from software engineering, solutions architecture, and ML engineering. In the final exercise you’ll map your own work against the role’s core demands, and leave with a realistic view of your readiness for this role and a good idea of whether it’s a good fit for you.

This live event is for you because...

  • You’re a software engineer, solutions architect, or ML practitioner wondering whether the FDE role fits your background.
  • You work in consulting or technical delivery and want to know how customer-facing experience maps to the role.
  • You’re evaluating FDE job postings or doing the hiring for this role, and you need a better definition of what it entails.

Prerequisites

  • Some experience in software engineering, consulting, or technical delivery

Recommended preparation:

  • Jot down your main projects and responsibilities from the past two years for use in the final exercise

Recommended follow-up:

Schedule

The time frames are only estimates and may vary according to how the class is progressing.

What the role is (15 minutes)

  • Presentation: The mandate—one engineer owns discovery, scoping, build, deployment, verification, and the customer relationship inside a company that is not theirs; where the role came from, why it’s growing now, and why the definition is still unsettled; what an FDE owns and what belongs to someone else
  • Q&A

What the work looks like (15 minutes)

  • Presentation: One real sanitized engagement from start to finish—the vague ask, discovery, scoping, the constraint that nearly killed it, ship, and proof; a week in the role—the meetings, the customer, the code, and the ratio between them
  • Hands-on exercise: Decide what you’d do next
  • Q&A

How it’s different, and why the confusion (15 minutes)

  • Presentation: FDE versus software engineer, solutions architect, and ML engineer, drawn through ownership rather than skills; the overlap is real, the equivalence isn’t; why so much content labeled FDE is actually AI engineering; how to tell the difference when evaluating a role, a course, or a job posting
  • Group discussion: What did you think FDE work was before you took this course?

Who it’s for (15 minutes)

  • Presentation: The engineering, consulting, and delivery experience that maps to the role’s demands; which gaps matter; what the career path looks like from inside; the reasons the role doesn’t fit everyone
  • Hands-on exercise: Map your last two years of work against the role’s five core demands and identify your strongest bridge and biggest
  • Q&A

Your Instructor

Paden Gayle

Paden Gayle is a Forward Deployed AI Engineer at Notion, where he builds and deploys production AI systems inside enterprise environments. His path to the role did not run through a computer science degree. It ran from Juilliard, through business school, into client delivery as a technical architect at Accenture, and into software engineering at Bloomberg and Google, before he became one of the first software engineers to formally move into the Forward Deployed AI Engineer role, the same move this book exists to teach. The winding route is not a footnote. The job is part engineer, part solutions consultant, part product thinker, part founder, and every stop on that path handed him one of the parts. He writes from inside the role rather than about it: the patterns, the deployment failures, the customer realities, and the career path in these pages come from current production work, not from research or summary.

Skill covered

Interviewing for a Job