Hello guys, Time is changing and so is Java interviews. Gone are the days, when knowing the difference between String and StringBuffer can help you to go through the second round of interview…

Java Revisited's resource offers insights, tutorials, and resources for Java developers and enthusiasts. Readers can learn about Java programming, JVM internals, and enterprise Java technologies. With articles, tutorials, and code examples, Java Revisited provides  guidance and expertise for mastering the Java language and ecosystem.

Javarevisited

A comprehensive collection of 140 Java interview questions and answers specifically designed for developers with 3-5 years of experience. Covers advanced topics including multithreading and concurrency, JVM internals and garbage collection, Java collections framework, IO/NIO, design patterns, and coding challenges. The questions range from basic concepts to sophisticated topics like volatile variables, memory management, thread safety, and performance optimization. Includes practical coding examples and best practices for writing clean, efficient Java code.

Top 140 Java Interview Questions Answers for 3 to 5 Years Experienced Programmers

Frequently asked Java Interview Questions with Answers for 3 to 5 years experienced developers

1. Multithreading, Concurrency and Thread basics Questions

Wow nice. Even as a long time Java developer, I’d probably fail to answer some of those questions correctly.
Some advice seems outdated, for example to use jodatime should probably be replaced by java.time classes (that more or less evolved from jodatime) and are available since Java 8.
Other answers depend on how much you want to go into detail: take the answer to the “regular expression for a number” as an example. This can be much more tricky than the solution(s) given(taking into account locales that use different notations, scientific representation using exponent etc) - I recently had to deal with this and so checked what regex was given in your answer.
I also never had to use sockets directly, so I would have probably miserably failed that part.
I maybe have some other working background where other tricky questions would matter.
One example would be something like: “You have a large collection of doubles that you need to sum. Does the order of elements influence the result? If so, how to keep the rounding error minimal?” (Sort by absolute amount of numbers first, going from numbers with smaller absolute amount to bigger)
And since you mentioned the equals()/hashCode() contract: there’s another one concerning equals()/compareTo().
<ul>
<li>Why you should not simply use subtraction when implementing compareTo().</li>
<li>What’s special about BigDecimal here? (It doesn’t fulfill the the contract, and two BigDecimal instances representing the same amount do not have to be equal. So prefer using compareTo() over equals() when dealing with BigDecimals unless you know exactly what you are doing.)</li>
</ul>
But it’s a great write up. Thank you!