Writing a QA or software tester CV is a lot like writing any other CV, but there are some particular things you want to include to ensure that your details get the attention of the right person.
Things to do:
So, as development on Jobyssey rolls along we’ve stared seeing more pieces of functionality completed and ready for testing. As a start up, our developer hands over the code and it’s up to us to check that everything is functioning properly. We found a real dearth of ideas about how to implement an extremely simple, basic QA procedure. Plenty of ideas as to why QA was important, why you should hire QA people, how you should track bugs and so on, but not much that spoke to the “QA on a shoestring” contingent (Yo).
Here’s the procedure we followed:
I’m working on the Jobyssey help section at the moment. In addition to the normal trouble-shooting stuff we’re adding advice sections, and we’ll have a section of interview questions for specific roles too (so, if you’ve never interviewed a project manager or head of QA before you can generate some ideas about specific questions for their roles).
After jotting down the questions we usually ask for these positions I went out and trolled the Internet to see if there was anything I’d missed. Pretty quickly I started turning up “gotcha quizzes” (see an example here for graphic designers). Basically, these are lists of specific facts to interrogate potential employees with- Is Avant Garde serif or sans? What’s the difference in PHP between include and require?
This is not a great approach for a plethora of reasons:
Recent Comments