Mozilla is actually the best-paying job I've ever had, if that tells you anything. And it was an okay salary. I've never been more financially secure. But I'd like some of that "easy SV money" :)
If you asked your engineer peers how they would feel if you were paid an equivalent salary, I am confident some of them would admit that they would not like it. Privately, I think most of them would definitely not like it but would probably refrain from publicly admitting as much.
Which to me is the crux of the matter. If I was your manager at Mozilla and looking to maintain team cohesion and minimize talent loss, engineers would always come first. In my experience it is very common for managers with an engineering background to think that anyone can be a technical writer. Same for evangelizers. People do it for free if they like the technology that they are using. These are not strong bargaining foundations.
I think your first paragraph is on the money, this is indeed how many engineers and engineering managers think. You seem to throw in your cards with that viewpoint in your second paragraph, though, and I think the logic there is circular. Engineers and engineering managers persistently devalue the skillset behind being an excellent technical writer, and the value that an excellent technical writer brings to a project, which in turn weakens the “bargaining foundations” of technical writers artificially. It’s been my experience as an engineer that this artificial devaluation is harmful to projects both directly and indirectly, because technical writers are inevitably aware of the fact that it’s happening. That technical writing maybe has a greater foundation in so-called “soft skills” doesn’t mean that it’s less valuable, and especially in cases like Rust where the documentation can very reasonably be considered part of the product, it’s a huge mistake to undervalue the work of someone like Steve Klabnick that way. In general, I can’t imagine being resentful of a technical writer earning as much or more than me as an engineer: a perfect gem of software engineering that no one uses is a failed product, and it’s very much because of the work of technical writers that good projects see widespread use.
