In one of the interviews that I attended, I was asked 2 questions:
- From a particular release perspective, how (on what basis)would you say, that the QA has done a really good job this time? How does one evaluate QA effort for a particular release? Based on what criteria?
- How does a QA manager evaluate performance of a QA engineer? How can he determine that the QA engineer has done a good/bad/ugly job? What criteria?
There are no the answer. There are a lot of answers and some of them may be better.
You should be able to come up with at least one (no matter how poor or even naive) answer. So go ahead with your round-about!
My math teacher used to say (rephrased) "Please tell me what exactly you don't understand and I will explain it to you. If you don't understand anything you have to go to the first grade"
?:the art of a constructive conflict perceived as a destructive diagnose.
A reasonable answer would have been... If the exit criteria has been satisfied/signed off and the released product does what it's supposed to do and what it's not supposed to do according to the requirements and your test documentation (i.e. risk analysis/matrices), you've done a good job...
Intellectuals solve problems.
Geniuses prevent them.