RE: TW -> QA

Subject: RE: TW -> QA
From: "Lisa Wright" <liwright -at- earthlink -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 5 Feb 2003 22:20:53 -0800

Hi Belinda,
All your other respondents have provided some good suggestions for
evaluating a QA job. I've been down this road a few times, so I'll offer
my perspective, give you a few more questions to ask yourself.

I'm really good at testing software products, finding things out about
them, and ferreting out problems/scenarios that no one else thinks to
look for. My project teams, especially the managers love this.
(Sometimes the software engineers don't love it because I find stuff
they have to fix. Most of the time they think it's cool.) I enjoy this
kind of exploration and it gives me good insight into a product.

But I make a lousy QA person/tester. Why? Because being QA requires
rigid, repeatable structure, planned out in advance, followed through to
completion. My way of working through a software project is very, well,
intuitive and free-form. My mindset, my work style, pretty much my
entire being cannot tolerate working the way QA requires you to work. I
turned down a job because of this. My agency manager likes me to put
"testing" on my resume because it offers an additional avenue into a
project, but I would resist actually taking a job that advertised itself
as "testing" or QA.

So, I guess what I'm saying is, really take a close look at what the job
of testing entails. It's not the same as the work you do now with the
software. It may provide you with some additional job security, true.
But take a look at the longer career direction as well.

Good luck!


-----Original Message-----
From: bounce-techwr-l-53104 -at- lists -dot- raycomm -dot- com
[mailto:bounce-techwr-l-53104 -at- lists -dot- raycomm -dot- com] On Behalf Of Belinda
Sent: Wednesday, February 05, 2003 4:14 PM
Subject: TW -> QA

I work as a tech writer for a medium sized company. Our QA manager is
going to be leaving soon and I've been offered the QA position. I've got
an editing/tech writing background, rather than a QA one, but know the
products well. However, I'm a bit concerned that I'll probably have to
keep up my tech writing duties in addition to the QA stuff. Basically,
I'm after suggestions or advice on this situation.



Buy or upgrade to RoboHelp X3 today and receive the WebHelp
Merge Module for FREE ($299 value). RoboHelp X3's all-new
features include conditional text, completely re-engineered
printed documentation output, Context-sensitive Help Toolkit,
single-source layouts, and more!
Order online today at

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 for more resources and info.

TW -> QA: From: Belinda Kelly

Previous by Author: RE: Have to know Programming to be able to write about it? -- NO
Next by Author: RE: Providing Samples (Was RE: Why they don't ask for candidates by technology skills.)
Previous by Thread: TW -> QA
Next by Thread: RE: TW -> QA

What this post helpful? Share it with friends and colleagues:

Sponsored Ads