Most important requirements to put on a QA job posting?

Question

We're in the process of hiring a new Q/A person for our team. The previous person wasn't as technical as we would have liked and lacked formal Q/A experience. This was probably due to the former posting going up and the requirements not matching what the job expectations were! As a result our teams development suffered for quite a while as we had to bring that person up to speed. After the fact, we lacked good test plans etc.

Going forward, I wanted to poll the group and see if anyone else who has hired a rockstar tester can give us some tips. Our goal is to hire a tester that knows Q/A processes, is flexible, and isn't afraid to ask questions. We need someone who wants to "rise to the top" and become a lead of the existing Q/A team. (yup, I know these are good points to convey on that posting!)

I do know requirements on a posting won't be the be-all-end-all here and the interviews are the next and more important step. I've had some fantastic answers from this group and I just can't not ask!

Answer 1

I am not sure about your "rockstar" attribute ;)

But make sure he/she knows what metrics are for when using them in a Q/A process.

Answer 2

I'm going to use information gleaned off this question as well as this site in addition to the mention of metrics. Anyone else have any points to add?

Answer 3

1. Knowledge of a dynamic scripting language (any) would be a plus.

2. Requirements Engineering knowledge, specifically how to create and maintain a RVTM, and how to inspect and review requirements.

3. Good problem solving skills.

4. Detail oriented. All the best testers I know love to dig into the details of everything; code, cars, computers, A/V equipment.

5. Any experience with the programming language you use would be a plus.

6. Knowledge SDLC (any) and where QA fits into it.

7. Politically savy. Must know when to "stand up" for quality at the expense of schedule, but in a way that doesn't alienate. Must know when to compromise for the overall good at the expense of quality.

Answer 4

Your job posting should include something along these lines:

The successful candidate can explain the difference between Quality Assurance and testing.

QA isn't just testing. It's reviewing requirements, providing input during the design phases, performing code reviews, and analyzing real-world performance after ship.

The point is, effective Quality Assurance requires more than just testing. An exceptional QA candidate should know this.

Answer 5

Thick skinned. :)