Had one telephone interview which did not go as well as I would of liked, basically as had not done certain areas of core Java at the role I was in was using an in house Java API and XML.... After that telephone interview I spent �300 on books and got this book in PDF form.
Straight away my knowledge of Java grew. Simple questions like why use intern() and what is it I then knew. The answers were probably explained in details (I like totally know it). Shortly after reading the first chapter of the book I was getting numerous job offers!
The book is good for : 1. Refreshing Java knowledge 2. Improving knowledge of areas previously believe totally knew! e.g. using intern(). Look at substring sun code.... use of new keyword. 3. Learn new parts of Java which Id never touched like JSF, hibernate, but gives reader an overview of technology so at least you have some idea! Also has diagrams (thank god).
After landing a job I have kept on reading the book and recommend it to all my friends. At work recommended it to my peers/manager as a resource for improving everyone current skills! Its not just for interviews, its for improving one's knowledge/knowing what's out there too.
My former colleague has also bought it too, even low he borrowed mine he found it so good he bought it.
One for everyone's bookshelf and bed time reading!
My only question is how did the author manage to make such a book! His brain must be like an elephant and would love to be his understudy as would learn so much! and i am a Senior Java Developer
Judging from the title this seems to be a great reading for just about to graduate students like me intersted in enterprise computing. Would you say, however, that the book is targeted at students, or is it a rather more appropriate reading to young professionals willing to make a step ahead in their careers?
Originally posted by arulk pillai: Thanks Darren. It took a good 2 years part-time to write. I collected the information over 3 years.
Hello Arulk, in all-likelihood I will be getting this book as the phone and face-to-face interviews have become increasingly more difficult than in years past. I have noticed a trend with interviews, say typically, a 2 or 3 tech interview gauntlet: each tech has about 5 to 10 questions for a total of 10 to 30 questions for the opening gambit. The more expertly I answer questions the more the level of difficulty of the questions increases until the questions are from the more infrequently used and obscure parts of the Java code including frameworks and toolkits derived from core Java. One wrong answer during the interview and it is game over. Background and experience seem to have no weight in getting a Java job. I would expect that background and experience is needed to write a book about Java interveiw questions. Unfortunately, I for one and many other Java Programmers cannot write books about Java for a living.
Yet some, not wise, go to the other side of the globe, to barbarous and unhealthy regions, and devote ten or twenty years, in that they may live,-that is, keep comfortably warm,- and die in New England at last. Henry David Thoreau - Walden - 1845
posted 12 years ago
As a contactor I get to move on from job to job and I might have attended about 45-50 interviews to date. Generally attend 5-6 interviews before settling on a contract. I collected the questions from my own experience and from others' experience.
This book is targeted for novices to seasoned pofessionals. Novices may have to read more fequently and repeatedly compared to seasoned professionals.
can help as a refresher material on a vast Java/J2EE topics if you are an experienced professional but a bit rusty on certain topics. I use it myself fo this purpose.
can help as a study material/roadmap on fundamentals and key areas relating to Java/J2EE topics if you are a novice or less experienced to fast track your career.
can help as a quick reference material while you are working on a Java/J2EE project to pro-actively identify issues and build a better quality software whether you are a beginner or an experienced Java/J2EE professional.
can help as a Java/J2EE job interview preparation material/confidence booster whether you are a beginner or an experienced Java/J2EE professional.
I have made every effort to cover enough details while keeping it short for brevity with diagarms, examples, code snippets etc. For readers who need extra explanation my suggestion is to google for the key words.
Is it usefull for Java programmers, Developers and architects because all need to underrstand the fundamentals.
One wrong answer during the interview and it is game over
I do not think that is completely true. In my view if you do not answer questions on the core concept then the game could be over but not if you get a very uncommon question. For example if you take design patterns, some are more popular than the others e.g. singleton, factory etc. But not many of us have used a vistor pattern. If you are asked a question on a visitor pattern you could honestly say that you have heard of it but not used it and suggest that you have used singleton, factory, decorator, proxy, strategy etc. If you do not suggest this the interviewer might think that you do not know design patterns at all. Inteview is not only all about the employer assessing your skills through questions but also about you selling your strengths and accomplishments.