The FDE Gap Isn't Just a Hiring Problem—It's a Market Signal

I stumbled on this piece from Gergely Orosz at The Pragmatic Engineer about why the Forward Deployed Engineer role is struggling to attract talent. He points to job postings growing tenfold while only 10% of engineers want the job, citing interviews with disappointed FDEs who found the work more like sales engineering than software development.

Here's what Gergely's analysis misses: this isn't just a tech company hiring problem. It's a structural market inefficiency that shows up across 92 industries in our data. When businesses need technical implementation but developers prefer building products, you get a gap that creates real operational pain—and real opportunity.

Our platform tracks 2,494 problems across every industry from manufacturing to healthcare. What stands out is how consistently businesses struggle with implementation work. We've got 47 problems specifically related to customer onboarding and implementation, with an average severity score of 4.1 out of 5. That's not minor inconvenience—that's business-critical pain. Yet when we surface app ideas to solve these implementation challenges, they get 30% fewer developer submissions than product-focused opportunities.

Gergely focuses on companies like OpenAI and Ramp, and his anecdotes ring true. But our data shows this pattern extends far beyond tech giants. In Workflow Automation alone, we track 18 problems with average severity 3.8/5—persistent operational friction that businesses desperately want solved but struggle to staff internally. The FDE role might be the most visible manifestation of this gap in tech, but it's the same fundamental mismatch playing out everywhere: business needs technical implementation, technical talent prefers product development.

This creates what I'd call a classic market signal. High demand meets low supply, and the gap doesn't close because the work itself feels misaligned with what many developers find rewarding. One engineer told Gergely their FDE role felt like "a typical IT services mindset" where they were used "more on the engagement lead side, and nothing on software development." That's the exact mismatch our data reveals across industries.

For indie hackers and agency developers, this represents something more interesting than just another hiring challenge. It's a market opportunity hiding in plain sight. When a business need is widespread but the traditional staffing solution isn't working, that's when tools, platforms, and new business models emerge. The companies that figure out how to make implementation work more efficient—or more appealing to technical talent—will capture value that's currently being left on the table.

Think about what happens when you can't hire enough FDEs: projects stall, customer implementations drag on, technical debt accumulates in customer-specific solutions. Our data shows these aren't hypotheticals—they're daily realities for businesses trying to deploy and maintain technical solutions. The severity scores tell the story: implementation problems consistently rank among the most painful operational challenges businesses face.

What's fascinating is how this connects to broader trends in software development. As tools get more powerful and abstraction layers improve, the actual coding part of implementation work should theoretically become easier. But the human coordination, customization, and customer-facing aspects remain stubbornly resistant to automation. That's why the FDE role exists in the first place—and why it feels so different from traditional software engineering.

For seed investors, this pattern should look familiar. Market gaps where business demand outpaces available talent often precede the emergence of platform companies. The question isn't whether FDE roles will become more desirable—it's what new tools and business models will emerge to bridge this implementation gap. Our data suggests we're still in the early innings of this shift.

Gergely's piece does excellent work highlighting the human side of this equation—engineers taking roles expecting software development work and finding something entirely different. But the business side is equally important. When companies can't staff implementation roles adequately, they either accept suboptimal outcomes or look for alternative solutions. That's where the opportunity lies.

If you're building in this space, the signal is clear. Look at the problems businesses actually face with implementation, integration, and customer-specific solutions. Our Workflow Automation problems show consistent patterns of friction. The solutions that succeed won't just make implementation faster—they'll make it more aligned with how technical talent wants to work, or they'll abstract away the parts that create the mismatch in the first place.

This is one of those rare situations where everyone's right. Engineers are right that many FDE roles don't feel like traditional software engineering. Businesses are right that they need this work done. And the market is right that there's opportunity in bridging that gap. The companies that figure this out won't just solve a hiring problem—they'll tap into a fundamental market inefficiency that shows up across industries.

Sometimes the most interesting opportunities come from looking at what everyone agrees is broken. The FDE role discussion reveals more than just hiring challenges—it shows where business needs and technical preferences diverge. And in that divergence, there's space to build something new.