> Would you mind telling us more about your recruitment process? So, in general, I ask 2 main questions: - talk to me about you, what you like and which proje

> Would you mind telling us more about your recruitment process? So, in general, I ask 2 main questions: - talk to me about you, what you like and which project you worked on that you liked. - a generic question, that can be a bit misleading, on purpose. Like "What is the difference between TCP and UDP, and is HTTP over TCP or UDP?" for webdevs or "What is the =0 in C++ classes headers? Since NULL and 0 are the same, can I use "=0" here?" for C++ devs, or "How would you improve C if you could?" The first type of questions see if the person truly likes software development, and is not here just because "that's what cool kids do" and that removes a lot of bro-grammer. The second is more to see the generic culture, and if the person was curious enough to look a bit at the core of the technology they are working on. Because there isn't a yes/no answer, you must discuss. And also, I need to meet in person. No 1hr phone-call, no white-board, no multiple meetings, no complex CS question that anyone can prepare. I have one big issue with recruitment process: when I meet people, after those 2 questions, I can know very quickly that I don't want to hire them. If we are in the first 5 minutes of the interview, how can I tell them "no" without being too rude? Finally, the culture, and the political culture of the community must fit. And unfortunately, sometimes that shows on the resume/introduction mail. But to be honest, it's rarely been an issue, except for one intern once.