Top 15 Java Multithreading, Concurrency Interview Questions Answers asked in Investment banks (original) (raw)

Multi-threading and concurrency questions are an essential part of any Java interview. If you are going for any Java interview on any Investment bank like Barclays, Citibank, Morgan Stanley, etc for the Cash Equities Front Office Java Developer position, you can expect a lot of multi-threading interview questions on your way. Multi-threading and concurrency are favorite topics on Investment banking interviews, especially on electronic trading development jobs and they grill candidate on many tricky java thread interview questions. They just want to ensure that the guy has a solid knowledge of multi-threading and concurrent programming in Java because most of them are in the business of performance which provides them a competitive advantage and it's hard to write correct and robust concurrent code.

For example, high volume and low latency Electronic Trading Systems which are used for Direct to Market (DMA) trading are usually concurrent in nature. Most of the time the focus on microsecond latency, that's why a good knowledge of how to use effectively to minimize latency and improve throughput is important.

These are some of my favorite thread interview questions on Java asked on different on a different time. I am not providing an answer to these thread interview questions but I will give you hint whenever possible, some time hint is also enough to answer. I will update the post further with detailed answers just like I did for 10 Singleton interview questions in Java recently.

After the introduction of the concurrency package in JDK 1.5 questions on concurrent utility and concurrent collections were increased like ThreadLocal, BlockingQueue, Counting Semaphore, and ConcurrentHashMap become popular.

The same is true for Java 8 and Java 9, where questions on lambda expression and parallel streams, new fork-join pool, CompletableFuture is also on the rise in 2018 and will remain in 2019. Hence you should prepare well for those topics.

And, if you are preparing for Java interviews then you can also checkout my book Grokking the Java Interview Volume 1 and 2 which covers most of the Java topics including multithreading, concurrency, serialization, classloader, performance and debugging and many more. You can also use code friends20 to get 20% discount now for a limited time.

15 Java Thread Interview Questions with Answers

Anyway, without any further ado, here is my list of some of the frequently asked Java multithreading and concurrency questions from Java developer Interviews on Investment banks e.g. Barclays, Morgan Stanley, Citibank, etc.

1. You have thread T1, T2, and T3, how will you ensure that thread T2 run after T1 and thread T3 run after T2?
This thread interview question is mostly asked in the first round or phone screening round of interviews and the purpose of this multi-threading question is to check whether the candidate is familiar with the concept of the "join" method or not.

The answer to this multithreading question is simple it can be achieved by using the join method of Thread class. If you are not familiar with the join method, please see my post on how to join threads in Java.

2. What is the advantage of a new Lock interface over a synchronized block in Java? You need to implement a high-performance cache which allows multiple readers but the single writer to keep the integrity how will you implement it?
The major advantage of lock interfaces on multi-threaded and concurrent programming is they provide two separate locks for reading and writing which enables you to write high-performance data structures like ConcurrentHashMap and conditional blocking.

This java thread interview question is getting increasingly popular and more and more follow-up questions come based on the answer of the interviewee.

I would strongly suggest reading about Locks before appearing for any Java multi-threading interview because nowadays It's heavily used to build cache for an electronic trading system on client and exchange connectivity space.

And, if you are serious about mastering Java multi-threading and concurrency then I also suggest you take a look at the Java Multithreading, Concurrency, and Performance Optimization course by Michael Pogrebinsky on Udemy. It's an advanced course to become an expert in Multithreading, concurrency, and Parallel programming in Java with a strong emphasis on high performance

How forkjoin pool works in Java

3. What are the differences between the wait and sleep method in Java?
Another frequently asked thread interview question in Java mostly appear in a phone interview. The only major difference is that wait releases the lock or monitor while sleep doesn't release any lock or monitor while waiting.

The wait is used for inter-thread communication while sleep is used to introduce pause on execution. See my post wait vs sleep in Java for more differences
4. Write code to implement a blocking queue in Java?
This is a relatively tough Java multi-threading interview question that serves many purposes, it checks whether a candidate can actually write Java code using thread or not, it sees how good the candidate is at understanding concurrent scenarios and you can ask a lot of follow-up question based upon his code. If he uses the wait() and notify() method to implement blocking queue,

Once the candidate successfully writes it you can ask him to write it again using new Java 5 concurrent classes etc.

5. Write code to solve the Produce consumer problem in Java? (solution)
Similar to the above questions on the thread but more classic in nature, some time interviewer ask to follow up questions How do you solve the producer-consumer problem in Java, well it can be solved in multiple ways, I have shared one way to solve the producer-consumer problem using BlockingQueue in Java, so be prepared for surprises. Sometimes they even ask to implement a solution to the dining philosopher problem as well.

6. Write a program that will result in a deadlock? How will you fix deadlock in Java?
This is my favorite java thread interview question because even though deadlock is quite common while writing a multi-threaded concurrent program many candidates not able to write deadlock-free code and they simply struggle.

Just ask them you have N resources and N threads and to complete an operation you require all resources.

Here N can be replaced with 2 for the simplest case and a higher number to make the question more intimidating. You can further check the Applying Concurrency and Multi-threading to Common Java Patterns course on Pluralsight to learn more about popular concurrency patterns and the right way to use them.

Top 15 Java Multithreading, Concurrency Interview Questions Answers asked in Investment banks

7, What is an atomic operation? What are atomic operations in Java?
Simple java thread interview questions, another follow-up is do you need to synchronize an atomic operation? :) You can read more about java synchronization here.

