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: How do hiring companies view TW resumes? From:Tony Chung <tonyc -at- tonychung -dot- ca> To:TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 16 Mar 2010 09:35:46 -0700
[Re: want ad hirings â pure chance]
Richard Nelson Bolles has been saying this for years in his "What
Color is Your Parachute" book series. I've heard it said the resume
isn'# a hiring document, it's an exclusion document.
You don't need specifics on your resume, only specific stories leading
to potential benefits:
- Increased product sales by 30% through the release of preliminary
product documentation
- Reduced support calls by 50% by initiating and moderating a user support forum
- Simplified the creation of developer documentation by writing a
series of boilerplate templates that broke through writers block,
leading to a working prototype more quickly.
These don't speak to specific projects, but we can all attest that we
contribute in a similar fashion.
Then you list your specialty subject areas, and a table of your
toolbaox. State whether the tool is widely used in the field
(Peoplesoft, Oracle, FrameMaker, Word), and either generally
categorize, or provide a brief description of the problm solved by
in-house, proprietary, or indstry specific tools.
At the end of it, state References supplied upon request. You want to
contact references who will most effectively communicate your vale to
the one who interviewed you, based on personality and communication
style.
And while recruiters are great people to speak with, their role is to
get you hired so they get paid. Work your network yourself, and leave
your resume behind you, not before you've had some contact with the
"one eith the power to hire you".
I heartily recommend the 2010 edition of Parachute. I've read a
selection since 1988, and get the sense that Bolles completely
restuctured the content for this edition.
He may even have used DITA.
Cheers,
-Tony
--
Tony Chung: Creative Communications
Cell: +1-604-710-5164
Email: tonyc -at- tonychung -dot- ca * Web: http://tonychung.ca
Skype: tonychung.ca * GTalk/MSN: tonychung -dot- ca -at- gmail -dot- com
Twitter: @techcom * Facebook: http://www.facebook.com/tonychung.ca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-