A first ninety days reading list, ordered so each book answers the question the last one raises.
If you have just moved into product, the difficulty is not a shortage of advice but knowing what to read first. This is a sequence rather than a pile. Each book answers a question the previous one leaves open, and the whole list is readable in a first few months without stopping the day job.
Start here. Describes the job as it actually is, including the ambiguity, before you read the books describing how it should be.
What good looks like, so you have a reference point for the gap between your organisation and a strong one.
The first practical skill to get right. You can apply it in your first week and it stops you gathering useless research.
Ninety pages on the distinction that everything else in the job hangs from. Read it in one sitting.
The bridge from what you learn to what the team actually builds, and how to keep a backlog comprehensible.
By now you will recognise the pattern in your own company. This gives you the language and the argument for changing it.
The influence skills that decide whether any of the above lands, given you own an outcome but manage nobody.
If you came from outside engineering, this fills the technical gaps in plain language without requiring you to code.