Feels like the PM / engineer boundary is getting weird/close lately. Engineers are doing more “PM stuff” than they used to; writing specs, defining success metrics, figuring out what to build instead of just implementing tickets. Engineers are obvisouly getting faster at writing code. We’re moving to what Martin Fowler calls the middle loop , “A new category of supervisory engineering work is forming between inner-loop coding and outer-loop delivery.” We’re defining more specs and spending more time in the backlog than ever. At the same time PMs are doing more “engineering stuff”; creating prototypes, running experiments themselves, writing analytics, even pushing code to prod. So you see two opposite narratives floating around “Engineers are replacing PMs”, “PMs are becoming builders” (see r/ProductManagement ) But honestly I don’t think either role will replace the other. What seems more likely is that the roles are just collapsing into something else: product engineers . People who sit across both sides because the cost of switching contexts between “product thinking” and “building” has dropped massively. AI tools make it easier for PMs to prototype. Better tooling + analytics makes it easier for engineers to reason about product decisions. So instead of a handoff between roles, one person can just… do the loop. Problem -> idea -> prototype -> measure -> iterate Curious how people here see it submitted by /u/magicsrb
Originally posted by u/magicsrb on r/ClaudeCode
You must log in or # to comment.