Yes, it would. I like teams that execute exploratory testing in pairs, I think it is easier to write charters, create mind-maps and decide on heuristics together than alone. It will keep you sharper, you will go faster in executing and analysing the results.
I would like to find answers on the following questions during an interview:
- Will your team like working with him/her?
- Can they design good test-cases?
- Can they produce reproducible results in a free-format?
Seeing how someone would approach a pair-testing session is worth a lot. It is about communication and test design. Also, you will notice if someone is a quick learner. Can they lead the session and get some results while working together with someone else. How do they respond to critical feedback during the session.
Exploratory testing sessions are time-boxed, making it a great candidate for a second interview test. You can perform it with a time-box of let's say 45 minutes and work with a tester colleague. Afterwards, review the results together with the hiring manager. Giving the candidates room to explain what they would do differently next time for example. Resulting in an interview of around 1.5 hours, which I think would be acceptable.
Alternatively, I would do pair-programming of test automation on a simple application. Just like I would always do a pair-programming interview for developers.