I am applying for several jobs in QA (games testing) and am writing my cv. Now i know the basics of cv writing and what to included but I am really not sure what to put in about myself and about experience. I have never been employed in IT/ICT before (been a paper boy, lifeguard) and so really the only experince i have is community based. However that fact that its a hobby dosnt make me any less envloved and its all still real experience Thing with games testing is that to be a good tester you need a few main characteristics Love of playing games of many genres (yup) Think outside the box (you have to be an explorer and love to really tair things apart) IT liturate (yup, office suite skills are needed but I dont think there are many of us here who cant use office, though many of us wouldn't through choice) and of course the normal things an employer wants, reliability, punctuality, good communicator etc Now i know I would enjoy QA alot and anything i enjoy i will preform well at because i love to do it So anyone willing to point me in the direction of a few QA cv examples ?, maby someone who works in QA could give me an example or give me a lil chat on msn Finally what other experience is good to have and relitivly easy to get ?, i know doing some unpaied beta testing is great experience thing is there are so many applications and often after selecting a few specific aplicants the companys will pic at random making it nothing but chance, something im not fond of Anyone who can offer any help with the cv, experience, suggestions or anything benifical what so ever i would be very greatful Cheers

I'm sorry if this won't be much help, but nobody seems to be replying, so I'll give it a try. [edit: I've worked as QA in the software industry for 3 years. Not games, and I've not worked in that Industry.]

Quote:
I am applying for several jobs in QA (games testing) and am writing my cv.

Well, which is it? QA work is generally different from 'testing'. Testing generally involves playing the game haphazardly and reporting on your impressions, and any problems you might stumble across. QA will often be more methodical, requiring you to design and execute cases for specific areas of the code. They require different skills, and will likely change how your resume should be formatted.

Quote:
Love of playing games of many genres (yup)

This is actually only important for the 'tester', and if you're only going to work on one game, the genre variety might not be so important. For QA work, actual game experience is far less important.

Quote:
Think outside the box (you have to be an explorer and love to really tair things apart)

Good to have, but the exceptionally vast majority of QA work is obvious. Take Engineering specs, write obvious test cases, execute obvious test cases over, and over and over again.

Quote:
Now i know I would enjoy QA alot

I wouldn't be so sure.

QA work [in my experience] is the worst job I've ever done, slightly below Summertime Greenhouse Cashier. Maybe 'testing' work is better. Maybe white-box QA is better. Maybe QA at different companies is better. *shrug*

Quote:
So anyone willing to point me in the direction of a few QA cv examples?

Mine is not for public consumption, but a resume is a resume. Take experience [even informal], education, and employment. Put the one you're best at up-top, worst at the bottom.

Quote:
Finally what other experience is good to have and relitivly easy to get ?, i know doing some unpaied beta testing is great experience

Yup. That's the only easy experience I can think of quickly.

Quote:
thing is there are so many applications and often after selecting a few specific aplicants the companys will pic at random making it nothing but chance, something im not fond of

Like any job, social networking is far more likely to win you a job than any actual credentials on your part.


And one last tidbit: You might want to work on, or focus a little on your writing. That's fairly important for QA people. Test cases you write must be descriptive enough for others to follow. Bug reports must be clear enough for engineers to reproduce.