The Return of the Product-Minded Software Engineer

“Only a few years ago, 10 engineers were responsible for innovating, building, and maintaining all of the products—also known as features—on Facebook, including Profiles, Pages, Groups, Messages, Photos, and Events. These people were our first product engineers, a role that is a mix of generalist engineer, product designer, and product manager.” - Bob Baldwin, Michael Novati

In the 2000s, software engineers often played a central role in defining product features, guided by business needs and user feedback. Facebook publicly described this model in its article Product Engineering at Facebook.

As systems became increasingly complex and product management matured as a discipline, these responsibilities gradually became more separated. Engineers became more focused on implementation, while product decisions moved further toward specialized product roles.

I’m glad to see this relationship returning to its roots—where it arguably should never have left. Product-minded engineering is not about making engineers replace product managers or designers. It is about bringing technical expertise closer to user needs, business context, experimentation, and measurable outcomes.

This is especially timely now that AI tools can help absorb part of the complexity involved in building software, giving engineers more room to think about the product, the users, and the trade-offs—not just the implementation.

I’m very glad that Drew Hoskins wrote The Product-Minded Engineer: Building Impactful Software for Your Users at such an important moment. The book provides a thoughtful perspective on how engineers can take greater ownership of the problems they are solving and the impact their software creates.

Gergely Orosz also wrote a review of the book, The Product-Minded Engineer: The Importance of Good Errors and Warnings, where you can find more details and a preview of one of the book’s chapters.