Getting a Tech Writing Job

Our developer group is looking for a new tech writer to write specs and they're getting all sorts of fun resumes. They are a source of endless amusement!

One guy sent his resume in .txt format. That's funny! Another sent a resume that was badly formatted (a new indent for every 5 lines, whether it needs it or not!) Other resumes include some blatant misspellings, mis-use of words like "an" and "a" and "then" and "than", and the like.

Now, I'm not sure about other jobs, but when you are applying for a job that has anything to do with communications, you could at least get the resume part right. I'm sorry, but I look at some of these resumes and I think "At least get the resume right, get the job, then sluff off, ok?"

First, if you can't format a document properly, you can't be a tech writer. period. Part of being a good tech writer is document design, and if you can't design a document, don't bother.

Second, if you can't spell, don't bother. Even if you inherently can't spell and rely a whole bunch on spell checker in your word processing program, have someone look at it before you send it off. Also, read it out loud. Word doesn't catch everything. If you can't proof your own writing, how you gonna proof mine?

Third, don't give links to Web sites that may have information on it that may disqualify you. One guy gave a link to a site proclaiming his love for film making and blogging and the fast paced cali world. Not gonna get him a boring job writing specs here... he'll be bored and bored and bored! Quits in a week. Can't have that!

Got some more rules for me? Speak up!