Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

A variant on the How should you interview for QA positions? I am interviewing candidates for an Automation position, we don't use commercial automation tools, but rather use a framework using mainly Perl, so knowing Perl or some other programming language is required, but being a "computer geek" is a great plus. Another problem is that good programmers tend not to have testing state of mind, they will follow the needed design but will have a hard time going from test case to test code without forgetting something in the way.

So... besides some basic programming questions, maybe a single very basic testing question, what else should I ask ?

share|improve this question
this appears to be an exact duplicate of the question you linked to - I don't see anything different in what you're asking here. Can you explain what additional information you think you'll get, that you don't get from the various answers to the original question? – testerab Jun 4 '11 at 13:07
Interviewing for a wider set of skills is a challeange – Rsf Jun 5 '11 at 3:19
I'm not seeing how that helps people give a better answer to your question though? – testerab Jun 6 '11 at 3:21
up vote 16 down vote accepted

In my experience, if you hire an "automator", you're going to get someone who can write code, but has no skill or desire to test. And that's fine if that's what you want.

However, if you just want tips on how to hire a tester than can automate, then ask testing questions that have potential to be solved more efficiently with code. An example I use frequently is "You're in charge of testing a fuction that returns a random number between 1-6 (esentially a die rolling program) - how would you test it?"

I won't go into the details of the answer here, but testers who can program, are good at recognizing the scope of challenges in this problem and will have ideas on how writing automation and analysis tools will help them address the challenges.

share|improve this answer
+1 Problem solving skills and analytical skills can be evaluated by giving a challenging coding exercise/puzzle – Aruna Jun 4 '11 at 18:06
+1 for if you hire an automator. If one knows exactly what automated tests need coding you need a developer. If one does not one needs a tester who can code. – kinofrost Jun 8 '11 at 8:27

You must define the role before you can determine the interview questions. You need to ask yourself - what will this new hire be expected to do?

Will your Automator actually be required to do any testing? Or just build automation tools? Will your Automator analyze your needs and create her own requirements? Or is someone else creating the requirements? Will your Automator be required to conceive, design, and develop a test automation framework? Or is that already in place, and this person will just write the code to fill in the missing pieces?

Knowing that answers to that will help steer you in the right direction.

You may need only a developer, who happens to be developing test automation code. Or you may need a tester, who can build automation to aid in her testing. Or you may need a designer/developer with domain expertise in testing and test automation who can analyze your department's needs, design an effective solution, and develop the code to implement that solution.

The sourcing and interviewing of the candidate will change depending on your choice of role.

share|improve this answer

I've been very successful in asking candidates to write code for some simple algorithm and then have them test the code as if someone else wrote it. I try to look for tests that go well beyond unit tests and into integration or system tests. If they are good coders and good testers, they will start to go into more complex areas like boundary, stress, performance testing, and lots of white box. See if they come up with good ways of looking into the code they are testing and that they are comfortable with it. Do they know how to debug, interpret code, understand complexity, understand callpaths, think about code coverage? And echoing some of the answers in How should you interview for QA positions, make sure they don't give up - if they are good testers they will figure out lots of crazy ways to break what they're testing and shouldn't stop until the interviewer says so. Good coders will stop with unit tests. Good testers will stop at black box. Good coders + good testers are ninjas on fire.

share|improve this answer

To evaluate the candidate's creativity give them some exercise involving lateral thinking skills like testing a new feature that is not yet implemented on Facebook. Are they able to think about the risk areas?, Are they able to ask you good questions to go about the exercise? What different test methodologies come to their mind while testing it?

In testing you could ask about the framework and test methodologies. This way we can evaluate if they are aware and really understand why they apply certain test methodologies in certain situations and the benefits and disadvantages of using one approach over another. For example you could ask how to design test data while testing "post comments" feature in facebook. What are the pros and cons of using data-driven testing approach or random test data generation approach in this context?

share|improve this answer
Your idea is good in general, but it assumes the candidate knows Facebook, or whatever system you are asking about. My experience shows that it is hard to find a common large enough system to ask about similar question. – Rsf Jun 3 '13 at 10:25

Here you can find lots of: Automation Testing Interview Questions and Answers

Regards, Akaas Developer

share|improve this answer
Unfortunately, the post at the link you provided has some questions that you can ask to a non-programmer entering the field of testing. In the context of this post, those questions won't help the interviewer gauge anything about the candidate's skill sets. – Suchit Parikh May 17 '13 at 18:09
I wouldn't use these questions to interview for any testing position, no matter whether a candidate applies for manual tester position or automation job. Most of those questions do not focus on solving the problem, but rather on checking whether a candidate learned by heart some definitions. Hence, instead of asking what is ETL process, I would ask how would you test this ETL process? And then going in automation part of the interview: How would you automate then your test strategy for this ETL? – dzieciou May 18 '13 at 6:27

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.