The journey of a Software Engineer

Software Engineering, Programming, Cloud, AI and anything that need a fix.

The rise of Forward Deployed Engineers

The rise of Forward Deployed Engineering (FDE) is stirring up some serious conversation in tech circles. As someone who’s navigated the often murky waters of software engineering, I find this intersection of engineering, consulting, and product management both fascinating and a little concerning. It’s like a cocktail made out of…

The rise of Forward Deployed Engineering (FDE) is stirring up some serious conversation in tech circles. As someone who’s navigated the often murky waters of software engineering, I find this intersection of engineering, consulting, and product management both fascinating and a little concerning. It’s like a cocktail made out of different spirits that might just leave you with a hangover if you’re not careful about how you mix them. FDE positions are allegedly designed to bridge the gap between complex technical products and non-technical customers, but are we just falling for another tech industry buzzword?

Let’s break down what FDE really is. The role is often misidentified as a rebranding of sales engineering or a form of professional services. That’s a simplistic view. In reality, FDE encompasses much more. It demands a unique skill set that combines technical know-how with the ability to communicate effectively with stakeholders who might not even know the difference between a function and a feature. It’s not enough to just write good code; you have to be a translator, a therapist, and sometimes even a magician, making complex systems understandable to those uninitiated in the intricacies of software.

This leads us into the controversial territory of whether FDE is a sustainable role. Some argue it’s essential for companies selling highly technical products to non-technical buyers. But what happens when the hype fades? Are we setting ourselves up for another round of layoffs as companies realize they don’t actually need a dedicated team of FDEs when they could just train their salespeople in basic tech skills? A lot of the conversation around FDE paints it as the next big thing, but the question remains: are we overhyping it?

There’s also the issue of talent. The ideal FDE is described as a unicorn—someone with a strong technical background, high emotional intelligence, and the ability to work autonomously across various departments. But as any seasoned engineer will tell you, unicorns are notoriously hard to find and even harder to keep. The war for talent is real, and if companies don’t start offering competitive salaries and growth opportunities, they might find their FDE teams lacking.

A common refrain is that FDEs are crucial for providing feedback loops between customers and engineering teams. This sounds great on paper, but in practice, how often does that feedback actually lead to meaningful changes? How many times have we heard about companies that shun customer input until it’s too late? Companies often collect data but fail to act on it. If the FDEs are merely there to collect dust on a shelf, then what’s the point?

Another perplexing aspect of FDE is the notion that they should be able to operate in any industry without losing credibility. This is a tall order, especially in industries with their own jargon and paradigms. The idea of being a jack-of-all-trades can often lead to being a master of none. For example, an FDE working with a bank might struggle to gain the trust of a CIO if they can’t speak the lingo of asset management and risk mitigation. Therefore, is it feasible to expect these engineers to be so versatile without extensive training and experience in specific industries?

And let’s not forget the pressure on FDEs to deliver results quickly. Companies are notoriously impatient, often expecting rapid turnaround times for complex problems. This can lead to burnout, not to mention a decline in the quality of work. The very essence of what makes an FDE valuable—their ability to listen, adapt, and create tailored solutions—can be compromised when they’re pushed to meet unrealistic deadlines. The FDE role, while promising, could easily devolve into just another cog in the corporate machine if not managed carefully.

What’s clear is that FDE has the potential to revolutionize how companies interact with their clients. But it’s not without its pitfalls. The buzz around FDE could either usher in a new era of customer-focused engineering or it could become yet another corporate fad that fizzles out when the next shiny object appears. The future of FDE will largely depend on how well we manage the expectations, the talent acquisition, and the integration of this role into the broader corporate culture. As we look ahead, let’s not just chase the next big thing; let’s be mindful of the structural changes that could make—or break—this promising new role.

Sources

https://youtu.be/APqXGyCoGW4?si=eRxUp-rtGeov9joe

https://youtu.be/Ck-LeYlAVbY?si=EaJ_6Q4Xmqr4h57y

+

Discover more from The journey of a Software Engineer

Subscribe now to keep reading and get access to the full archive.

Continue reading