Determination, evaluation, and articulation of requirements is the sweet spot of the product manager role. Understanding those requirements is certainly necessary for an engineer to build to the requirements.
Once upon a time, this too was a formalized practice in engineering that people called "Systems Engineering":
https://en.wikipedia.org/wiki/Systems_engineering
https://www.nasa.gov/reference/2-0-fundamentals-of-systems-e...
Writing good code is a very separate skill set from that kind of problem-space work, and software engineers are mostly hired for the former.
Imagine developing an AAA game with no one in charge of the overall product. Or creating a movie without a producer or a director, expecting the talent to somehow organise itself.
PM isn't an engineering job, it's a vision job - one that needs enough technical knowledge to create a vision that's grounded in reality, while also appealing to customers, while also being able to sell it up and down the org.
That skillset is incredibly rare.
The article was all about the consequences of the skill set being incredibly rare.
Imagine if a director was a bureaucrat. One who followed checklists and made policy documents, and did not have the slightest clue about the actual craft of setting lights, working the camera, and acting.
What's our profession's equivalent of a film director? One with deep knowledge about data structures, who cared about getting it right, together with professionals?
Scrum master.
Good product managers identify the problems to be solved, and prioritize which ones should be solved first.
I'd argue that the position taken above weakens the engineering practice. Understanding requirements (e.g. constraints) is a core element of engineering, engineering management, and general management. Part of the problem plaguing the tech industry is the "dumping" of this responsibility, and others such as "project management" into some other role. What some like to call a "specialization" may also be called an abdication of responsibilities and ultimately accountability.
In my opinion, the essence of engineering is the methodical art and practice of solving problems. A fundamental part of engineering is understanding the problem(s) to be solved, the constraints, as well as the trade space and trade offs of solutions for those problems.
Not all aspects of (engineering) problems are "technical" in nature, and a failure to understand this and cultivate this understanding weakens the engineering practice.