There were 2 technical rounds, 1 communication round, and HR.
First technical round was quite easy. They asked questions on core Java and basic questions on Spring, Multithreading, Hibernate, Collections, and Serialization. One can easily crack it.
Second round was quite tough. The interviewer checked deep knowledge about Spring, Hibernate, Web Services, and Concurrency Control.
One thing I did not understand was that they were hiring Java professionals and asking them to work on Salesforce and Hybris when they were hiring Salesforce developers as well at the same time.
Write a method to remove even numbers from a list without using any other collection.
Print a star pattern.
Thread vs. Runnable.
Immutable class.
How does ConcurrentHashMap work?
How to apply security to RESTful web services?
If an application has more write operations and fewer read operations, what will you use: Hibernate or JDBC? Why?
Why should wait() and notify() be called from a synchronized block?
How to implement a second-level cache in Hibernate?
If your application has multiple databases, how many changes would you have to make in Hibernate?
If SOAP is more secure than REST, why do many banking applications still use REST?
The following metrics were computed from 34 interview experiences for the Deloitte Java Developer role in India.
Deloitte's interview process for their Java Developer roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Deloitte's Java Developer interview process in India.