Ask real-world problems
We have set of pre-compiled questions and tests asked to each candidate to see how well he meets minimum requirements for position. We expect good understanding of the required technical topics.
We start our
face-to-face interview (after a pre-screening phone interview(s) of course) with a question on what are the interests of the candiate, and continue with basic fundamental questions and then adjusting the level on how deep we would like to continue with that topic.
guidance in technical topics is candidates resume. Thus,
spending 10 minutes to read resume before interview is more than important. We try to check important stack of technologies by real-world daily routine questions, that only hands-on experienced candidate may have glue about.
I would suggest to combine some real-world problem solving questions and try to see how candidate reasoning of problem work. If candidate answers honestly, and saying he does not know topics that we ask, we
really appreciate honesty and not bullsh**ing.
As an example: if some candidate claims 6+ months of work with
jQuery, but can not explain what is
"selector", i would just stop asking further. Because, power of jQuery is coming from good understanding of selectors.
Same thing holds true for other topics like indexes in Database. If someone memorized what is cluster and non-cluster index is, but could not give proper explanation when and where we need indexes, by claiming 2 years of experience in DB development then everything is clear.