{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Product Engineering Podcast","title":"Should \"Product Engineer\" Be A Job Title? (with Phil Hornby)","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/6ca7ecc6\"></iframe>","width":"100%","height":180,"duration":2010,"description":"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?\nIn 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.\nDrawing 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.\nWe 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.\nWe cover:\nWhere the boundary between product management and engineering should sit, and whether we need one at all\nWhy organisations should be designed around people's individual strengths rather than rigid job descriptions\nHow engineers can participate directly in product discovery without becoming product managers\nThe difference between understanding users and understanding the customers who actually pay for a product\nWhy product management is as much about business strategy, pricing and commercial viability as it is about user experience\nWhether AI makes the idea of a one-person product engineering team realistic\nUsing AI and personal knowledge management systems to capture context, accelerate thinking and improve writing\nWhy storytelling is an essential skill for communicating customer problems to engineering teams\nThe danger of using AI to turn feature requests directly into working software without understanding the underlying problem\nThe trade-offs between generalist Product Engineers and deeply specialised engineering teams\nHow...","thumbnail_url":"https://img.transistorcdn.com/tOpN0tMoB9dtDg__O2XafuXKrZuomc_ze_mLWYIpO7A/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS83Mjc4/NGQwOThhMzkyZGVm/ZmFjYmQ3N2NkMDcz/YWNlYS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}