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.
How many titles do we have out there today? [ducking] ;-)
I label myself as a technical writer. I write, I design, I code, I create
markup, I edit, I test, I train, I ramble, I piss people off, I get paid.
Don't spend too much time dressing up your tasks. I can't speak for others
(not that I'm a hiring manager) but when I review resumes I overlook the
titles and task titles and dig right into what these people did over the
years. If a resume is infected with buzzwords, I tend to think that perhaps
this person is experimenting in creative writing in order to get the job.
Let your experience, portfolio and references speak for you. When they get
the initial job done and you get that face-to-face interview, strut your
stuff but be genuine. I don't think I'm the only person out there who has
enjoyed setting traps in an interview.