The good: This CV has a clean and simple format with enough details to create a clear picture of the person’s background, but not enough to make the recruitment specialists’ eyes glaze over. Click here to view.
The bad: This CV is much too generic and short. For QA positions, knowledge of specific technologies or industries can make or break, so being vague will keep you from being considered for some roles. Here’s an example.
The Ugly: Coming soon. It takes a surprisingly long time to invent bad CV’s.
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:
Recent Comments