Breaking back into IT - possible?

[QABaron]

I know there are threads for what to do when you come up against becoming obsolete and whether to go for certifications or to simply get a degree. I have a B.S. in CIS that I got in 1998. I was in the tech field until I was laid off in 2001 and couldn't find another position in tech. I do not enjoy what I am presently doing, and found being a tester in tech to be the perfect position for my temperment and skills (love puzzles, challenges, and have great soft skills). I would like to break back into testing but aren't sure exactly how (other than networking or sending resumes everywhere - can't imagine that will bring my desired response). I worked as a manual tester on mainframes systems. Any positive suggestions?

You must be the change you wish to see in the world. - Mahatma Ghandi

I'll be more enthusiastic about encouraging thinking outside the box when there's evidence of any thinking going on inside it. - Terry Pratchett

 

[DPlank]

I've found Testing to be one of the few growth markets in IT at the moment.

I get at least 10-15 calls a week (in the UK) asking if I'm available for work. I'm a member of LinkedIn.com, and the only other place people can get my details from is Jobserve.co.uk, where I publish and keep up to date my CV.

My CV is, however, pretty good. I had it designed by a recruitment consultant friend of mine a few years back he gave me some good advice on it.

Essentially, I have a skills matrix after the Personal Information, and before the Career History. This lets people know what you can do, before limiting their thoughts to what you actually do. I have had calls asking me about working as a Web Developer, Project Manager, C++ Programmer, because I make it clear these are skills I have before the CV points out that I am a Test Manager.

Thankfully, the vast majority of the calls I get are from recruitment consultants who have read the whole CV and offer me test work.

Cheers,
Dave

"Yes, I'll stop finding bugs in the software - as soon as you stop writing bugs into the software." <-- Me

For all your testing needs: Forum1393

 

[QABaron]

Hi Dave,
well I wish I were in the U.K. because the U.S. seems to be quite tight for any IT jobs right now unless you have the exact qualifications that the HR person has listed on the job description.

I've read about just going door-to-door to hand out resumes but can't believe that would get any kind of response at all but I am willing to try about anything at this point. I have always heard that networking works well but after I was laid off all my friends were having a difficult time of it and their places of employ weren't hiring. I do have information of an IT association that meets but can't attend the meeting since during their meeting times I am at work.

Thank you for your response...I will keep trying to re-enter as a software tester, even if I have to take more classes or get certifications.


You must be the change you wish to see in the world. - Mahatma Ghandi

I'll be more enthusiastic about encouraging thinking outside the box when there's evidence of any thinking going on inside it. - Terry Pratchett

 

[mmorancbt]

QABaron,

I am surprised that you would indicate that going door-to-door is even questionable. It is the only way I had ever heard of finding work. I've never found an opportunity online or in a want-ad. The only opportunities I consider are referrals and those people I meet in person.

Why? There are a number of reasons. I've written and presented on this topic quite frequently but here they are:

1) Geographic considerations:
I do not commute. Time is far to valuable. I will only work 15 minutes or less from my house. I am very selfish wtih my limited time. I coach my kids sports team, like to eat dinner with the family, and like my wife's company.

2) The advantage of being the only game in town:
When you walk into a company and let them know what you do - and you get to know what they do, often, you are the only game in town. Many times a position has only been discussed by the company - they've never posted anything - and there you are - skills and all. You come across as ambitious and interested. For the 1 company that does not want the self-directed ambitious person, there are 20 that do. Besides, I don't want to work for a company that does not want self-directed and ambitious. It would worry me.

3) You control the contact and situation:
Yes, you get to bypass companies that look unappealing and select those that look appealing. You don't find this out when you show up for the interview - along with 25 other people.

4) You can command a higher wage:
Read Bolles' book, What Color is Your Parachute. He describes why most job seekers meet employers at the least desirable place. Employers do not like want ads. They are a high-risk proposition and they are unwilling to pay for high-risk endeavors. When you meet them directly you get more of their time, become more familiar with them and they with you, and you can command a higher wage.

5) Numbers play to your advantage:
When you meet employers directly, you create more opportunities more quickly than the passive want-ad, online resume mode. More opportunities means more options and the ability to better analyze the opportunities. When you have one job after, after months of want-ad seeking, you take it. It doesn't matter if it is the one you want.

I've blogged on this topic numerous times:

Opening Doors As Quickly As Possible:

http://blogs.ittoolbox.com/pm/career/archives/005103.asp

The Best Places For Business And Career:

http://blogs.ittoolbox.com/pm/career/archives/005057.asp

Create Career Coincidences:

http://blogs.ittoolbox.com/pm/career/archives/001346.asp

Warning: There will be people who tell you it won't work or that they wouldn't do it. Most people won't earn 6 figures part time out of their house either. I'm glad I didn't listen to those people.

Also, one person told me that he didn't like the thought of going door to door. Two thoughts here: First, I don't go door to door. I determine if the company looks the the type of place I would want to work. If not, I pass them by. Second, I asked this person whether he liked the thought of being out of work for 4-5 months and sitting at home waiting for the phone to ring? He visited several companies over three days and ended up with 6 job offers in about 4 weeks. He liked that, I guarantee it.

