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:FW: using a slogan on a resume From:"Sella Rush" <srush -at- MusicNet -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 16 Jan 2003 18:24:20 -0800
Hey Bruce:
I've only heard this advice in context to online resume banks like Monster, and the advice is to include the most important points you want to get across, such as "Technical Writer, 6+ yrs exp, SDKs, Java & C++". Employers looking for resumes on those sites will search for "technical writer" and get back a long list of matches with title only. Those with detail make scanning easier. I can say during a recent job hunt I started with a basic title and was getting no matches. But after I added detail I started getting interest. And that was at Xmas time when I wouldn't expect interest to pick up.
I don't see why the technique wouldn't work on a print resume too, if you could make it look good. You're a risk-taking kind of guy--try it out and get back to us!
My resume is a little unorthodox, but I've only ever received good comments on it. My name and title are at the top, followed by a section called skills or something, with a one-sentence summary of my career (# of years, what industry) followed by bullets with my best points or summaries of skills. Then I move into the traditional resume stuff like employers and education, etc. The career summary is more than 12 words, but it's rarely more than 2 lines. But the real info is in the bullet points. I usually have 5 or 6 bullets, and they're brief--little detail (like "C++ programming experience").
People like that summary at the top--it gives them the info quick and clean. The fact that it's summaries, however, means that I have to ground it in a job description or project summary later. But it gives them a quick overview, and interviewers often use the list as a guideline for questions.
(Note: I often change the bullets (along with the project list) to suit the job I'm applying for.)
___________________
Sella Rush
Tech Writer III
MusicNet, Inc.
(206) 269-6115 Direct
srush -at- musicnet -dot- com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.