[myownpetard]

Almost every PM I've worked with had an engineering degree and/or previously worked as an engineer. This "Josh" sounds like a strawman or you've had bad luck with PMs in the past.

It also sounds like you have a PM on your team, but they actually have the title of SWE or Eng. Mgr. They probably spend > 50% of their time on the above listed responsibilities rather than engineering. Hopefully they don't get docked in their performance reviews for essentially performing the duties of a PM rather than those of an engineer.

[ath3nd]

I am very much for any SWE or Eng. Mgr taking responsibility and spending as much of their time as they see fit on anything they see fit to build a great product. Not only that, but I will encourage them to continue doing so and give them a great review score and potentially a salary bump!

> Performing the duties of a PM rather than those of an engineer.

The duties of an engineer are to know what to build, prioritize it against their other work, and build it, alon with the other engineer in their team. If you consider the "knowing what to build/prioritize" as PM work, so be it. I consider it engineering work.

[PH95VuimJjqBqy]

most PM's will have worked < 5 years (typically 1-2) before moving onto the PM track.

There's a world of difference between a senior developer and what these guys are, and you want your senior developers making these calls.