One of the most common questions we’re asked is how to become a Technical Author. We have an ebook on becoming a Technical Author that addresses this in detail, but let’s provide some general advice by looking at what you should consider when writing your CV.
The demand for API documentation writers continues to increase, and we have a new vacancy for a contract API documentation writer on our books. In this case, you need to have a background in/a good understanding of the C programming language.
We may have another requirement for a similar person, again working from home, coming up very soon. If you’d like to be informed of this and other similar vacancies, simply register with Cherryleaf’s Recruitment team.
One of the most successful software companies in Cambridge is looking to recruit a Technical Author to join its team. The company has grown rapidly over recent years, based on a philosophy of hiring great people, providing an enjoyable working culture and environment, and building great products.
For more information, see #4137 Technical Author, Cambridge, £28K-£40K DOE
Editor’s Note: This post has been written by Dr. Tony Self of HyperWrite. Tony will delivering DITA training during October at Cherryleaf’s training centre in London.
In the field of technical communication, an argument crops up from time to time saying that technical communicators shouldn’t have to know anything about XML, because writing is writing, and XML is coding, and never the twain should meet. Dissecting the argument, it appears that the underlying claim is “language first; technology and tools later”.
In many cases, it seems the logic gets a little lost. I have heard statements along the line of “if you can’t string a sentence together, knowing about XML elements and attributes won’t make you a technical writer”, as if those skills are mutually exclusive.
My first observation is that the debate is often poorly framed. XML is not precise enough a term; what does “knowing about XML” mean? XML is an enormous field, covering programming, writing, archeology, journalism, eLearning, spacecraft design, mathematics, chemistry, audio recording, banking, gambling, engine management, and pretty much every field of human endeavour. So in a discussion about the role of XML in technical communication, we need to define what we mean by XML. Bearing in mind that XML is principally a standard for creating XML languages, the XML languages (or applications, in XML terminology) of interest to technical communicators are probably DITA, DocBook, XHTML, SVG, MathML, and XLIFF.
It’s quite difficult to know how many Technical Authors there are in the United Kingdom. The profession doesn’t have its own Standard Occupational Classification code, so there are no official statistics.
We can estimate the number of Technical Authors in the IT sector. One way to do this is by looking at the total number people working in the IT and the percentage of permanent IT job vacancies that are advertising for a Technical Author.
One of the most common questions we get asked is for advice on becoming a freelance Technical Author. To help address that question in depth, we written an ebook, which you can purchase via the Cherryleaf website.
This guide answers the key questions people have when considering a freelance career as a Technical Author. It is focused on starting out as a freelance Technical Author in the United Kingdom, and in the IT and medical equipment sectors. However, many of the sections will also be applicable to other countries and other industry sectors.
Editor’s Note: Introducing a new guest blogger to Cherryleaf’s blog: Dr. Tony Self of HyperWrite.
Where are all the technical writers?
I have often wondered why there are so few technical writers in the world.
In my country, Australia, the Bureau of Statistics (ABS) estimates there are over 2,000 technical writers within the total workforce of 11.65 million people. The Australian Government groups technical writers into a category called “Journalists and Other Writers”. That category of writer has shown little growth over the last decade, and in 2011 represented just 21,400 people.
In the US, the Bureau of Labor Statistics estimated that there were about 50,000 American technical writers in 2010.
We are living in the information age, yet the numbers of technical writers in countries like Australia and the US are not skyrocketing. Why not? Continue reading
Here are the slides on “Technical writing career paths in the UK”:
Thanks to everyone who contributed.