What is behind the "Strong Knowledge of Multithreading" in Android developer jobs?

Question

Java

It's not often that an ordinary android developer has to write complex multi-threaded code and use the full power of java.util.concurrent .
What does an employer expect to hear about multithreading ownership?
The ability not to load the UI thread or knowledge of the most sophisticated deadlocks and their elimination?

Answer 1

You can do, in a sense, "easier". Take and read the book Java Concurrency In Practice . This is a classic book on multithreading in Java, a must-read. Despite the fact that it was written for Java 6 in the "bearded" 2006, the book still has not lost its relevance. The knowledge from there will more than cover any interview questions, plus you will have a more fundamental understanding of working with threads in Java.

Answer 2

Most likely the following: volatile, atomics, collection synchronization, well, it would not be bad to know about synchronizers (semaphore, barrier, etc.). And the concept of a monitor itself (questions like why wait / notify in an object and not in a thread; waiting stack, etc.)

Answer 3

Everything that is included in Multithreading for android, and solid knowledge of the above. What does an employer expect when asking for solid knowledge of the multiplication table? Obviously, we are talking about the entire table, and not just the even numbers in it.