Testing is an area of software engineering that does not historically draw the widespread respect accorded to "normal" software engineers. QA and test automation have historically been seen as less-skilled, more junior roles, perhaps even drudge work that could be replaced with adequately sophisticated tools.
Industry standard: A QA Manager generally gets paid the same as a Senior Software Engineer
It says something that it’s considered a perk to be hired into a position where, as a software engineer, one can work on testing tools but not be publicly identified as “in test.” Believe me, in my travels as a consultant this is a theme I have heard a lot with regard to why engineers do/don’t choose to work with various organizations.
It is demonstrably impossible to build and run a reliable system without engineers who excel at “maintenance,” also known as “keeping the site up.” Testing (aka debugging) makes up the better part of maintenance.
However for historical reasons the software industry suffers from a persistent condition in which QA doesn’t get the respect it deserves for the most part, in most organizations. As a corollary, organizations that do value and reward testing professionals, wind up recruiting all the (already rare) competent people in the field.
And this is the state of the (Web and mobile) software industry right now: everyone who is good at being an engineer “in test” already works for a company that is willing to pay above the industry mean for testing expertise.
Escaping the stigma associated with being a tester
Once hired, these “engineers who test” have no incentive to publish publicly nor to be publicly seen as a voice in the testing community — remember the industry standard is to pay testers less than other kinds of engineers.
The result is a stagnating industry where almost no one with deep technical testing knowledge is motivated to share it.