Aller au contenu

Should "Product Engineer" Be A Job Title? (with Phil Hornby)

20 octobre 2026 · 34 min

Notes de l’épisode

Where should the line between product management and engineering sit? And in a world where AI is making it easier for anyone to build software, do we even need that boundary anymore?

In this episode of The Product Engineering Podcast, James is joined by Phil Hornby, product leadership coach, founder of For Product People and host of the Talking Roadmaps podcast, to explore the increasingly blurred boundaries between product management and engineering.

Drawing on Phil's experience across both engineering and product leadership, we discuss whether organisations should define responsibilities around job titles or build teams around the strengths of the people within them.

We explore what it really means to be a Product Engineer, why engineers should get closer to customers and business decisions, and whether AI could eventually enable individuals to take on responsibilities that previously required entire cross-functional teams.

We cover:

  • Where the boundary between product management and engineering should sit, and whether we need one at all
  • Why organisations should be designed around people's individual strengths rather than rigid job descriptions
  • How engineers can participate directly in product discovery without becoming product managers
  • The difference between understanding users and understanding the customers who actually pay for a product
  • Why product management is as much about business strategy, pricing and commercial viability as it is about user experience
  • Whether AI makes the idea of a one-person product engineering team realistic
  • Using AI and personal knowledge management systems to capture context, accelerate thinking and improve writing
  • Why storytelling is an essential skill for communicating customer problems to engineering teams
  • The danger of using AI to turn feature requests directly into working software without understanding the underlying problem
  • The trade-offs between generalist Product Engineers and deeply specialised engineering teams
  • How different organisational structures, from functional organisations to cross-functional teams, can both be successful
  • Why engineers should become more curious about customers, business models and the commercial outcomes their work supports

A recurring theme is that high-performing teams aren't created by finding people who fit neatly into predefined roles. They're created by combining people with complementary strengths and giving them the freedom to contribute where they can add the most value.

We finish with Phil's advice for engineers who want to become more product-focused: stop worrying so much about the terminology and start developing genuine curiosity about your customers, your users and your business.

Find Phil:

  • For Product People: Phil's product leadership coaching and training
  • Talking Roadmaps: Phil's podcast exploring product roadmaps and product leadership
  • LinkedIn: Search for Phil Hornby

Tous les épisodes de The Product Engineering Podcast

Paramètres

Affichage

Langue

Détermine les stations affichées en premier sur la page d’accueil.

Historique

Les stations et épisodes écoutés récemment et tes dernières recherches sont seulement enregistrés dans ce navigateur.

Notifications

Un court message quand un podcast que tu suis publie un nouvel épisode. Désactive un podcast précis avec la cloche sur sa page.

Compte

Enregistrez vos favoris – dans l’app et sur le site.

Raccourcis clavier

/
Ouvrir la recherche
Espace
Lecture ou pause
← →
Dans le lecteur : 15 s en arrière, 30 s en avant (épisodes) · dans une rangée : tuile suivante
↑ ↓
Dans une rangée : cible dans la tuile
Début / Fin
Dans une rangée : première ou dernière tuile
Esc
Fermer la fenêtre ou le menu
?
Cet aperçu
En cours de lecture

Voir la station

À suivre

    Ajoutez des épisodes avec « À suivre » – ils seront lus après l'épisode en cours.