In short
A chip program manager holds a tape-out or product date across design, verification, physical design, IP vendors, the foundry, packaging, test, firmware and the customer. Most of the week is finding out what is true and chasing what moved. When software holds the commitments and does the chasing, the role becomes what it was meant to be: deciding trade-offs, settling conflicts, and representing the program to the customer and the executives.
The job as it is
Weekly reviews prepared from a dozen sources. Status chased from engineers who would rather be engineering. A schedule maintained by hand that is wrong somewhere every day. Escalations that arrive late because the signal was in a tool nobody checked. The judgment the role exists for, which risk to take, which team to move, what to tell the customer, happens in the margins.
The job when the date is held by software
Tymeline holds every commitment against its evidence, re-plans dependent work the hour something moves, and puts the worked-out fix in front of the owner. The program manager stops collecting and starts deciding. Reviews become short, because they are about exceptions with the recovery already underway. The role gets its afternoons back, and the program gets a manager who is thinking.
What the role keeps
Every consequential decision. The authority envelope that says what the software may do without asking is set by the company, and the program manager is usually the named approver inside it. The record of every action is there to read. The job is not replaced; the chasing is.