＜本文发表于: 相约加拿大:枫下论坛 www.rolia.net/f ＞
These simple questions are tough enough to check if the candidates have true experiences. I have enough questions to test the candidates. For instance, ask them to explain what is "dirty read", what is "phantom read", explain the difference of some APIs between different JDK versions.
I think it is natural for the candidates not to know something. So I allow the candidate to claim he/she does not know something I asked for. For instance, if I ask a candidate to write a few line Java code to load a property file and display it to the IO cosole, I am ready to get a nagative answer. This won't change my judgement on him/her. I may ask him/her to write a few lines of code to save an Object into a file. If I can remember, I may ask him/her what kind of design patterns have been used in the design of FilterReaders and FilterWriters. If he/she cannot give an answer, I may ask something else. From his/her overall performace, we can conclude if this candidate is knowledgeable and smart. In a job interview, I always try to give people opportunities to make mistakes, for instance. Book knowledge is not very important .
I am sorry we could not consider you as a candidate, because of some corporate policy. I wish you good luck.＜本文发表于: 相约加拿大:枫下论坛 www.rolia.net/f ＞