CIO — Some people suck at their chosen profession. Despite all the enthusiasm and training in the world, sometimes quality and productivity just aren't meant to be. Technical writers are subject to this failure just like everyone else. Your job, as an IT manager, is to hire only the good ones.

Unlike project managers, network administrators and Java developers, technical writers have no formal professional certification to demonstrate their expertise. If you need to hire a documentation specialist, all you have to work with is the candidate's résumé and the person seated across your desk. So how do you tell if the applicant in front of you is worth her weight in gold or should be invited to consider a new career path? Here are a few tips to help you weed out the good from the bad—even if you've never hired a tech writer before.

Education and Experience

Until just a few years ago, there was no formal college degree in technical communication. Expect a younger applicant to have some sort of training in technical communication, business writing and composition, or a subject many university English departments call "rhetoric and professional communication." Technical communication programs are becoming more popular in colleges, where they usually offer a more focused curriculum than other majors.

But what about those who started writing long before these degrees were an option? Look for experience—but the right kind. Even if someone has previously had a writing gig, not all writers are well suited for every type of writing job. Journalists and marketing specialists often have a hard time crossing over to technical writing, because it requires a different style of writing. For example, journalists are taught to use the inverted pyramid style of writing, in which the most important and broad topics are covered first, and supporting but less important details follow. Tech writers write in a factual style that usually delivers a polite command, all arranged in a very specific order. When reading a news article, you can leave the story at any point in the article with knowledge. When you read a technical article, you need to read it in a specific order to walk away with predetermined amount of knowledge.

Ask the job applicant questions about specific tasks performed in previous jobs. You're looking for an analytical, succinct and (dare I say it) dry style of writing. Yeah, I know, technical documentation is dull stuff to read. But your writer is conveying information, not entertaining your staff.

You may have other skills that pertain to your specific situation, such as specific software that your future employee needs to use. Don't be dismayed if you don't see that tool on your applicant's résumé. Similar technology skills may illustrate the individual's ability to learn, and that's a much more valuable skill. If your applicant demonstrates knowledge of Word and FrameMaker, it's a safe bet that he can easily adapt to RoboHelp or Flare.

Considering a career change? See our list of The Hottest Jobs In Information Technology.

Continue Reading