Link Details

Now if at least half the people I interview would just study the interview questions and tell me some 'good' lies.....

I want to create a Java interview prep site loaded with disinformation just to see if I get someone in an interview reciting off of it.

One can always look at things "glass half empty" or "glass half full".


Let me look at the "glass half full" aspect:


-- There are number of Java/J2EE interview questions and answers sites (anyone can create one in a week), but
this site stands out from the rest by having a wide coverage of Java/J2EE based technologies, popular/faq interview questions are answered clearly and concisely with lots of diagrams, examples, code snippets, cross-referencing, emphasis on key areas etc which took over 18 months to come up with. So this site is a very handy career companion and it is evident from reader feedbacks and review comments I receive every day.

-- I have interviewed Java/J2EE candidates who are excellent coders but do not come across very well in the interviews. This may be
due to being nervous, not being confident enough, being more of a hands-on practical and detail driven person than being a person who is concepts/fundamentals/theory/big picture driven. This site will not only act as a great refresher material prior to interview(s) but also a confidence booster. This site will also help Java/J2EE practioners to have the right balance between practical experience and the theoretical knowledge. In my view a good Java/J2EE practioner should be able look at the big picture and skilled/experienced enough to drill down to the level of required details. This site can definitely give one the big picture and enough details to reflect back on your past/current experience if you are an experienced developer or act as a learning guide & a road map if you are an inexperienced developer.


-- This site is not meant to be an interview cram guide although one can use it that way. This site is meant to be a pro-active
companion to fast track your career by being ware of and by applying the key areas (e.g. design concepts, best practices, design patterns etc) mentioned in this site in your regular job to become a high calibre practioner in a shorter span of time. Like any other tool/book, you can always abuse it by cramming it. If I am hiring a graduate level or a candidate with less experience, I would rather hire some one who is at least familiar with or aware of some of the core concepts/theory/key areas/emerging technologies. If I am hiring an experienced candidate then only way to prevent cramming is by conducting a comprehensive interviewing process (unfortunately some interviewing processes are not adequate).


-- Only criticism the 400+ interview questions and answers had so far were "Some grammatical errors" -- English is not the authors' first language & "being bit on the expensive side" -- thousands of man hours had gone into producing this and also you are at the mercy of the wholesalers and retailers. If you look at the brighter side, the authors have been touched by personal emails of readers' interview success stories and a small investment on your career advancement with a potential for much greater payback.


-- Do not take the authors' word for it. Get you’re free downloads and you be the judge. There are a number of free downloads.

I will not defend myself in front of negative voters. I will rather make justice to the hard-work I have put in (just like how you provided free downloads). Who has time to read a big thesis of defense? It then looks as if someone is "selling" something. Keep up the good work! Do not take advice from (intellectually) broke people.

It is very good link. The quality of the information is very good. Especially Java/J2EE Career companion is worth full book.
Within short time with this material we can get grip in Java/J2EE technology. Very good reference book.


Thanks to author.

Whether or not someone writing something to be posted here, and other places, has English as their first language is irrelevant. I cannot go into an interview or a job and feel okay saying "I know my syntax is a little off, but C# is not my first language."

Just as something small can change the way a line of code executes, placing a comma incorrectly or using the wrong tense of a word can change what a sentence means. It happens too often in IT books and literature, and when it does it is often missed because to someone who already knows the information will have their mind skip over the sentence structure. At the same time, those who are trying to learn won't be able to guess at what the author meant the sentence to actually say.

These questions and the interview guides are lit up by Google and sold on other sites [the full versions]. I would be fired if I thought to flippantly display a belief that communicating properly is not a big issue, and then insinuate that it is petty and impolite if someone thinks it is important to actually communicate clearly.

I have no doubt that someone writing something like this can speak English better than I can speak his or her first language, but that is not the language in which it is written.