本文发表在 rolia.net 枫下论坛For a Java-programmers with hands-on experiences, all of my questions are easy. However, not a few "senior" Java programmers sweat for these questions. For instance, one candidate claims his main Java servlet experiences are related to Image processing, not to page generating. I asked him how to write first lines to get a Graphics object in a servlet, but he was stuck. At this point, I had concluded that he was trying to cheat on me. I lost interest in questioning hin further and gave him my permission to boast about all the "projects " he had been involved in.
It does not make sense to test how much knowledgeable a candidate commands. My point is: If you claim you know something, that must be true. In the job interview, a guide line is to figure out whether candidates has some true experiences, whether they have a good potential, whether they are good at communications. Tough questions do not help much for our screening candidates.
I think you are a veteran. But I have to say, I have seen many "senior" Java programmers with a junior level understanding of Java. For instance, as I tried to initialize some talks on Java Threading, most of them can tell me that there two basic ways to create Threads. Some guys even told me that Java Threading is very simple. As he/she said that Java Threading is very simple, actually he/she has lost in the Job interview, because I would be desparate in convincing him/her that things are not as simple as he/she read from Core Java or Thinking in Java. Here are some questions to come yet: How do you manage Thread group? If your Applet needs to download a 100-MB image, how do you set Thread priorities here? Is there any use of ThreadLocal class in the real project?
By the way, one candidates claimed he is good at Java performance tuning. But he failed at my very first question: "What kind of profilers did you use?" This guy is my countryman and he could not understand the word "profiler". I explained what the profiler is but he still could not give an answer. To help him not to embarrassed, I asked him to describe how he did performance tuning. His answer was that he checked on all the code in the project and did some modifications so as to make it run faster.更多精彩文章及讨论，请光临枫下论坛 rolia.net
It does not make sense to test how much knowledgeable a candidate commands. My point is: If you claim you know something, that must be true. In the job interview, a guide line is to figure out whether candidates has some true experiences, whether they have a good potential, whether they are good at communications. Tough questions do not help much for our screening candidates.
I think you are a veteran. But I have to say, I have seen many "senior" Java programmers with a junior level understanding of Java. For instance, as I tried to initialize some talks on Java Threading, most of them can tell me that there two basic ways to create Threads. Some guys even told me that Java Threading is very simple. As he/she said that Java Threading is very simple, actually he/she has lost in the Job interview, because I would be desparate in convincing him/her that things are not as simple as he/she read from Core Java or Thinking in Java. Here are some questions to come yet: How do you manage Thread group? If your Applet needs to download a 100-MB image, how do you set Thread priorities here? Is there any use of ThreadLocal class in the real project?
By the way, one candidates claimed he is good at Java performance tuning. But he failed at my very first question: "What kind of profilers did you use?" This guy is my countryman and he could not understand the word "profiler". I explained what the profiler is but he still could not give an answer. To help him not to embarrassed, I asked him to describe how he did performance tuning. His answer was that he checked on all the code in the project and did some modifications so as to make it run faster.更多精彩文章及讨论，请光临枫下论坛 rolia.net