Being let go

eatchicken

Just want to get your thoughts on this..

In my last employment, I was on 6 months probation but after that I was let go. The reason put to me was while I was a genuine, friendly person who was good to work, my boss did not feel that I had the confidence in the technology that I was trained in to go on site and to do the job even-though I had no exposure, and he also thought that I lacked enthusiasm on the product.

Now I believe that I knew the product better than he though but I agreed with him and I was happy to leave. However, now as I have gone through 2 interviews, I feel that saying that I got let go is another way of saying that I got fired.

Have anyone on this form have any experience about telling a story of being let go or know the best way to get around the issue.

Thanks

Nody

They where downsizing on a last in first out basis and sadly due to this your position was removed.

Mr. Loverman

Nody wrote: »

They where downsizing on a last in first out basis and sadly due to this your position was removed.

I like this one.

It might be a good idea to contact the ex-boss and ask is it OK if you say you were let go/downsized/whatever rather than pushed out, as you are having difficulty finding new work due to the blip on your CV. Unless he's a total bollox, he will agree.

starlit

I wouldn't see it as let go as being fired, if it was a contract thing put it down to that, you were still considered a temp depending on the contract if temp or permanent and well you had your probation it was up to them to keep you on or not. Just mention they didn't continue the contract and leave it at that, if probed further state the reason or just state they couldn't keep you on that should be enough a reason.

You carried out your contract so imo you weren't fired. You can just state they did not continue your contract stating you were let go. Most reasons are due to no being able to afford to hire you or job cuts, first in first out basis, downsizing or what ever.

You don't have to tell people in applications/CV/interviews unless they ask. Its ok if you want to tell them that your former employer thought you weren't confident with technologies yet stating your good points but the fact is he mentioned good points so focus on the positive rather than the negative.

All he really said was that you weren't confident in using the technologies you were taught on the job I don't think is a valid reason to let someone go though. Its a reason not to hire someone yes or to renew a contract maybe but to let someone go, I think he should have given you more of a chance, the fact you had no exposure previously he should have taken into consideration, you won't know everything after 6 months just enough to hit the surface! You'd need a year to years experience to become confident with any kind of technology you never used before! Some people pick things up easily others don't takes longer.

I know myself I have been interviewed for couple of jobs in relation to technology and one thing that has been mentioned to me pretty similar to what you have stated yourself, the good points and then well employers don't believe I have such and such a skill and not enough research in technologies, my answers in my application was good enough to give me an interview but not good enough to get the job! They weren't convinced enough of my skill with my examples! How can I possible brush up on that - study/research/work experience and work experience is hard to come by at the moment even for IT grads its not so easy unless you are in IT professionally!

When it comes to applications/Interviews, I think stating you were let go is enough of a reason they shouldn't try to probe further unless you asked previous employer for a ref. State you worked there but mention a different ref in case they state you weren't suited to the job. You have gained transferable skills but maybe just brush up on the technologies you did learn - do certs or what ever. Lacked enthusiasm for the product, I can see where they are going with it but a sill made up reason if any if they didn't have a reason to back that up, if they gave you an example they should have or at least pointed that out to you during your contract which is a let down on their part. They should have been mentoring you at least.

What technologies are these would you mind me asking? Its a load of crap for the reason why they let you go, silly reason, they could at least try to train you up more or you go back to study/do certs or what ever to improve your knowledge hands on experience isn't enough if you haven't learnt it and then apply in practice, if anything they didn't teach you well if they think you aren't confident with technologies they used so if anything its their fault that you weren't confident with them as so they say, he should have at least tried to be sure you be confident and ensure you would be by the end of the contract if they wanted to keep you on but my guess they had other reasons they found another candidate or they just couldn't be bothered to keep you on and gave you a made up or silly/not so convincing reason to let you go but they had the choice at the end of the day to keep you on or not for what ever reason.

Look on it as a learning experience you learnt something you gained some work experience, future employers be only too happy to have you, maybe just brush up on the technologies you are unsure of and prove your previous employer wrong! There was probably other reasons, couldn't afford to take you on, job cuts, a case of first in first out, the fact you were on a probationary contract considered a temp depending on the type of contract then they could do what they like.

eatchicken

Thanks all for your advice. I got on to my boss who said that I was on a 6 months development contract and they did not have a need to renew it.

I think that this will suffice as it is hardly pointing the finger at me if I was just not needed.

What technologies are these would you mind me asking?

The technology was internal and there is no way anyone could know it outside of the establishment. It was specialised lab software that had configuration and a private scripting tool that was not too complicated to use but no good as a career. There was a chance that c# could be utilised and I took the job on the back of it, but it never materialised.

starlit

Well in that case if it was just to complete a development project/contract then that's all it was! How would you be expected to know and understand a software if it only used within the confines of that company makes no sense really if they expected you to be an expert after a few months. It takes more than just a few months to become an expert at something.

Some people just pick things up quicker than others. You'd learn it eventually and once you grasp it isn't that enough. It take more than a few months of experience to be good at it.

Best of luck