10 questions to make programming interviews less expensive -- Reference

Conductor interview is not cheap and costs both time and money to a company. it takes a lot of time to find the right candidate for a job from 100 s resume you receive from consultants and agents. they will always tell you that this guy is a Java guru, this one is SQL expert and next one is the full stack developer you are looking. if you have trust them blindly and invite all of them for face-to-face interview, you are going to be disappointed. one of the first thing you shoshould do is to filter candidates who claims to have certain skills e.g. SQL but doesn' t have them, the faster you can weed out those candidates the cheaper will be the hiring process. A phone screening interview is just for that purpose, it doesn't cost you much and also suitable for candidate, as they don't have to take off and come down to your office. it's flexible for both the parties. when I Phone interview someone, I spent fist few minutes to listen them and then I go for my list of weed out programming question to see If candidate is good enough to spend another 30 to 40 minutes. they have saved a lot of time, where I found out that candidate having words like"Strong knowledge of Java","Predictional in SQL"And"Programming Gurus"Fail to answer these simple questions. if you are a candidate and gone through couple of interviews, you might have noticed that almost all interviewers make up their minds in the first 10 minutes. the rest of the interview gives them reasons supporting said demo-, but not all is lost. if you ever feel that you have messed up with your chance, try coming of some really good answers on rest of questions, if you can impress interviewer to an extent that encourage you to go deep, you may be able to change his initial demo. to get some feedback and improve upon my method, I have decided to shareMy list of weed out programming questions(Don't bother about sharing questions, I have too similar questions on my secret question bank and you can create them easily as well ). I have chosen one or two question from common programming skill set e.g. java, SQL, XML, programming, coding, oops, multi-threading and UNIX. I am looking forward to know what you guys do, what do you ask to check Same skill set before calling candidates for face to face interviews. comment if you agree or disagree.

10 questions to start your programming interview

Here is my list of filtering or weed out questions for different programming skills. as I said it serves two purpose, it gives nice warm-up to deserving candidate, make them comfortable but same time weed out programmers who can't programmer or SQL expert who can't write join queries.

In SQL, my first weed out question is asking them to describe a left Outer Join. they don't have to get it exactly right, I just want to see if they have ever did anything more than a two table inner join. depending upon their answer I ask them classical SQL queries like write all orders and number of employees in that department to verify that whether they only know theory or can apply that knowledge as well. if they use inner join instead of left Outer Join they will be missed out on orders with no employee.

For a Web Developer the first weed out question is to explain difference between a get and an post. here at minimum I want then to know is that a get is what you generally see in the URL and a post is commonly what you see in HTML forms. again depending upon their answer, you can also further question about limitation, security and usage of get vs POST method. this question will give you enough hint that whether they really know something about Internet or not.


In UNIX, one of the popular weed out question is rather simple, how do you find a special process and kill it? Here I have CT them to tell me about ps, grep and kill. also to gauge their level of understanding you can ask them about PS options e.g. what does a, F and E means in PS-AFE command. second level weed out question in UNIX can be about command to find large files in UNIX e.g. files which are greater than 2 GB etc. don't get me wrong but if a person cannot answer these question, it wocould be difficult for him to work in a project which has tons of process and connected to tons of other server. one counter argument question against my weed out question, I always hear that it wocould take just 5 minutes to learn those commands, but they fail to answer me, when I said why they didn't spent those five minutes before coming to interview.

In oops (Object Oriented Programming), my weed out question is difference between class and object? Here I have CT slightly more than the popular definition of classes are blue print to create objects, yes that's correct but how do you know that he understood the concept and not just have mugged it, ask him to give examples, and then cross question him on that e.g. where does object get created, who creates it etc.

In programming, Fig when it comes to code, the most popular question to weed out the non-programming programmer is "fizz-buzz" test. if a programmer cannot write a fizz-buzz in 10 to 15 minutes, he probably needs more practice and not ready yet. this is something I don't ask on phone interview but on written test I have before face to face interviews. there has been instances in past before we had a proper interview process of multiple rounds where I had literally asked fizzbuzz, and their answer took the better part of an hour. another weed out question in my list for programming is to have them write Fibonacci series and ask them to optimize it. fibonacci is very common but you wocould be surprise with number of programmers failing to write in using pen and paper and even on IDE. it also weed out programmers who understand recursion than who doesn' t. my experience is the programmer who understand recursion are usually better than those who doesn' t. this is where most of natural programmers comes in.

In XML, my weed out question is difference between DTD and XML schema? Some one may say that it slightly harsh to judge someone's XML skill with just one question, but you wowould agree that this is a fundamental. I know there are using programmer who has worked in XML and can work in XML but doesn't familiar with this fundamental but shouldn't it's their responsibility to learn fundamental like this, just working is not enough, you also need to fill your gap.

In Java, my weed out question is difference between JDK, JRE and JVM? It's such a fundamental that I have CT anyone who has worked or learned Java shoshould know about it. here I recommend CT that they shocould mention about some tools which comes with JDK, at least javac (the Java compiler) and JVM, which actually runs every Java program. one more question in my list to weed out non Java programmer is difference between path and classpath? I have hard time teaching this fundamental to couple of people and have found that if you don't know difference between these two, you will struggle to set-up your project, debugging and fixing those nightmarish classnotfoundexception and noclassdeffounderror. it's again a must know detail for any one who claims to work in Java.

In multi-threading be it in Java or any other language, one of the good weed out question is asking candidate to write code to avoid deadlock. you can ask this question differently either by giving him a practical scenario or just asking about how to code so that deadlock doesn't happen. if you have not done has interviews, you will be surprised with how many programmers, with professional experience of 2 to 4 years fail to answer this question correctly.

In data structure and algorithms, the first question I ask to candidate is about how to add or remove elements from linked list, because I believe that as a programmer you must know array, linked list, set, MAP and string algorithms. if you want to add another level of cushion than you can also ask about how to remove duplicates in array without using any library function. this will give you enough idea whether to proceed further or not.

I knowTrivia is not a good way to find a programmers, But questions which are closely related to practical experience are good way to weed out someone who claims to know something but not there yet. the best way to find a programmer is to sit down with them and examine their projects, or have them to pair program with you. ask them what part are they most proud of and ask them what part they wocould change, why they wocould change it and how they wocould change it. once you do this, other than personality questions their is nothing more that you need to ask to gauge their ability to program. but if you do this with 100 programmers, you are not wasting lot of your time but also your organization time and money. before you invite programmer for face to face interview, you must ensure they deserved to be there. it's not practical to call all the guys based upon their agents claim only. let me know what are you set of weed out questions, what do you ask to C, C ++, Ruby, Python or Javascript developer to check whether they deserve your time or not.

Read more: http://javarevisited.blogspot.com/2014/09/10-questions-to-make-programming-interviews-cheaper.html#ixzz3Ef8ZUoPP

10 questions to make programming interviews less expensive -- Reference