A Refreshing Angle on the Name of our Profession
I enjoyed David Farbey's post on the name we should call our profession. Aligning our name with the most profitable business model makes sense. If you look at indeed.com for jobs as a "technical communicator," you won't find hardly any. Look for "technical writer" and you find a ton. So what is the benefit of calling ourselves technical communicators, when no one is hiring technical communicators?
Sponsored
About Tom Johnson
I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, agent skills, tech comm careers, and more. Check out my AI courses for more on the latest in AI and tech comm. If you're looking for info about documenting APIs, see my API documentation course.
If you're a technical writer and want to keep on top of the latest trends in tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me.
Finally, I want to note a couple of things. I usually write the first drafts of my posts myself and then use AI to improve accuracy, clarity, and detail in places, so my writing is a mix of human and AI. (Hopefully that's not too off-putting.) Also, the opinions I express on my blog are my own perspectives, not those of my employer.