[existencebox]

I've definitely felt that sentiment as well. What both backs my "feeling" and hints at the heart of things is in something I've heard said verbatim on multiple occasions: "We need to do X; I don't even need to be an engineer to understand it" where X is a deep engineering topic, e.g. a full re-architect of a relational backed platform as streaming. (Also, "PM work is far more difficult than engineering work" said by a just hired PM to the faces of the 4 senior engineers assigned under him... you can imagine how that went).

For the former quote I've found there to be hope, since you can engage the "it's so easy, I see how you can do it" the same way _we_ engage ourselves, making them deconstruct the problem to the end of running them into a common design issue (in my sample it was asking the PM to reason about long-horizon backfill and replay logic); it can even have a positive outcome if you explain it such that the PM gains trust in your insight, and may help to build some of that respect.

In the latter, when there is simply as you say a LACK of respect, and not just a... shall we say communication gap? Those are the situations I've seen some of the more painful PM/dev interactions and I have far less helpful advice, unfortunately, since I'll admit that the problem then resonates, as eng loses respect for PMs who don't respect them and etc etc.

Sorry for the ramble, this has been a topic I've thought about a lot WRT "implicit problems in scaling a company past a certain size"