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: Explanations for getting fired From:Penny Staples <pstaples -at- AIRWIRE -dot- COM> Date:Wed, 10 Mar 1999 10:41:13 -0600
Dear Annonymous,
It was a position that didn't work out. OK. I think that's something that's
happened to many people at some point in their working lives. I was lucky
enough to be let go from a non tech writing job I had while I was at
university. The important thing is to learn from it.
My experience taught me just how badly things can go wrong when there are
misunderstandings and miscommunications in the workplace, and people start
jumping to wrong conclusions. In retrospect, I'm glad it happened. The
things I learned have been very useful in my current career.
It seems that you learned valuable lessons from your experience, as the
subsequent two positions worked out well for you. In the interview, focus on
the positive things. If the job that didn't work out comes up, I would be
honest but brief, and try to put a positive spin on it.
You are not the same person as you were at that first job. You've moved on.
You work differently now, and you probably have some good references. If I
were you, I wouldn't mention the fact that I was fired on my resume, and in
the interview I wouldn't talk about why I left, unless the interviewer asks.
[Question to the list: is this dishonest?]
