Forward Deployed Engineering: Why Domain Experts Win Now

A real estate investor with no software background built his own property management app rather than keep paying a 16% management fee. That single move is the clearest evidence yet that coding syntax has stopped being the scarce skill in software. AI tools like Claude Code and OpenAI Codex already write fluent code. What they can't do is know which problem is worth solving, or what "correct" looks like for your specific business. That gap has a name now: forward deployed engineering, and it's turning solo creators and small-business owners into builders without a computer science degree in sight.

The term "forward deployed engineer" started as enterprise-tech jargon for engineers who sit physically embedded with a client instead of working remotely, borrowed from the military sense of putting people on the front lines. It's become a hybrid role that blends product management, customer-facing implementation, and actual software engineering into one person who owns a business outcome end to end, not just a codebase.

This isn't a niche title anymore. TechCrunch reports a search-firm study finding only around 2,000 U.S. engineers currently combine real sector expertise with applied-AI experience, and projects FDE demand to surge 2,100% by year-end. The money backing that bet is real: AWS has committed $1 billion to a forward-deployed engineering unit, Anthropic has a $1.5B+ joint venture with Blackstone, Hellman & Friedman, and Goldman Sachs, and OpenAI's Deployment Company is capitalized north of $4 billion. On YouTube, creator Nate B Jones broke down what that looks like in take-home pay: "OpenAI is hiring forward deployed engineers at up to $280,000 in base pay plus equity... Handshake has posted the same title at $300,000."

It's a fair pushback, and the episode addresses it directly: a traditional consultant sits with a client, diagnoses the problem, and hands over a slide deck of recommendations. Then you still have to go hire a dev team to build it. A forward deployed engineer skips the handoff. They understand the customer's problem and ship the working software on the spot, using AI to close the gap between diagnosis and deployed code. The output isn't a recommendation; it's a running app.

The clearest illustration is the smallest one. A real estate investor with zero software background got tired of paying a property management company a 16% fee, so he built his own property management software instead. He didn't need to learn to code from scratch. He needed to know exactly what his business required, and current AI tools were fluent enough to translate that into working software. That's the actual shift: the moat isn't the code anymore, it's knowing precisely what needs to be built.

The workflow that makes this repeatable follows a simple split: humans own the first 5% (defining intent and the architecture) and the last 5% (reviewing whether the output actually solves the real problem). The AI handles the noisy 90% in the middle: writing the actual code. That final 5% matters most, because AI doesn't know if software solves a real-world problem. It only knows whether the code compiles. You still need a domain expert to look at the result and say "this workflow doesn't make sense for a property manager."

The mechanical unlock behind all of this is local environment access. Instead of copying and pasting code snippets back and forth from a browser, tools like Claude Code and OpenAI Codex get permission to read your actual file folders, then write code directly into your project the way a remote engineer would. That's what lets a non-coder spin up a custom dashboard from a folder of receipts, or automate a daily email triage system, entirely on their own machine. The best analogy from the episode: it's less like having a magic wand and more like having an incredibly fast, highly skilled typist who happens to be blindfolded. Flawless execution, but they need you, the domain expert, to be their eyes and describe the blueprint.

If every solo creator and small business can now generate bespoke software tailored to their exact workflow, the open question is whether the massive, one-size-fits-all SaaS platforms eventually lose their edge. Software-as-a-service has always traded flexibility for scale. That trade only wins if building your own alternative stays expensive. Forward deployed engineering, at the individual scale, is a bet that it no longer does.

Anthropic's own research backs the underlying claim. Analyzing roughly 400,000 Claude Code sessions across 235,000 users, the company found non-software occupations hit a 29% verified success rate on code-producing tasks against 34% for software engineers, a five-point gap, with every major occupation landing within seven points of professional engineers. As @AndrewLeeWard put it on X: "AI coding agents are turning domain knowledge into a software skill. That is the part many hiring plans still have not caught up with." Writer @wstickevers went further, calling 40 years of "learn to code, leave your old industry behind" career advice "almost completely backward," since it tells people to discard the one advantage they already have.

Not everyone is convinced. On Reddit, r/cscareerquestions and r/ExperiencedDevs are running an active counter-narrative, with threads like "My entire software development workflow is AI now, and it feels both exhausting and soulless" pulling nearly 1,500 upvotes. On TikTok, @vaguely_aware pushed back hard under an FDE hype video: "Fellow SWE here. We see LLMs f*** up constantly in every day usage, but somehow people think they can code better than a real software engineer?" AI still makes mistakes, still hallucinates, still picks inefficient paths. That's exactly why the domain expert doing final QA matters as much as the code itself.

What is a forward deployed engineer?
A forward deployed engineer (FDE) is a hybrid role that combines software engineering, product management, and customer-facing implementation, typically embedded directly with a client to turn their real business problem into deployed, working software rather than a recommendation.

Do I need to learn to code to build my own software now?
Not necessarily. Current AI coding tools like Claude Code and OpenAI Codex can write functional software from plain-language instructions when given access to your local files. What you need instead is deep, specific knowledge of the problem you're solving. The AI can't supply that part.

How is forward deployed engineering different from hiring a consultant?
A consultant typically diagnoses a problem and hands over recommendations, leaving you to find a team to build the solution. A forward deployed engineer (or a domain expert acting like one) skips that handoff and ships the working software directly, using AI to close the gap between the business problem and deployed code.

What is the "5-90-5 rule" mentioned in the episode?
It's a framework for dividing labor between a human and an AI coding tool: the human owns the first 5% (defining intent and architecture) and the last 5% (quality control, checking the output actually solves the real problem), while AI handles the messy 90% in the middle, writing the code itself.

Watch the full episode:

If this playbook is useful, get more daily breakdowns of what's actually working in AI agents, coding tools, and automation at joebuildsai.com, built for solo creators and small teams who don't have time to track it all themselves.