> You must be joking, or else work with very low caliber people.
They're only low caliber people when it comes to writing. Otherwise they're exceptional engineers. The company historically and currently is a market leader. We're not talking about a small shop.
> I don’t consider people for positions who cannot write well
And this is exactly what I'm talking about. If you're in a setting that values it, and set up filters for it, then of course writing is important. If you're in my company where it isn't valued, then not only is it not important, it has little benefit. No point in writing well if people aren't going to read it.
> Really, can you take a poorly written engineering spec or RFP seriously?
In the case of my company, yes - if you want to keep your job. Unless it's inscrutable, I can't go to my manager and refuse to work on something because the spec is poorly written. He'll immediately tell me to go contact the author and sort it out. Occasionally the author will be nice enough to fix the spec and release a new document. But it's hit and miss. The reason many don't fix the formal spec in these cases? Their managers don't value it.
Specs are for major efforts. At the intermediate level: "What the heck is a spec? We just communicate requirements via PPT."
(No, I'm not kidding).
