I was wondering if somebody has done this, and to what success compared to the classic method of getting them to solve a problem as you watch on?
Any pointers on how to carry this out in an interview situation?
I was thinking about doing this for mid/senior candidates which should definitely have the technical knowledge to do a pull request. I was thinking it may be a good character test, if they give a full fleshed out and kind response, as apposed to "NO!". You may really see how they will get on in a team.
The way I was thinking about doing this, was to send a candidate a small piece of code before the test. They could read through it, ensure they understand what it does and any technologies it uses (I hate interviews that confuse peoples ability to program with how well they know an API).
Then when the candidate comes to the interview you give them the pull request, using Jira to do a git pull request. Since the web interface just shows you what has changed and the ability to view the raw before and after I do not think this would be large barrier to entry.
My core theory of this was to try to remove the memory game test/pressure cooker a lot of interviews can be and try to let somebody show how they would work on a daily basis with you.
To summarise, I want to know if any one is currently doing/done something similar and what outcomes they see. Also any pain points that became evident when you started this process.
Thank to everyone who has answered so far they are helpful and very valid but my original intent with this idea was to stop interviews looking for cookie cutter programmers and to let raw talent shin. I wanted to test this theory here with fellow programmers that would possibly go through such a process.