Hi there...just about to start a new job on Monday as a QA Analyst / Tester for a company that builds and runs six big websites getting c. 60M hits a month, yet has no real defined methodology for making and testing changes to them.
They want me because I've had c. 3.5 years of experience as a business analyst / tester, am used to working with a very structured methodology, and they want someone who can come in with experience of testing and application development methodologies, and work with the team to implement a slick, well-defined methodology within the company, and over time, build the one man QA / Testing department into a team.
I felt really confident during the 3 interviews for this position, and was really happy when I got it, as it's a great company and a great opportunity for me to learn a lot more and take on more responsbility. Problem is, I'm now getting very nervous about starting on Monday - I'm basically the only QA Analyst they're going to have, and, rather than the week or so I figured I'd get to browse through documentation, etc. and figure out what's going on, I'm straight into an update meeting on Monday at 10am to review the progress of a project they have going on at the moment to rebuild one of their sites.
I've got the '50 Ways to Improve your Software Testing' book which everyone recommends, and I have to say that, whilst everything makes sense, and I've come across probably 75% of the stuff in there, I'm feeling a bit overwhelmed by all the information, and suffering a bit of a crisis of confidence - getting the "Did I oversell myself", "I'm not going to be able to do this" thoughts cropping up!
Anyone out there had similar feelings before starting a new job, and if so, how did it all pan out?
<font size="2" face="Verdana, Arial, Helvetica">Well with what you said I dont think you will face a lot of problems. I had a similar experience once. I was **** scared too! [img]images/icons/confused.gif[/img]
Originally posted by srpa:
They want me because I've had c. 3.5 years of experience as a business analyst / tester, am used to working with a very structured methodology,
But i guess as they say - "in the land of the blind - the one eyed man is king" [img]images/icons/smile.gif[/img] I think you should be able to get thru with some preparation. My advice:
- prepare well on whatever you know - their current methodologies in developing the application and how the process you would suggest will plug in.
- take it cool cause u have a good chance on impressing them cause you have the experience and they dont (might be a bad assumption - but if they would know they would have implemented a lot of stuff - which doesn't seem like it)
- when your going thru the docs try to relate to your experience and what u have read about.
- you could try some new stuff too which you have heard about (code checkers? testing tools? frameworks? )
- improvement on other stuff like the build process? parsers? something like HTMLTidy?
- maybe migration to a better app/web server that you have used?
be careful on what you suggest though.
Best Of Luck! [img]images/icons/wink.gif[/img]
As a consultant, I've been in your situation many times. I've learned that most of the pressure you're feeling is put there by your own anxiety and desire to excel. No one will expect you to work miracles overnight. I accept every meeting invitation and take note of who handles what; those are people I can talk to later for more information. I just act as a sponge for a while; asking questions when it seems appropriate, and gathering as much information as I can, even if I don't understand everything at first. I've learned that before anything can be improved, or I can contribute anything meaningful, I need to assess the current situation and determine how best to start implementing some standard processes without upsetting current production schedules. I also like to get a feel for how much kickback I'm going to get from other organizations, particularly development, and decide how I can best meet those challenges.
In short, feeling a little overwhelmed at first is normal. But you'll be on a fact-finding mission for a while, and if you approach it that way, it should help your composure.
Ditto - to what Linda said - I started a new job 2 months ago as a Director of QA with a company that has 40+ in their QA dept. - they don't expect miracles right off the bat. Do as Linda says the first few months act like a sponge and absorb all the information you have, find out who the players are, find out what processes are in place - are they working, what can you do to improve them - I'm a huge beliver in piloting new initiatives/ideas before I try to shove it onto everyone plates. Pick something that you know you can get a good return on and something that'll give you a quick win.
As Linda says feeling overwhelmed is very normal, take your time and all will go well and use QAForums as a resource to bounce ideas off offolks and you'll do great!!
Best of luck!
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!
Linda is right
Unless you lied in the interview on any tool that you know very well, you don't see any wonders in new companies.Be careful on what you are talking in the meeting, notedown the names of all developers,database people,networking guys(if they are in meeting)so that you know whom you need to talk to when need arises.
You get enough time to read documentation and application on what you are going to test.
Nobody expect you to do wonders in overnight.
Thanks for all your help and words of encouragement - feeling a lot more confident about starting the job, and looking forward to getting stuck into a challenge. Will doubtless be a regular poster / contributor on this forum from now on!