8. What is a volatile keyword in Java? How to use it? How is it different from the synchronized method in Java?
Thread questions based on a volatile keyword in Java has become more popular after changes made on it on Java 5 and Java memory model. It’s good to prepare well about how volatile variables ensures visibility, ordering, and consistency in a concurrent environment.

9. What is a race condition? How will you find and solve the race conditions?
Another multi-threading question in Java which appear mostly on senior-level interviews. Most interviewer grill on recent race condition you have faced and how did you solve it and sometimes they will write sample code and ask you to detect race condition. See my post on the Race condition in Java for more information.

In my opinion, this is one of the best java thread interview questions and can really test the candidate's experience in solving race condition or writing code which is free of data race or any other race condition.

One of the best books to get the mastery of this topic is "Java Concurrency in Practice by Brian Goetz". If you are thinking that this book is old then think again, it's still relevant in the era of Java 11.

10. How will you take a thread dump in Java? How will you analyze the Thread dump?
In UNIX you can use kill -3 and then thread dump will print on log on windows you can use "CTRL+Break". Rather simple and focus thread interview question but can get tricky if he asks how you analyze it. A thread dump can be useful to analyze deadlock situations as well.

11. Why we call the start() method which in turn calls the run() method, why not we directly call the run() method?
Another classic java multi-threading interview question This was my original doubt when I started programming in the thread. Now days mostly asked in a phone interview or first round of interview at mid and junior-level java interviews.

The answer to this question is that when you call the start() method it creates a new Thread and executes code declared in the run() while directly calling the run() method doesn’t create any new thread and execute code on the same calling thread. Read my post Difference between start and run method in Thread for more details.

difference between start and run method in Java

12. How will you awake a blocked thread in Java?
This is a tricky question on threading, blocking can result in many ways, if the thread is blocked on IO then I don't think there is a way to interrupt the thread, let me know if there is any, on the other hand, if the thread is blocked due to result of calling wait(), sleep(), or join() method you can interrupt the thread and it will awake by throwing InterruptedException. See my post How to deal with blocking methods in Java for more information on handling blocked thread.

13. What is the difference between CyclicBarriar and CountdownLatch in Java? (answer)
New Java thread interview questions mostly to check familiarity with JDK 5 concurrent packages. One difference is that you can reuse CyclicBarrier once the barrier is broken but you can not reuse CountDownLatch. If you want to learn more see Multithreading and Parallel Computing in Java course on Udemy.

14. What is an immutable object? How does it help in writing a concurrent application?
Another classic interview questions on multi-threading, not directly related to the thread but indirectly helps a lot. This java interview question can become more tricky if ask you to write an immutable class or ask you Why String is immutable in Java as a follow-up.

15. What are some common problems you have faced in multi-threading environment? How did you resolve it?
Memory-interference, race conditions, deadlock, livelock, and starvation are an example of some problems comes in multi-threading and concurrent programming. There is no end to a problem if you get it wrong and they will be hard to detect and debug.

This is mostly an experienced-based interview question on a java thread instead of fact-based. You can further see Java Concurrency in Practice Course by Heinz Kabutz for some real-world problems faced in actual high-performance multi-threaded applications.

Java Concurrency in Practice Course by Heinz Kabutz

These were some of my favorite J_ava thread interview questions and mostly asked on Investment banks_. This list is by no means complete so please contribute some of the interesting java thread questions you have faced during the interview.

The purpose of this article is to collect and share great interview questions on the multi-threading concept which not only helps in the interview but opens the door for learning a new threading concept.

Update:

One of the Javarevisited readers, Hemant has contributed some more thread interview questions in Java, though he hasn’t provided answer sand left that job for me, I will certainly do when time allows, just like I have recently updated 10 Singleton interview question in Java with answers.

If you guys know answers to this Java concurrency questions then please post a comment.

Here are his comment “Good questions on multi-threading though you may need to prepare more in order to clear any multi-threading interview, you need to be familiar with the concept of immutability, thread-safety, race condition and many more.

10 or 15 questions is good for the quick recap but you at least need to prepare more than 50 questions on threading and concurrency to perform better on Java interview.

You can find some interesting thread question below which is no doubt highly popular –

  1. Difference between green thread and native thread in Java?

  2. Difference between thread and process? (answer)

  3. What is context switching in multi-threading?

  4. Difference between deadlock and livelock, deadlock, and starvation?

  5. What thread-scheduling algorithm is used in Java?

  6. What is a thread-scheduler in Java?

  7. How do you handle an unhandled exception in the thread?

  8. What is thread-group, why it's advised not to use thread-group in Java?

  9. Why the Executor framework is better than creating and managing thread by the application?

  10. Difference between Executor and Executors in Java? (answer)

  11. How to find which thread is taking maximum CPU in windows and Linux servers?

  12. Difference between virtual thread and normal thread in Java?

Apart from practicing these question answers, more important is to understand the concept behind these multi-threading questions simply mugging the answers of these thread interview questions is not going to help because there would be a lot of follow-ups based on your answer and if you haven't mastered the particular thread topic it would be difficult to answer them.

Other Java Interview Questions on different topics you may like to Explore

Thanks for reading this article so far. If you like these multi-threading and Concurrency Interview questions then please share with your friends and colleagues. If you have any questions or feedback then please drop a note.

P.S. - If you can't solve these questions and looking for online courses to learn Java Multithreading and Concurrency then you can also check out my list of best Concurrency Courses for Java programmers to explore this important topic in depth.

And now, over to you, what was the last question you were asked on Thread or concurrency in Java?