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.
----- Original Message -----
From: "Bruce Byfield" <bbyfield -at- axionet -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: March 15, 2003 09:12 PM
Subject: technical skills vs. writing skills (again)
>
> At the risk of reviving a long-ago exhausted subject, yeterday I had
> first hand experience of a technical writers' need to have a technical
> background - or at least the willingness to obtain one.
>
> I was called in to an interview for a full-time job yesterday. I don't
> know if I'll take it if offered - contracting being in my blood - but
> that's a decision for another day, and depends on what the salary and
> working conditions are like. If nothing else, the occasional application
> helps to keep me informed about the local job market.
>
> At any rate, before the interview, the company sent a brief writing test
> to those who were short-listed. The test was based on the company's
> product line, which is very technical, and likely beyond the knowledge
> of anyone who hasn't worked in the company's particular area of
> high-tech. In giving my response, I noted at the top that I could edit
> the material provided, make design suggestions, and indicate how I would
> go about learning about the subject matter - but that I couldn't do any
> actual technical writing because I didn't know enough.
>
The echoes of Bruce's experience in my own are reassuring to me, despite my
disappointment.
Last Friday I received an editing test from a company that wants to find
several freelance, telecommuting editors. After reviewing the test, I wrote
the following to the company:
***
Xxxxxxxxx,
I am concerned about this test because of its focus on a particular product.
Without in-depth knowledge of the product, any attempt I make to clarify,
reorganize, and reorient seems doomed to missing the mark. I have done enough
research about the product to know that learning about it is not something I
can do in a couple of hours. It also seems to me that the bulk of the editing
involved in this test is in restructuring the presentation. While I have a
good idea of what I would do, I cannot be sure that I will not change the
meaning or wind up with incorrect statements.
Therefore, I am going to think about whether I want to take this test at all
over the weekend and get back to you on Monday.
Best regards,
***
I am disappointed because I will not be taking the test at all, but I am
reassured because I know that as an editor, I cannot edit something that
requires in-depth product knowledge. The test was so product-specific that no
amount of generalized knowledge about VoIP would suffice.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Order RoboHelp X3 and receive a $100 mail-in rebate, plus FREE
RoboScreenCapture, WebHelp Merge Module and iMarkupSoftware, for a total
giveaway value of $473! Order here: http://www.ehelp.com/techwr-l
Help celebrate TECHWR-L's 10th Anniversary starting this month!
Check out the contests at http://www.raycomm.com/techwhirl/special/contests/
Happy birthday to you, happy birthday to you, happy birthday TECHWR-L....
---
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.
