Learn Java/J2EE core concepts and key areas. With. Java/J2EE Job Interview Companion. By. terney.infomaran. &. terney.infoni. Technical Reviewers. Learn Java/J2EE core concepts and design/coding issues. With. Java/J2EE Job Interview Companion. By. terney.infomaran. Technical Reviewers. Craig Malone. Ebook Java_Programming Exercises. Contribute to ToanPV90/ Java_Programming development by creating an account on GitHub.
|Language:||English, Spanish, Japanese|
|Genre:||Academic & Education|
|Distribution:||Free* [*Registration Required]|
books/Java-J2EE Job Interview Companion, Second Edition terney.infomaran, A. Sivayini (Lulu, ).pdf. Find file Copy path. Fetching contributors. You, too, want to nail the job interview by being prepared to respond to critical interview found Java/J2EE Job Interview Companion - Java Best practices. Java/J2EE Job Interview Companion pdf by Arulkumaran Kumaraswamipillai In stock soon alternatively you go about designing a concise. I am sure will be.
Have you got the time to read 10 or more books and articles to add value prior to the interview? But from an interview perspective it is not possible to brush up on all these books where each book usually has from pages to pages. The interviewer can also use this book to make sure that they hire the right candidate depending on their requirements. This book is also appropriately categorised to enable you to choose the area of interest to you.
The best way to fast track this is to read appropriate technical information and proactively apply these in your work environment. It worked for me and hopefully it will work for you as well.
Two years later I decided to start contracting. Since I started contracting in , my career had a much- needed boost in terms of contract rates, job satisfaction, responsibility etc.
I moved from one contract to another with a view of expanding my skills and increasing my contract rates. In the last 5 years of contracting, I have worked for 5 different organisations both medium and large on 8 different projects. For each contract I held, on average I attended interviews with different companies.
In most cases multiple job offers were made and consequently I was in a position to negotiate my contract rates and also to choose the job I liked based on the type of project, type of organisation, technology used, etc. I have also sat for around 10 technical tests and a few preliminary phone interviews. The success in the interviews did not come easily.
I spent hours prior to each set of interviews wading through various books and articles as a preparation. The motivation for this book was to collate all this information into a single book, which will save me time prior to my interviews but also can benefit others in their interviews.
I am not suggesting that every one should go contracting but by performing well at the interviews you can be in a position to pick the permanent role you like and also be able to negotiate your salary package.
You can discuss with your senior team members about performance issues, transactional issues, threading issues concurrency issues and memory issues. In most of my previous contracts I was in a position to impress my team leads and architects by pinpointing some of the critical performance, memory, transactional and threading issues with the code and subsequently fixing them.
Trust me it is not hard to impress someone if you understand the key areas. For example: Struts action classes are not thread-safe Refer Q in Enterprise section. Chapter highlights Section 1 Interview questions and answers on: Java Fundamentals.
This section also has questions related to new features which were added in J2SE5. This section starts by explaining the difference between AWT and Swing and answers several interesting questions like how does Swing painting happen, how will you improve the painting performance, and explain the Swing event delegation model. This lesson talks about the basics of applets, life cycle of an applet, communication betweens applets and Servlets and finally difference between an applet and application, and whether you can use an applet as an application.
Performance and Memory issues are the most frequently asked questions in all interviews. This section has answers to: How would you improve performance of a Java application? How would you detect and minimize memory leaks in Java? Did you have to use any design patterns in your Java project? Why are you leaving your current position? How do you handle pressure? Do you like or dislike these situations? What past accomplishments gave you satisfaction?
What makes you want to work hard? The author says in the first point "Material rewards such as salary, perks, benefits etc naturally come into play but focus on your achievements or accomplishments rather than on rewards". Behaving right in an interview. Also well covered section where the author gives some useful tips like; Never arrive too late or too early, Firm handshake, maintain eye contact do not make up your answer or try to bluff, You should also ask questions.
Key Points. This section provides one or two lines definitions for major key words. These I think you can and should memorize for your interview. Covers life cycle methods of Servlet, directory structure of a web application, the difference between doGet and doPost, how you make a Servlet thread safe, what is a RequestDispatcher and Servlet clustering and many more.
It covers a wide range of questions in this topic as well.
Refer Q5 in Enterprise section. Why is UML important? Refer Q in Enterprise section. If you happen to be in an interview with an organization facing serious issues with regards to their Java application relating to memory leaks, performance problems or a crashing JVM etc then you are likely to be asked questions on these topics.
These areas are their favourite topics because these are essential to any software development. Some interviewers request you to write a small program during interview or prior to getting to the interview stage.
This is to ascertain that you can code using object oriented concepts and design patterns. So I have included a coding key area to illustrate what you need to look for while coding. Program to interfaces not to implementations: Refer Q08, Q15 in Java section.
Use of relevant design patterns: Refer Q11 in How would you go about… section.
Stay away from hard coding values: Refer Q04 in Java section. My dad keeps telling me to find a permanent job instead of contracting , which in his view provides better job security but I keep telling him that in my view in Information Technology the job security is achieved only by keeping your knowledge and skills sharp and up to date. The 8 contract positions I held over the last 5.
It also kept me motivated since there was always something new to learn in each assignment, and not all companies will appreciate your skills and expertise until you decide to leave. Do the following statements sound familiar to you when you hand in your resignation or decide not to extend your contract after getting another job offer?
What can I do to keep you here? You might even think why you waited so long. The best way to make an impression in any organisations is to understand and proactively apply and resolve the issues relating to the Key Areas discussed in the next section. These key areas are vital for any good software development.
This index will enable you to refer to the questions based on key areas. Also note that each question has an icon next to it to indicate which key area or areas it belongs to.