This is a great resource, thanks for collecting them. A couple points on prospective new writers: while you don't need to be a great (or even good) software de

This is a great resource, thanks for collecting them. A couple points on prospective new writers: while you don't need to be a great (or even good) software designer or programmer or coder to become a technical writer, it truly helps to get comfortable reading and interpreting code. Every minute of an engineer's time that you can save by understanding a feature from its implementation and asking better-informed questions makes you more valuable. Also, while it's true that there are a lot of tech writing roles in marketing, don't limit to that if you're getting into the field from a different one. Tech writers show up in many contexts, from engineering-focused dev docs to UI/UX design docs to product docs to whitepapers to support knowledge bases. Experience with any of those can lead to more focused technical writing roles later. I've worked the same product documenting role organized under marketing, product, engineering, and support teams, and they all prioritize and value work differently — you might find yourself more compatible with one than the other even if the job req itself is effectively identical.