Ok, ok, it’s not literally called boutique tester. But listen to this:
You: someone who can make guesses about how a website or application is going to fail, prove that you’re right, and then communicate it clearly and effectively to the folks who need to fix it. Ideally, you also have the ability to predict the things about our products that will confuse or dismay a new customer.
As an example of what we do, imagine we have four months to write, test, and ship two applications on a brand-new hardware platform (with no specimens of said hardware in the building) while still updating and maintaining our released products on both platforms. Could you keep up without going totally crazy in the process?
If so, we’d like to hear from you — we’re looking to expand our QA department by adding another Software Test Pilot.
About the future of software testing
For the past couple of year I have been engaged in a sort of shadow-boxing match of ideologies with some folks. Predominantly in the United States it has been with the idea of the tester/developer – that “the tester of the future” /will/ be writing test automation code, not doing actually testing, and the customer-facing tester will “go away.”
Now certainly, I grant that testers will become ‘more’ technical over the next decade or so, but then again, our entire society is becoming more technical.
I still think it will take a variety of skill sets to find defects on different types of projects. We might have more tester/dev-ers in certain places, but I think “going away” is a bit strong.
In fact, I believe there are some simple economic conditions that make a boutique tester a valid choice for a company like “the omni group.”
More to come. Or maybe more on test estimation to come. Either way, I’m writin’ again. 🙂