FDO School | Forward Deployed Operator Program

The Role

What is a Forward Deployed Operator?

A Forward Deployed Operator works between the business, its people, and its systems to turn messy processes into AI deployments that perform in daily work. The role combines workflow discovery, systems thinking, technical judgment, stakeholder adoption, and business proof.

The precedent

You already know the Forward Deployed Engineer.

Palantir coined the title. Today FDE roles appear at Scale AI, Anduril, Databricks, and hundreds of startups. Then the largest companies in AI placed the same bet within weeks of each other. Anthropic, OpenAI, AWS, and Microsoft all launched dedicated deployment ventures. The market validated the model: embed a technical person at the point of impact.

729%YoY increase in FDE postings

~$9BCommitted to deployment ventures

70%Of companies plan to hire FDEs

$200–350K+Mid-senior FDE compensation

The gap

But FDEs come from engineering. The need comes from the business.

What companies actually need now are people from the business side who've learned to build with AI and no-code tools. People who understand the work deeply enough to deploy the right system and earn adoption from the people who use it. That skill set has been scattered across siloed functions:

Solutions Architect RevOps Marketing Ops People Ops BizOps Systems Admin

The FDO is the evolution.

Not locked to one function. Not limited to pre-sales or a single ops silo. An FDO works across the business, builds and owns the systems, and proves the impact, in an AI-native way.

Why this role needs building

The work exists. The role doesn’t.

Companies already depend on people who do this. But there’s no job title, no posting, and no training pipeline — so the work stays invisible and the career path stays stuck.

AI changed the stakes.

Every company is deploying AI. Few have someone who can bridge the gap between what the technology can do and what the business actually needs done.

Proof is the bottleneck.

The best operators do this work inside a company where nobody outside can see it. Without a way to show judgment and impact, the career dead-ends.

Sound familiar?

If this is your Monday, the work already has a name.

01

Cross-functional fixer

Problems that cross teams, tools, and job descriptions land on your desk first.

02

Ambiguity → systems

You turn unclear business needs into workflows, decisions, and working processes.

03

AI judgment calls

You know where AI belongs, and where deterministic automation will outperform it.

04

Builder + adopter

You ship the system and earn trust from the people expected to use it.

05

Tech ↔ business proof

You connect technical decisions to operational and financial outcomes.

06

Invisible impact

Your strongest work lives inside your company, and it's nearly impossible to show.

10 seats per cohort

Here's who fills them.

Ops-minded generalist

You work across teams, tools, and job descriptions.

3+ years in ops roles

RevOps, BizOps, Solutions, People Ops, or similar.

Builds with AI & no-code

Zapier, Make, Retool, or AI assistants in a work context.

Ready to show the work

Build in the open and present at Demo Day.

Not the right fit if Looking for a passive course No operational experience Need AI fundamentals from scratch

See who's hiring →

From the Founder

We built the school we wish existed. And we teach it ourselves.

Ysimer "Ysi" Gonzalez

CEO and Principal Forward Deployed Operator

Founder of FDO School and Embedded Operations Partner for founder-led companies that have outgrown their early scrappy systems: mapping what's actually happening, surfacing hidden workarounds, and building simple, durable systems that scale without firefighting.

Eighteen years of Fortune 500 supply chain across ABB, Pratt & Whitney, Bombardier, and Bell Canada. She co-leads every session and brings the enterprise operations lens to every deployment review.

The Program

Eight weeks. One real deployment.

Every fellow owns a sponsored project matched to their individual goals. You run the deployment. You make the calls. Each week ends with an artifact gate that moves your work from diagnosis toward proof.

Your project. Your proof.

One sponsored problem, one fellow. You own the sponsor relationship, the user conversations, and the live build from start to finish.

Never alone.

Every fellow is paired with an accountability buddy, matched by complementary strengths, to pressure-test decisions, trade feedback, and keep each other sharp.

Week 00

Setup

Onboarding, sponsor intros, project scoping.

Week 01

Position

Articulate what you do in one sentence the market pays for.

Week 02

Diagnose

Map what really happens, including the parts nobody documents.

Week 03

Decide

Evaluate build, buy, and rent. Defend the call.

Week 04

Build

Create the smallest useful version that moves a real number.

Week 05

Test

Put it in front of real users. Observe where it breaks.

Week 06

Deploy

Hand off with docs so the system survives without you.

Week 07

Prove

Turn the deployment into a measured case study.

Week 08

Demo Day

Present your finished proof packet to a room of hiring managers, sponsors, and the cohort. This is where the work becomes visible.

FAQ

Common questions.

Do fellows need to write code?

No. This program is built for people from the business side, not developers. Fellows build with AI tools, no-code platforms, and automation systems. The emphasis is on judgment, adoption, and proving business impact, not writing software.

How much does the program cost?

$3,000 USD for the live cohort. This includes eight weeks of live sessions, a sponsored deployment on a real company problem, mentor access, artifact reviews, Demo Day, and warm introductions to hiring partners. We're also developing a more async, self-paced version at a lower price point. Join the waitlist to hear when it's available.

What if my sponsored project doesn't go well?

That's part of the work. Not every deployment will be a home run, and we don't expect it. What matters is how you diagnose, decide, adapt, and document. Your proof packet captures your judgment and process, not just the outcome. Some of the strongest case studies come from projects that hit real friction.

Can I do this alongside a full-time job?

Yes, the program is designed for working professionals. Expect 5 to 7 hours per week, including one live session and the rest spent on your deployment. Weeks 4 and 5 run heavier as builds move into testing. All sessions are recorded if you miss one.

What happens after Demo Day?

You leave with a finished proof packet: a working deployment, a measured case study, a positioning statement, and a competency profile. We also make warm introductions to hiring partners who attend Demo Day and our network. The proof packet is yours to use in interviews, on LinkedIn, or in proposals.

Is this remote or in person?

Fully remote. Live sessions run on video. Sponsor and user conversations happen async or over calls, depending on the project. Fellows have come from across the US and internationally.

Cohort 02

Next time, be first in line.

Applications for Cohort 02 open this fall. Waitlist members hear first.

For Mentors, Speakers, and Hiring Partners

Work with the next cohort.

Mentor a fellow mid-deployment, speak to the cohort about a real project, or get early access to operators with proof-of-work before they hit the market.

You've been doing the work. Now make it count.

Cohort 02 opens this fall. Ten seats, eight weeks, one real deployment, and the proof packet that makes the work legible to any hiring manager.

Join the Waitlist For Mentors & Partners

Seats limited by design.

Every system you fixed became someone else's win. The next one has your name on it.