The reality is that usually someone other than a tech writer is the hiring manager. So I thought I'd share my thoughts on how to hire great writers, especially those who write developer documentation.
Screening Resumes When you screen resumes, look for someone who has experience explaining highly technical information. If you're hiring a junior writer with little to no documentation experience, look for related roles. For example, maybe they provided tech support for their school computer lab. Or if they're switching careers, maybe they provided customer support for developers, or worked in an environment testing APIs. Pro-bono experience writing similar documentation for an open source project is great; it shows proficiency with similar projects, and also shows initiative.
I tend to approach ex-engineers with caution. Some of them make fantastic tech writers, but it's important to dig deeper into their motivation for a career change. Look for those who have discovered that they enjoy writing specs and communicating with customers more than they enjoy debugging code, so they've decided to make a career out of writing. Shy away from people who would prefer an engineering job but, for some reason, can't get hired as an engineer. At best, they will transfer to a new job at their first opportunity. At worst, they will hate their job and damage team morale.
In the education section of the resume, look for evidence of continuing education in related topics; for example: technical writing, programming, or project management classes. A successful technical writer needs to be constantly learning, since the work we're doing is always on the cutting edge of technology, and also because our jobs are so varied and require many skills from many different curricula.
As long as the candidate has a bachelor's degree, don't worry too much about what field it's in. There are very few technical writing degree programs in the US, and there are as many paths into tech writing as there are tech writers. I've met successful tech writers who have degrees in journalism, business, computer science, teaching, and philosophy, among others.
Evaluating Work Samples Any tech writer worth his salt will have a portfolio of sample work. Even someone just getting into the industry should have something to show you: a spec he wrote, an exercise from a class he took, or documentation he wrote for an open source project.
When you request samples, be sure to ask questions to ascertain how much of it the candidate wrote himself. Did he write it from scratch, revise an existing document, or co-write it? Did he have support from an editor to help with the writing, or a support from a publisher to help with publishing logistics? You're really looking for work that the candidate did himself, so ask him for samples he wrote himself. If he doesn't have any of those available, first ask yourself why not, and then at least get a clear picture of how much involvement the candidate had in writing the samples he does have.
When you review samples, evaluate whether the candidate is explaining things clearly. If you don't have any relevant domain knowledge, it's possible that you won't understand everything; however, at least part of it should resonate. Also, look for typos, misspellings, grammatical errors, and other things that indicate potential laziness. Tech writers' work isn't always perfect, but writing samples should be as close to perfect as possible.
Conducting the Interview During the interview, try to ascertain that the candidate:
- knows what goes into good technical documentation
- has the technical aptitude to pick up the particulars of your project
- shows the initiative needed to create great documentation without minimal impact on the productivity of others in your company
Q: What kind of information should be included in an API reference?
A: In addition to the basics (explanation of what the method does, arguments, and return values) a good writer should mention one or more of the following: acceptable ranges of values for arguments, default values, what happens if the method gets called using the default values, possible side effects of calling the method, a list of related methods that are often called with the one in question. Developers read the documentation to find out information they can't get by simply looking at the header file, and they'll be frustrated if that information isn't included.
Q: What kinds of documents need to be written to document an API?
A: At minimum, you'll need a reference, a basic developer's guide that explains how you put the methods together, and a basic sample application. If possible, the reference should be automatically generated using javadoc, doxygen, or similar technology. If possible, the sample application should be compilable, so someone can just use it as the starting point for their own application. If time allows, developer documentation should also include as many of the following additional components as possible: A tutorial that walks through a complex sample app, one concept at a time, release notes that explain what changed between releases, so developers know what they have to do to update their application to the latest version, and in-depth documentation that explains any of the concepts that the API relies on; especially if the developer isn't likely to be familiar with those concepts.
Q: Explain the technology involved with one of the samples you sent.
A: Even you aren't the target audience for the sample, the candidate should be able to explain it in a way that you understand it. A key skill for a tech writer is being able to explain things clearly. If you don't understand it after the candidate's explanation, it's not you--it's the candidate. Move on.
Q: Now assume you're talking to your grandmother. Explain the technology to her.
A: A good tech writer can explain even the most complex of concepts simply to a non-technical audience. I once had a candidate explain the concept of inheritance by saying that his DVD player, stereo and TiVo have an inheritance relationship, because they are all different manifestations of the same kind of technology.
Q: Explain the process you went through to write one of the samples you sent.
A: You're looking for evidence of self-sufficiency. The candidate should do all the research and reading she can (within reason) to avoid wasting engineers' time with basic questions. The candidate should not rely on a spec, or any other document where someone else is writing the majority of the documentation. With enough research, and asking the right types of questions, a good tech writer should be self-sufficient enough to write documentation herself. Chances are you're looking for someone who functions as a one-woman show, so in an ideal situation, the candidate publishes documentation herself, rather than passing source docs off to a publishing team or webmaster. If the writer used an editor, find out what kind of edits were recommended. If a developmental (structural) edit was required, then that demonstrates a fundamental inability to organize information logically, and you should walk away. Look for the ability to take and incorporate feedback. Ask how the candidate requests information and feedback from engineers, and look for evidence of the writer taking responsibility for the content, rather than pushing that responsibility off to the reviewers.
Q: Explain what's happening in a simple snippet of code (that you provide) This code should be written in one of the languages with which the candidate professes familiarity. It should contain a couple of basic constructs, like a loop, and an if, then directive. It should have an explicit return value and variables, and may also modify inherited variables. This is one of the few times where it's better to have less comments, so that you can ensure the candidate is really reading the code.
A: The candidate should be able to basically explain what the code is doing. She should ask good questions about things that aren't obvious. Give the candidate time to think before answering.
What Not to Ask: Don't ask a tech writer candidate questions about how to optimize code efficiency, questions about design patterns, questions about how to resolve bugs in code, or even puzzle/logic questions. Almost universally, none of the skills touched on by those questions are relevant to a tech writing job. There are very few tech writers who could answer these sorts of questions.
Checking references Finally, it's important to check references. You'll probably get more information if you talk to someone who has left the company; today's HR laws dictate that any reference request made to a current employee will probably get passed directly to HR, who will be able to tell you little more than the dates that the candidate worked there.
Ask open-ended questions, such as:
- What are candidate's strengths?
- What are candidate's weak spots?
- What's it like to work with candidate on a project?
- If the reference worked with the candidate on a project he discussed during the interview, ask the reference for his perspective on how that project went.
- Would you hire candidate again?
Oh, and if you're a tech writer looking for job-hunting advice, stay tuned for follow-up posts on how to get hired as a tech writer, and how to break into tech writing.