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: Mistaken job requirements, take II From:Ben Kovitz <apteryx -at- CHISP -dot- NET> Date:Fri, 29 Jan 1999 10:36:55 -0700
Geoff Hart replied to Elizabeth Vollbach:
>I think you've raised an important point, because raw talent usually
>doesn't become true competence until you've obtained some experience
>in the trenches that teaches you how to apply that talent. So as an
>indirect clue, listing experience with (say) Frame is a good way for
>an employer to be reassured that you've been around long enough to
>get to the competent stage. Admittedly, it's not always the best way
>to judge someone's talent, but it is a good clue... though hopefully
>one of many that you use in making your decision.
Interesting point. I recently pulled the tool list off my résumé in order
to make room for other stuff. Maybe I should add it back.
But the main way that I impress people at an interview is just by bringing
samples of my work. And that's mainly how I evaluate people when I'm the
one doing the interviewing. A well-written manual that you wrote and can
talk intelligently about--wow, that blows a lot of people away.
Of course, the résumé is what *gets* you the interview. (Well, knowing
people and talking to people is what gets you an interview if you know how
to look for a job. But I digress. See that "Parachute" book.)
