Feedback on "Pair Programming Interviews" Post #1
This feedback is a mixture of a braindump, what I consider important on this topic and my thoughts, as well as my opinion or questions about the specific points already mentioned in the post.
Feedback on already existing draft
quotes from here on, are quotes directly from the draft
I also think it's important, esp. wrt reducing possibly anxiety and/or stress of the candidates, to be very explicit about the interviewer's/company's expectation towards the interviewee. What amount of time should the person plan for? What prep should the interviewee do before the pairing session? Should they read up on some stuff? Should they already possess some specific skills or know about some specific technology?
Furthermore, in the past I found it important to state in advance, what kind of coding "style" was expected in the interview. Is it expected that the candidate shows their best/cleanest possible code? Or something else? Should they obsess over naming, more than they would usually do?
I don't see why this is a relevant aspect. If you want to keep it, IMO you'd
I find this eventually hard to do right and would drop it. If you want to stick to this, then make it very clear, what should be installed on the interviewee's machine, which version of language runtimes, and the steps you will need to perform on-site in order to get the codebase which you want to pair on up & running. Again, even if it the project setup is really just a
Be sure to not be hand-waivy about this in the final post. This is very hard to
I suggest reading 'Why Hiring for "Culture Fit" Hurts Your Culture'
Other from the word 'culture fit' I would question the usefulness of this not-goal. Can you really not assess if someone "feels right". And if I put it this way, I think this not-goal is nearly the same as "See how chemistry works out" which you state as a goal above.
So, I'd scrap this from the list completely.
And while we're at it, here's my reading list for hiring practices, not
The text was updated successfully, but these errors were encountered: