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.
Tony...the resume IS written for the reader...it is in the
appropriate tone, uses the appropriate terminology, phrases things
the way they want to hear it, has the right "words". To me, that IS
writing for the reader. OTOH, the content is about the product. The
product is not going to change me for the reader. When it comes to
style, we write for the reader. When it comes to content, we write
about the product. It is then up to the reader to determine if the
product is appropriate.
> job hunting, <G> I can't understand how a technical writer, who
> knows he has to write for the user's understanding in a technical
> document, can apply a different standard on something as important
> as a reume. As I see it, the same method should apply: write
> for your reader.
> Now, I'm NOT condoning ANY misinformation on a resume. A fibs a
> fibs whether it's a white lie or not. However, the emphasis
> placed on previous work experience can change from resume to
> resume. If I'm applying at a software company, any experience
> I had in the software field should take center stage.
Sometimes, non-sw related writing has an impact on the software
project in question. If I'm writing sw-related information for a
proposal response, wouldn't sales experience be a plus?
If I'm writing Network outage notifications, wouldn't writing press
releases be of benefit?
> 'The reader of resumes are a lazy lot.' (Direct quote from a former
> HR manager.
I DO their work for them in the way I phrase the information in my
resume. I use the feature/benefit approach. I don't them them the
feature and let them figure it out, that's work...I tell them the
feature, and then the benefit that they pass it back to their client.
> Write for the reader.
Take a look at my link to the resume. I think you might not find it
as bad as you think. I'd be interested in your comments.
Take XML and Tech Writing courses online! Our instructor-led courses
(4-6 hrs/wk) give you "hands on" experience at your convenience. STC members
get 20% off! http://www.online-learning.com/index.html.
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.