I think this is a much better idea than asking questions such as "Where do you see yourself in 5 years?" etc. :)
Let me share a few points I find important:
Regarding the application under test. I'd personally choose one I know and one where at least some bugs could be found. That's because I'd like to see the candidate reporting issues or at least talking ...
This is a very interesting topic and I have conducted a few interviews similar to this and here is my feedback based on the interviews:
You can evaluate candidate's ability to find out bugs within the given timeline.
You can evaluate the candidate's ability to focuses on functional or non-functional issues first.
You can judge the testing approach of the ...
Quite interesting topic and although this question has been raised two years ago it is still a current topic! Hence I would like to share our experience / thoughts.
Preparation from our side as business department:
We used a web application
Before starting we explained the product
We encouraged the applicant to speak all his steps "loudly" so that we ...
Although this topic is 8 years old nevertheless there are some updates in the exporatory testing methodologies and tools. Hence I will provide an update: In our project we tried it with Tricentis. It was very helpful for the testing procedure - especially in the way of exploratory testing.
Somehow with this add-on tool you plan your session testing before ...