Reddit reviews Developing Quality Technical Information: A Handbook for Writers and Editors (3rd Edition) (IBM Press)

This is a copy and paste from a few months ago. There isn't really a "bible," so to speak, because the field is so varied. But this list should get you started. There are also some technical writing textbooks on Amazon that might be useful.

• The Chicago Manual of Style, 17th Edition - the classic reference. This covers pretty much everything you ever wanted to know about grammar and usage, including things you didn't know that you didn't know.
  
  
• The Chicago Guide to Grammar, Usage, and Punctuation - this is an expanded version of chapter 5 of the CMoS mentioned above.
  
  
• The Microsoft Manual of Style, 4th Edition - if you write for Windows-based software, this is the book you need.
  
  If you're looking for more mechanical things like document structure and organization, I'd recommend the following:
  
  
• Information Development - look for this one used, it's been out of print for awhile. Good information on managing documentation projects. I'm a bit of a broken record on this subject, but a LOT of a technical writer's job is managing projects.
  
  
• Handbook of Technical Writing (this is apparently a textbook now...?) - just what it says on the tin. Good overview of various topics related to tech writing.
  
  
• Developing Quality Technical Information - another overview of various topics related to tech writing. This isn't a "read cover to cover" kind of book, but more of a "open to a random location and just start reading" kind of book.
  
  
• The Non-Designer's Design Book - one thing that tech writers have to think about, or at least should be thinking about, is document design. This is the best book I've found on that subject, bar none. The principles taught in this book guide the layout and design of pretty much every document I've created in the past 9 years.
  
  
• The Insider's Guide to Technical Writing - a good overview of some basic technical writing topics.
  
  
• Every Page is Page One - I've been trying to move more towards the concepts covered in this book as I redo and update the current mess I inherited from the previous tech writer.
  
  

Professional writer and hiring manager here. A strong portfolio and a relevant degree like English will help interview at entry level assuming the posting doesn't require strong advanced toolset experience like Framemaker, Robohelp, or DITA. Your folio should have technical communication type stuff like SOPs, policies , and help documentation. Google some templates or use the books I list below. Make them up for existing programs you know if you don't have real world examples. Managers will want to see that you you know the language and will ask for samples at some point during interview if not up front (If they don't ask for samples they probably don't know what they are doing ).

Recommend you at least familiarize yourself with staple toolsets like the Adobe technical communication suite (there may be a free trial or it is like $50 a month or so for subscription) until you are comfortable with it then cancel. Also diagram software like Visio. Screen capture software like Snagit. That will cover the typical core tools in the field. A lot of places will still use MS Word but more advanced places will use technical communication software.

Invest in some theory books to learn and reference. An English degree is great but there are theory and best practices behind technical writing that will help you in the long run and being familiar will help set you apart from all the other English majors that don't know what to do with their degree (it is quite common ).


Get these must have books to read and reference in your career :

(How to write as a tech writer )
https://www.amazon.com/gp/aw/d/0133118975/ref=dp_ob_neva_mobile

(How to design documents)
https://www.amazon.com/White-Space-Your-Enemy-Communicating/dp/1138804649

(Reference document for just about everything )
https://www.amazon.com/Handbook-Technical-Writing-Tenth-Gerald/dp/1250004411

Arguably most popular style manual
https://m.barnesandnoble.com/p/microsoft-manual-of-style-microsoft-corporation/1104743122/2678008132375?st=PLA&sid=BNB_DRS_Core+Catch-All,+Low_00000000&2sid=Google_&sourceId=PLGoP79700&gclid=EAIaIQobChMIycubtNvO1wIVTiOBCh232wKvEAQYASABEgKsUPD_BwE

Look for junior level jobs or contract to hire. A lot of companies will hire temp writers or contract to hire to see If they will work out. Worst case you get title experience on your resume and most recruiters know there is a lot of contract work in the field and it won't look odd.

Try to be open and communicative in your interviews. A lot of the gig is building relationships and getting information out of people you don't know well. Personable people that can communicate quickly, effectively, and confidentlly are desirable.

Good luck !

Edit: Ensure your resume is flawless. It is the first and most important document you will ever make as a technical writer and should be considered the first page of your portfolio.

Look up if there is an active STC chapter in your area. If they have meetings consider going as that is a good place to start networking. I can't recommend joining it if there isn't an active chapter as the ROI is meh ( I may get downvotes for this ).

Get setup with local temp agencies and let them look for jobs for you. Like I said before s lot of companies will go through them to fill temp or contract to hire positions.

Edit edit :

Last thing. It isn't a bad idea to get familiar with some coding languages to strengthen your resume and open doors when applying. W3schools has good , free online lessons to get your feet wet. You can get a certification after a test for $90. It is inexpensive and a good way to prove you are familiar. Html , xml , and css are good starters and you may want to expand from there depending on Your interest and Your local market.

Auto spam filter caught this post because of the shortcut link.
If you're suspicious of the shortened URL, the link refers to : https://www.amazon.com/Developing-Quality-Technical-Information-Handbook/dp/0133118975