In any case, this style is not for everyone. It is only for those who want to make the highest wage, working closest to their home as possible, for the best companies, in the shortest amount of time. Everyone else should stick with want ads.

And have fun...whatever you do!

Matthew Moran
Read my career blog at:

http://www.cbtoolkit.com

Career Blog:

http://blogs.ittoolbox.com/pm/career/

Todo esta bien.. Todo esta divertido (it's all good, it's all fun)

 

[kHz]

My current and last job were found online! And they are both very good positions with great companies and have higher than average pay.

Both positions require skill and ability and they both wanted somebody with years of experience to trust their systems with. Both did extensive background checks before hiring and one required a gov't security clearance.

 

[chiph]

I would like to break back into testing but aren't sure exactly how (other than networking or sending resumes everywhere - can't imagine that will bring my desired response).

Microsoft is looking for software test engineers for the WinFS product. You'll need to be able to write C or C# code (they have a pre-employment screening test that usually involves linked-lists or a binary tree). And be willing to relocate to Washington state, of course (they pay relocation).

See:

http://members.microsoft.com/careers/default.mspx

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first

 

[CajunCenturion]

Microsoft is looking for software test engineers for the WinFS product. You'll need to be able to write C or C# code ...

This is more of philosophical response with respect to delineation between testers and developers, but

Why should a tester be required to write code?

One possibility is that the testers will be required to develop their own software which automates the testing of other software. That leads to the question, who tests the tester's code?

--------------
Good Luck
To get the most from your Tek-Tips experience, please read FAQ181-2886
As a circle of light increases so does the circumference of darkness around it. - Albert Einstein

 

[GwydionM]

Have you tried posting your resume here? That little box on the right, at least that's where it is on my machine. I've never used it, so I've no idea how useful or otherwise it is, but it's surely worth the effort.

------------------------------
An old man who lives in the UK

 

[GwydionM]

For a tester, as distinct from a coder, being out of touch with current IT might be an advantage. Things that seem simple and obvious to IT people have a way of confusing the people they are actually intended for. That's part of the tester's job -- not only 'does it work as specifided' but 'will it make sense to people who are not technically minded'?

Of course a tester has to understand the basics of the technology if they are to do useful work. Depending on your age, it would be worth showing you have mastered some recent bit of techology, or taking the time to master it if you're not. (I'm hopeless with mobile phones, but I already know stuff that's more relevant to my actual work, including stuff that I knew nothing about 10 years ago.)

------------------------------
An old man who lives in the UK

 

[chiph]

Why should a tester be required to write code?

Part of the WinFS "product" are APIs which will be called by developers (it'll be part of the OS, after all). So code will need to be written to exercise/stress the APIs.

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first

 

[langleymass]

I am learning neuro-linguistic programming and conversational hypnosis. I am currently on a contract and can't wait for it to end, so I have more time to study what this stuff. If you want to get people to give you a job, you have to capture and lead their imaginations. Eventually you can get them to think the way you want them to. It takes practice though.

 

[QABaron]

Hey CajunCenturion:
Trying not to reinvent the wheel here, so here's a response from Dave Plank about software testing that hits the mark:

You don't need to be a programmer to be a tester.

I can test any system developed for any purpose without needing to be trained in the programming language. Test Techniques are platform independent.

The point of testing is to prove that the system is 'fit for purpose'. That means the tester has to know what the system is going to need to do, and have an idea of what the business users need for it. I understand you don't get time to complete specs and the like, but to develop a system, someone has to request it.

This is the tester's first point of call. Effectively the business area (end users) are the customers of the tester and the developers are the suppliers. The tester should take time to discuss with the business area what they expect the system to be capable of, and how it will be used.

Once this awareness is clear, it is possible to define your test requirements. These can be signed off by business users and will form the crux of the testing.

You know the system has to be able to carry out function x.

You can extrapolate from this that in order to successfully carry out function x, then several conditions must be met. These are the test conditions. Once you have these, you match them to what the system is supposed to do.

Basically, you just created a test plan. And since it's been signed off by the business area, it's valid and undeniable as the basis for the testing to prove the system is 'fit for purpose'.

The main issue I can see is that developers and testers have the opposing mindset of creation - destruction. Swapping between the two is difficult (I can't manage it properly - I'm a tester through and through)

It is important that testers and developers have good communication skills to avoid situations arising. Generally I recommend that the tester(s) and developer(s) on a project share a beer/mineral water on a Friday night. Socialising provides a common ground, and this leads to greater understanding from both sides.

Back to me:
A different animal entirely is a software test engineer who may test the software by creating code to run the program through it's paces. I am not particularly enthralled with this type of testing since I really don't like most programming languages; however, I am up for learning a bit and automated testing sounds like a lovely challenge.

Thanks for posting to my questions, all.
=)

You must be the change you wish to see in the world. - Mahatma Ghandi

I'll be more enthusiastic about encouraging thinking outside the box when there's evidence of any thinking going on inside it. - Terry Pratchett