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.
Well, my suggestion would be to play up your current skill set and
projects you've completed successfully. When they approach the issue of
why you are looking for a new job, put it in terms of knowing what the
market offers people with your skills. You probably also have several
things that starting your own department have taught you, and I don't think
it's saying anything negative if you say something to the effect that
you've had the experience of being both a producer in tech writer and of
managing a team of people, and find the role of producing documentation
more personally rewarding than management (if that's true, at least).
I recently went through a round of interviewing people, and spent a lot of
time reflecting on how the people who: 1) seemed really confident in their
ability to learn what was expected; 2) were able to convince me that they
knew the kind of work they excelled at and that they wanted nothing more
than to do that work to the best of their ability; and 3) seemed like
good, solid team players stood out favorably. The people who said negative
things about their current situation made me question whether I'd be
hiring someone alse's headache. The other kiss of death was an interviewee
who wanted to "learn the ropes and then be left alone in (her) cubicle"
(direct quote).
Hope this helps.
G
On Mon, 27 Jul 1998, Paul Hanson wrote:
> In the recent thread regarding whether to stay with a company that recently
> had layoffs or to look, one post suggested emphasizing the positive reasons
> why you are looking for a new technical writer position. That is an
> interesting suggestion, considering my current situation. I took my current
> tech writer position in February of 1998 and now, less than 6 months later,
> I am looking for a more financially stable future, if one exists in 1998
> America, considering my wife works part-time (80%) and our 2nd child is due
> in less than 100 days. That said, how would list members suggest I market
> myself. I worked at my previous company three years and only left because of
> the opportunity to start my own department. Well, things have changed.
> Suggestions?
>
> Paul Hanson
> Technical Writer
>
>
>
>
