I used to have a list of 200 or so questions covering Java, Javascript, C/C++, Oracle/DB2, Application servers (you get the point). I found though that I lost focus about why we were really there. Since i've given up my list I find I've given better interviews.
I usually start off with talking about the candidate's favorite project. This tells me how much pride they take in the work they've done.
I'll follow up with asking about what books they may have read in the past 6 months, to see what areas they are interested in. I tend to prefer hearing about books not related to the job.
Next I comb through the resume and ask at least one question on every skill they have listed. This shows how trumped up a resume they have.
Lastly, I have some trick questions I throw in, just for fun.
- What is CAFEBABE?
- Does Java support pass by reference or pass by value?
|