---
title: "Guest Post: Core Skills for Technical Writers Often Overlooked"
date: 2012-08-16
description: "$( document ).ready(function() { // Handler for .ready() called. $("
canonical_url: https://idratherbewriting.com/2012/08/16/core-skillsets-for-technical-writers/
---
# Guest Post: Core Skills for Technical Writers Often Overlooked
The following is a guest post by Vinish Garg, Director of Operations in Technical Documentation at vhite systems.

[![](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/orangebar.png)](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/2009/04/orangebar.png)

When I watched the Master Chef series (Australian version and then Indian version) last year, an important lesson for contestants was to not focus only on *extraordinary or most creative dishes.* The judges never really looked *only* for creativity, fancy ingredients, and garnishing. To the judges, adherence to instructions, balance, presentation, and the *basics* of a dish was equally important.

Most of the tech comm resources, including blogs, white papers, open forums, presentations, and workshops at local or global events, talk about topics such as XML or DITA, single sourcing, indexing, documentation management, or usability. It makes sense since we all know that the technical documentation practices are evolving faster than ever before. So the current and next generation should be well-equipped to handle the challenges.

[![](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/basics.png)](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/2012/07/basics.png)

However, I feel that somewhere along the way, mastery of the basics has been overlooked.

I have been developing technical documentation for eight years now. My general work routine involves (a) being a documentation manager, (b) training new technical writers, (c) writing procedures and instructions, and (d) participating in online community activities.

At this stage, I feel that the industry veterans are passing the baton to me, and at the same time, I am passing the baton to the next generation of technical writers. I have also realised that passing the baton to next generation is a greater and more challenging responsibility since they look to us for input and direction.

## The Current Generation of Technical Writers

[![](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/experience.png)](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/2012/07/experience.png)When I look to hire contractors, the most important factor for me is to evaluate the documentation and professional skills in the resume itself. While responding to open positions for my projects, many candidates apply with two to six years of experience. They claim to have developed world class documents in agile work environments, using global technology and enterprise platforms.

However, I am often *let down*. Here's how:

- Email: The emails that applicants write when applying for an open position are poor.

- Resume: The resumes are even less satisfying.

- Professional etiquettes: There is no follow-up, and no thank-you emails.

- Last and most unfortunate: When they ask me for comments or feedback, a few of them scoff at my polite yet professional comments.

The ability to fix CSS, compile the help file in Flare, set up a wiki, or use cross references in Microsoft Word are all good technical writing skills. But I wonder if this is enough. How can an experienced technical writer apply with a poor resume (most of the resumes are pathetic)?