I just received a "blog kit" about a new QA company called uTest, and I'm looking for information from people in the community who have dealt with them.
From first glance, it appears to have a bit of a unique set of strengths and weaknesses compared to traditional QA firms.
On the upside, they're trying to take advantage of the "many eyes" philosophy of testing and they seem to be trying to match testers to products within their areas of expertise. It does seem to be a nice, low-impact means of getting your foot in the door of software QA.
On the downside, they're a "pay-per-bug" place, which leads one to ask who determines whether or not it's a bug, do you get paid for duplicate bugs, and are all bugs created equal in the eyes of the payor? (In other words, am I going to get the same for finding a crash bug as I am for a misplaced comma?)
For the unknowns, how do they handle build security/watermarking for firms, can we remove testers from our products that don't "get" QA, how do they handle firms that reject bugs to prevent payment while fixing them anyway, etc.?
A lot of questions, and hopefully some good answers.