For years, the PM-engineering relationship ran on a quiet, unspoken contract: they build, you prioritize. You owned the what, they owned the how, and the gap between you was measured in Jira tickets and sprint reviews. That contract is dissolving. Agentic AI is changing what it means to be an engineer — not by replacing them, but by elevating them out of the code and into the architecture of ideas. Your best engineers are no longer defined by what they can write; they're defined by what they can orchestrate, review, and direct. Which, if you squint a bit, probably looks a bit like what you do as a PM. You may start asking: is your role at risk? Do we no longer need engineers? This line of thinking is almost certainly unproductive. Effective product managers understand how the job of engineering is changing and how that makes the role of PM even more necessary. The ground is shifting under us. This talk is about how we can adapt. We'll get into what the PM role looks like when your engineers are orchestrating AI rather than writing logic, and how the best product teams are already reorganizing around this reality. The temptation is to move quickly, the winners will be the ones who move in the right direction.