3 ms·
In the end, I'm always trying to have a "discussion about code" with the candidate. I ask questions that really are easy, but require a certain amount of listen
by gwbas1c 8y ago
In the end, I'm always trying to have a "discussion about code" with the candidate. I ask questions that really are easy, but require a certain amount of listening. This way I understand how the candidate behaves in more abstract discussions.
Some examples are things like:
- Walking the candidate through an outdated API (that the candidate isn't familiar with, but should be able to understand given the nature of the job)
- Walk the candidate through code that converts a database query into objects without an ORM. (Candidates who can't do this are incompetent. Really.)
- Discuss commonly-known details of exceptions / error handling in the language that the job is for
- Discuss commonly-known details of memory management in the language that the job is for
- Discuss API choice tradeoffs in an API that the candidate should be familiar with. (I like to pick serialization APIs built into the library in the language we will use.)
Also:
- I try to emphasize how I would do with my interview at the candidate's level of experience
- I have 2nd chances, and will usually stay on the phone for the scheduled interview out of respect. (There are still certain points where I will cut an interview short.)
- Make a decision to hire quickly.
Usually works well.
Signs to reject someone:
Figuring out how to use the teleconference software is an unofficial part of my interview. (Most of my interviews are conducted via teleconference because I'm on a global team.) There are candidates who take 15 minutes to figure out that they can type their phone number into the teleconference web site and it will call them back.
Candidates who want to answer a different question, or keep asking, "why can't I use XYZ" technique usually aren't hired. Again, the purpose is to have a discussion about code and demonstrate understanding of the discussion. I don't want to hire someone who can't adapt when the correct solution to the problem is some tool / design pattern / API / ect that isn't the candidates first choice.