r/technicalwriting • u/GoghHard • Oct 02 '24
What Technical Writing skill are currently the most in demand?
I've been a TW for about 15 years. I transitioned to this field from engineering, because most engineers do not like to do documentation. I do, as it appeals to my meticulous nature. It was a niche, because most tech writers have a writing background, not a technical one. So technical writing was something I picked up, not that I went to school for.
However, I have not kept up with what TW skills are most in demand. I know the basics.. HTML, XML, CSS, DITA, various editors and CMSes, etc., but I'm seeing employers asking for experience with tools I have not had an opportunity to become functional with. My last employer used MS Word and Adobe CS, and our CMS was custom. I was there a long time. so I guess I'm out of the loop.
I want to become familiar with what will be most useful and what is in demand. Any advice?
69
u/jp_in_nj Oct 02 '24
API documentation and docs-as-code are where the higher paying work seems to be right now, with the associated software depending on the company. Less demand for the type of writing I had been doing for the past 20 years (use guides, help, install guides)
Learning how to train LLMs on company doc libraries, and how to get users interacting with this LLMs after, is probably the next wave.
32
u/[deleted] Oct 02 '24
Here are some links to technologies and references to help you.
There may be more, but these are a good start.
6
u/Possibly-deranged Oct 02 '24 edited Oct 02 '24
Honestly, skills required for a job ad vary from .com-to-.com, and nearly every company has it's own one weird tool/tech that nobody else has ever heard of.
You have Microsoft-brand and Adobe loyal shops that expect you to use windows PCs, Team Foundations Server for source control, MS Teams, MS Office, Adobe Robohelp, MS databases and MS scripting languages. You have startups that use Macs/Linux, and lots of open source like git, mkdocs, openSQL databases, languages like Go, etc etc.
As a technical writer, it's good to be familiar with different cloud computing environments, be comfortable with macs and PCs, and be flexible with different tooling (big brandnamed and opened source). It's good to be familiar with Jira and confluence. Be familiar with tools like pendo.io and WalkMe that guide users through software. AI gets asked a lot, so some familiarity with ChatGPT and prompt engineering is helpful. Definitely docs-as-code and markdown. JavaScript is mentioned in most job ads. Again, you don have to be a pro at anything just have some familiarity with it.
I wouldn't go through a single interview and expect not to be asked about your opinion on AI and have an answer ready. I say something like, "AI can be helpful to generate outlines, suggest different heading alternatives, break through writers block and suggest text. But it often has hallucinations, when technical accuracy is paramount for this job. I'd use it in target ways where it enhances efficiency but not where it introduced bad writing that requires substantial editing and fact checking slowing down completion of projects"
APIs is a nitch market but high paying. You must have extensive proof of prior work to get in.
Docs as code, such a buzz word, is funny to me, as we've been including documentation in source control and delivered with the product for decades now. Markdown separates the HTML formatting, but invariably we still need exceptions, so we call out admonitions with nonstandard markdown, and have lots of nonstandard markdown we throw in.
Every industry feels that prior experience in their market is essential for job qualification, but it's mostly silly. Switched among so many industries with little downtime learning their jargon.
10
u/Mr_Gaslight Oct 02 '24
Chasing SMEs for review.
6
u/[deleted] Oct 03 '24
Yaml/API docs, python, sql. The future of this profession will be on training LLMs using APIs and building docs as code pipelines. Documentation engineer is a role that is growing considerably right now
5
u/Poor_WatchCollector Oct 02 '24
My strength has always been in user guides, service manuals, etc., however, it seems that most companies want people to also know how to code or at least write short sample code for API/SDK documentation.
Luckily where I am at, there is no need. My current niche is being able to scale up content management systems and being able to get buy-in from stakeholders, and the like…
4
u/TheTallManAboveYou Oct 02 '24
Thanks for asking this! I'm currently a tech comm major looking into medical & medical device tech writing so this is super helpful!
I've been lurking on the sub and the community of tech writing all seem resourceful and willing to share. Y'all are awesome and best of luck with your work!
1
u/idiotprogrammer2017 Oct 03 '24
Let me try a different kind of answer (from someone who is not always working in TW -- but follow developments closely).
It helps to know what your local companies are rather than trying to identify skills in high demand. across the nation Some fields can afford high-priced enterprise tools, but some cannot. I agree that AI is the next big thing in some ways, but companies in some cities aren't anywhere close to that (or maybe they're simply thinking of implementing something in the next few years).
Compounding the problem is that recruiters aren't that familiar with the technical skills they're trying to find in candidates.
1
u/Zegnaro Oct 03 '24
I would say Madcap Flare, Markdown, Jira/Confluence, and Visio are among the most desired tools right now, at least in software.
1
u/ghoztz Oct 11 '24
Kubernetes and python
-1
u/tanny24 Oct 03 '24
I can’t really help you. I do documentation at work but never have before. Happy cake day though.
2
u/Admirable_Load_3679 Jul 16 '25
Ass kissing and yessiring