-1

I'm trying to hire a QA engineer to come in and relieve some technical debt on our test suite. I'm having a hard time testing their knowledge of ruby and testing scripts in ruby.

Any suggestions on a good problem to give the candidates?

Improve this question
4
  • 1
    Did you try searching? I found a huge collection of sample questions by searching for ruby automation testing interview questions
    – Kate Paulk
    Commented Mar 28, 2019 at 13:59
  • @KatePaulk yup. thats why i asked. I found a lot of ruby specific questions but nothing about testing specifically
    – Deekor
    Commented Mar 28, 2019 at 15:54
  • I should mention we use rspec as well.
    – Deekor
    Commented Mar 28, 2019 at 15:55
  • 1
    You will get better responses if you take some of those suggestions and ask for situations where they would be good interview questions and situations where they would be not-so-good interview questions - you've got two distinct skillsets you're looking for: coding capability and test design capability. Chances are you're going to need to evaluate the two separately.
    – Kate Paulk
    Commented Mar 28, 2019 at 19:07

2 Answers 2

Reset to default
2

I'm not the most experienced guy when it comes to interviews, but this is my opinion on the subject.

I like to separate personal interviews and assignments.

Personal Interviews

For me personal interviews are mainly about two things:

  1. Attitude
  2. Discovering problem solving capabilities

The first one is quite obvious. Is the person a good fit to the team? Is he/she willing to learn? Will he/she enjoy the job?

The second one might be a bit tricky. Normally asking something that would require them to think. Something not necessarily tech related. Maybe start off with simple math problems, or anything that the person is capable of solving with his/her background. The point is to see how the person would solve a new problem. Something they've possibly never met before.

Of course for a senior role there should be also some questions about the technologies that are in use. But I don't really see the point of asking really specific programming questions throughout the whole interview.

Assignments

For the assignment you can give something similar that will be in use for their actual work. For example if you're looking for someone who will mostly work on UI testing, ask them to create a dummy application to test and create a UI test framework for that. Specify the technologies that should be used and maybe a few requirements. If you specify the requirements on the application, you can already see how they write test cases for example.

After submitted, talk with them about their solution, ask them why they chose to do it the way they did. What could be improved upon, etc.. From this you can tell much more about the technical knowledge of people.

Improve this answer
0

I suggest to give a test requirement and ask for automate it. Then the candidate should have to explain the how and why he/she have made every decision. Pros and cons should be described.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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