Also agreed that you really have to enjoy meetings. It's no longer a development role. It's a role where you become the communication line between the dev team and the client/users/QA/other depts.
You have to really understand what people are saying even when they're not saying. You also have to be really good at reading body language - people slouching when they're stuck or on something, or their eyes lighting up when you tell them something they want to hear. You have to be good at giving the right questions to unlock these answers.
It's incredibly difficult to go from being developer to product because product does everything developers shouldn't be doing.
I'd say the fastest route is to be a startup founder. A slightly slower route is to take on the product role at your company, but this usually means a performance hit because you can't develop well when 2-4 days of your week are dedicated to meetings.
You can also directly ask your boss if you can transition into the role. People who want to take product roles are very rare and expensive, and developers are much more valuable for the role vs people who took some certification.