Skip to main content

How can you prepare to clear any Java interview?

 Some Basic to prepare and clear any Java interview



Most of the time interviewer is looking for a candidate who can work with him. The vacancy may be in other teams but they use this parameter to judge. Mostly this article contains general tips. This is for targeted  2 to 6 years experienced candidates.
1. Be honest and don't bluff
Answer what you know, confidently. If you have been asked a question that you don't know, Start by telling "I am not sure, but I think It is .....". Never tell a wrong answer confidently. That will make them doubt your correct answers also or may feel that they were guesses. You can't use this technique for every question, but I would think 25% is a good amount. Most importantly this shows your ability to think and a never die attitude. No one wants to work with people says "I can't do this". Try to do something about all the questions.
2. Be ready to write Code
If you are been asked to write some code, be careful and follow some basic standards. I heard people telling me "I forgot the syntax..." and this for the syntax of a for loop. No one expects you to remember everything but basics like looping, if conditions, main method, exceptions are never to be forgotten. If you did, brush them up. Always write the code with good indentation using lots of white spaces. That might make up for your bad handwriting!!
3. Get ready to explain about your project
As engineers you have to understand the business before you start to code it. So you should be able to explain what is being done in your project. Write down 3-4 lines that will explain the project at a high level. By hearing the lines someone outside your team should get an idea about it. Because we always works inside on features, most of the time it is difficult to frame these. Check your client's internal communications how they are marketing and get some clue from it. Practice what you are going to say with friends make sure you are on to the point.
Once you have explained about the business needs then you will be asked about the technical architecture of the project. You have to be prepared with an architecture diagram that shows how the interaction of components in your project. It don't have to be in any specific UML format but makes sure you can explain stuff relating to the diagram you have drawn. For example, if you are working on a web application show how the data flow from UI to DB. You can show different layers involved, technologies used, etc.. The most important part is you should be clear in your mind about what you are currently working on.
4. Convert arguments to conversation
Even if you know that that person is wrong do not argue and try to continue the conversation saying "Ok, But I am not so sure if that is correct, I will check that out". This keeps the person in good terms. Be an active listener during the interview use reference to your experience when you are answering.
5. Be prepared for the WHY question
Good interviews focus on the question "Why?". It might start with "What" but will end in "Why?". For example in Java typical question would be "What is the difference between String and StringBuffer?". A follow-up why question will be like "Why is String has so-and-so" or "How is it done..?". Be ready to give inside information by answering "How?" and "Why" parts of the question.
6. Tell about your best achievement
During your work, there might be something that you consider as your best achievement. It is important to describe it in such a way that interviewer feels that you have did something extraordinary there. So, prepare a believable story on how your abilities helped you complete that task. It is important to prepare this because it takes time to dig your memory and find situations.
7. Do you have any questions for me?
This question gets repeated in every single interview. Here you don't actually care about the answers; but you should make yourselves look good by asking "smart" questions. This tips will help you.

Comments

Popular posts from this blog

Mastering Java Streams: Best Practices and Common Pitfalls

  Introduction Java Streams, introduced in Java 8, have revolutionized the way developers handle collections and data processing in Java. However, mastering Streams requires understanding not just the syntax but also the best practices and common pitfalls that can arise. In this post, we'll explore advanced tips for working with Java Streams, helping you write more efficient, readable, and maintainable code. Table of Contents Introduction to Java Streams Best Practices for Using Streams Leverage Parallel Streams Wisely Avoid State Mutations in Stream Operations Use Method References for Cleaner Code Short-Circuiting Operations for Efficiency Common Pitfalls in Java Streams Overusing Parallel Streams Modifying Collections During Stream Operations Ignoring Lazy Evaluation Improper Use of Optional with Streams Advanced Stream Operations Grouping and Partitioning Collectors and Custom Collectors FlatMap for Complex Mappings Conclusion 1. Introduction to Java Streams Java Streams provid...

Dealing with Passwords in Java Applications: 5 Best Practices You Should Follow

 In modern Java applications—whether core Java applications or enterprise-level web applications—working with passwords is inevitable. Passwords are sensitive pieces of information, just like Social Security Numbers (SSNs), and if you’re handling real human data in systems such as online banking or healthcare portals, it’s critical to implement best practices for dealing with passwords securely. Below, I’ll share five essential best practices that I’ve learned and recommend for managing passwords, particularly when you are handling authentication and authorization. While these tips are a good starting point, be sure to tailor them to your application’s requirements and security policies. 1) Use SSL/TLS to Transfer Username and Password When users send passwords over the network, it is crucial to use SSL/TLS to encrypt the communication. This ensures that sensitive information is protected from eavesdroppers. Tools like LDAP and Active Directory are commonly used for storing usern...

Fail Fast and Fail Safe Iterator in Java

  The concepts of "fail-safe" and "fail-fast" are often discussed in the context of data structures and algorithms, particularly in Java programming. Let's understand what each concept means: Fail-Safe: Fail-safe refers to the property of a system or data structure that guarantees it will not fail, crash, or produce incorrect results, even when it encounters unexpected inputs or concurrent modifications. In the context of Java collections, a fail-safe iterator is an iterator that does not throw a ConcurrentModificationException if the collection is modified while it's being iterated. Instead, it operates on a copy of the original collection or uses some mechanism to handle concurrent modifications safely. For example, the Iterator returned by HashMap or ConcurrentHashMap in Java is fail-safe. If a collection is modified while an iterator is traversing it, the iterator will continue to operate on the original elements that were present when the iteration ...