Amen. I've worked at a startup where the barrier to entry for a PM role was either low (in my perception) or they were allowed to get better at their job as the project progressed. Features were conjured up only to be canned after it was baked into the product and higher-ups shot things down.
The codebase was a total mess.
On the flip side, I've found experienced QA folks wanting to move up the corporate hierarchy by upskilling into PM roles a pleasure to work with, especially when it came to setting expectations upstream and estimating timelines.
Amen. I've worked at a startup where the barrier to entry for a PM role was either low (in my perception) or they were allowed to get better at their job as the project progressed. Features were conjured up only to be canned after it was baked into the product and higher-ups shot things down.
The codebase was a total mess.
On the flip side, I've found experienced QA folks wanting to move up the corporate hierarchy by upskilling into PM roles a pleasure to work with, especially when it came to setting expectations upstream and estimating timelines.