TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: Should we hire this guy? From:"Giordano, Connie" <Connie -dot- Giordano -at- FMR -dot- COM> To:"'Dave Neufeld'" <Dave_Neufeld -at- spectrumsignal -dot- com>, TECHWR-L <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 5 Jun 2000 14:43:42 -0400
Points to ponder:
-Does he want to write?
-Does he get it? Does the light come on when you explain a new concept?
-Taking a TW course and opening a style guide WILL NOT make a good
page/layout designer. Taking some layout and design courses MAY make him a
good designer, but should help him at least recognize good and bad design.
-Improvements in awkward sentence construction, run-on sentences, poor
punctuation and syntax will not come as a result of a course or style guide,
they come as a result of good, constructive editing and lots 'o practice.
-"Magic spelling" taught in many public school systems, and spell-checkers
are contributing to the dumbing down of American college graduates--it's not
necessarily all his fault.
-You've got a number of red flags here. What does your gut tell you? Can
he learn quickly, take criticism, look for added responsibility? If he can,
your other red flags are correctable. If he can't, stay away.
MTC
Connie Giordano
-----Original Message-----
From: Dave Neufeld [mailto:Dave_Neufeld -at- spectrumsignal -dot- com]
Sent: Monday, June 05, 2000 2:32 PM
To: TECHWR-L
Subject: Should we hire this guy?
Hi all,
Our company is hardcore high tech and we're interviewing potential
candidates. My audience are hardware and software developers who make nifty
telecom and signal intelligence stuff with our DSP hardware and support
software. In other words this stuff does not make to the shelf of Office
Depot.
I've come to the conclusion, that this type of writing demands a technical
background. All our current writers have at least 2 years of technical
education in engineering or computer systems. I've got 4 years of hardware
and software education behind me, plus work experience, and this stuff makes
my brain hurt and my eyes glaze.
Therefore I've posted job openings at regional colleges and technical
institutes with technical programs that should provide the technical
background.
Here's the problem. Even the fresh, young graduates with English as their
first language are not good writers.
My question is: Could/should I hire this potential writer based on this
evaluation of his writing for a course project. Bear in mind that technical
writing is a "new" career option to him...
Some GOOD things that were promising:
-Sentences are typically short, direct and often in the active voice
-Instructions begin with the main verb and convey one thought
-He is not verbose
Some UNUSUALLY BAD things that scare me:
-Several common words are repeatedly misspelled, such as "choos",
"paramaters", "consol", and "immitate"
-A few sentences don't make any sense at all
Some NORMALLY BAD things that most non-occupational and some professional
writers do. These can be corrected with a TW course and by following the
style guides:
-Lack of quality in the imported graphics
-Frequent use of the future tense; active, present tense is the de facto
mode of writing user documentation
-Misused punctuation
-Poor page layout and design
-Many awkward sentences
-Occasional run-on type sentences
-Needs to refine level of detail. Should be increased a bit
