When hiring testers it’s important to know what problem you are trying to solve.
By defining the problem that you have you’ll be able to ensure you solve the problem in the right way, whether that be by recruiting the right person or actually coming to the realization that recruitment won’t help.
Throwing more testers at a test problem is no guarantee that the test problem will go away.
For example, to handle a growing regression suite the answer may not be to hire more testers. It may be to hire a test automation specialist to automate the tests, or to encourage your developers to automate more tests.
Another example is poor quality products going out to production. You may improve the quality by hiring more testers, but you may also improve the quality by slowing down, spending longer designing what you’re building or working out some way to get rapid feedback on what is being built.
Recruiting is often time consuming and expensive so it’s always worth assessing whether recruiting more testers is going to solve your problem. To do this you need to know what problem you are trying to solve.
When you define your problem you’ll also have a clear understanding about the kind of person you are looking for. This will help you articulate your needs to recruiters. It also allows you to communicate more clearly to the candidate.
Being able to explain to a candidate what they will be doing and why it’s important for the business will increase your chances of a candidate accepting your role (assuming that’s what they want to do). Don’t be surprised if a candidate doesn’t accept your job offer if you cannot even clearly explain what their job role would be and in a sense, what problem they are going to solve for you.
Not all testers are created equal so it’s crucial to know whether their aptitudes and skills will solve your problems. Some are better at exploring, some are better at designing, some are better at building bridges between teams and some are very good at automating anything that moves. Each one of the above examples will help to solve a problem but not all of them will solve all problems.
By understanding your problem deeply you’ll be able to work hard to solve that problem. Simply hiring testers because you “feel” like you need resource leads to bloated test teams and ineffective delivery. And of course, the chances are you wont have solved your original problem.