It’s common for enterprises to leave the technical writer’s role out of the DevOps discussion. Even the marketing department joins the discussion in some DevOps-first organizations—so why not the writers?
I’ve written about hiring technical writers two or three times in the past with some impressive results. In fact, my initial article garnered me some not very nice emails from technical writers. It’s a timeless topic, so I wanted to go back and see if any of my initial advice and thoughts have changed in light of today’s economy.
There are still a lot of contrasting viewpoints on the role and skills of the technical writer that can even be confusing to technical writers themselves. This unnecessary confusion also leads to the fallout that affects the salary and career mobility of technical writers. But as a hiring manager, it gives you more room to craft a technical writer position that can be of full benefit to your organization.
Here are my tips for hiring a technical writer:
Throw out preconceived notions about the role
Writing your own job description for the role may seem like, but it means digging down and looking at where your technical documentation needs to go, the challenges getting there, and then when you get there how to maintain the documentation and ready it for the next step. If you’ve had bad experiences
Ask for what you want in a technical writer
It’s one thing to write the technical writer job description that fits your organization’s needs and doesn’t create more drag coefficient on your development team and the project as a whole. Yet, even in today’s down economy be prepared to pay the freight to get a high-end technical writer. This might mean securing more budget and also cutting out third-party recruiters with their 40–65% markup on contractor’s hourly wages.
Align the technical writer to your business
Academia and graduate degrees have really polluted the waters of technical writing and other professions like instructional design. Theory is no substitute for real experience delivering technical content.
Also, graduate degrees are no substitute for real-life experience. Look for technical writers that have worked in your industry or a similar one.
Contractor? Contract to Hire? FTE?
My recent look at my local market shows that the majority of technical writer positions are now 3– 6-month contracts. Full-time employment positions are in the minority.
If you have budgets and project timelines to contend with then starting out with a contract technical writer might be the way to go for your organization.
Look for an experienced technical writer who looks like they have a history of coming into new projects, learning the product, and documenting it in your industry or a similar one.
Contract to hire is the way to go depending on your budget and is an opportunity to have a shakedown cruise with a technical writer especially if you’ve been burned by technical writers in the past and/or rethinking the future of technical writers in your organization.
Look for evidence of technical curiosity
A good technical writer needs to be curious about technology. It’s not they need to be a programmer or engineer, but it’s the technical curiosity that drives them staying up to date with technology. There is an industry myth about “ignorance is an asset” that some lazy technical writers still try to push on people especially hiring managers new to bringing on technical writers.
It’s not about “ignorance,” it’s curiosity that drives a technical writer to learn new technologies and figure stuff out. Technological ignorance in a technical writer will only cost you an annoyed development team and lengthier document review and editing cycles on the project backend.
Rolling your own technical writer job description and ignoring the confused nature of the technical writer role today is the best way to get your documentation written without an unnecessary drag on your other team members.
How do you hire technical writers?
Hey there! My name is Will Kelly. I’m a technical writer and content development manager living and working in the Washington, DC area. After spending years focusing on technical and SDLC documentation, much of my work now focuses on thought leadership content and marketing collateral. My articles have been published by DevOps Agenda, Mobile Business Insights, TechBeacon, CNET TechRepublic, and others. Follow me on Twitter: @willkelly.