The phone interview focused on specific Java/J2EE technologies.

Key questions included:

• What is the difference between an interface and an abstract class?
• Implement the Fibonacci series. Can you implement it using recursion? Which method is more efficient, and why?
• What are the steps involved in creating a complete workflow of a module in Spring and Hibernate?
• What is dependency injection? Why is it beneficial?
• Explain the many-to-many mapping concept using Hibernate.
• Write a query to find duplicates.

The 1:1 interview consisted of three rounds:

1. Given an Employee class and a Dept class, provide a complete design and implementation to retrieve all employees grouped by departments.

   • This round revisited many-to-many mapping with Spring injections. They also assessed the reasoning behind choosing specific data structures.

2. The second round centered on the Producer-Consumer problem and involved various threading concepts.

3. The third round focused on design and performance-oriented thinking. For example, if you had a 10GB text file and needed to collect a specific string pattern to store in a database, what would be the most efficient approach?

Advice: Be proficient in Collections, Threads, and performance-related questions.

The work culture is good but hectic. Agile and Scrum methodologies are followed, with stringent deadlines. Colleagues are cooperative, but one needs significant energy to navigate the gigantic codebase and the somewhat complicated procedures for building and testing. Good luck.

Why don't constructors return any value?

What problem did Java face in returning a value from constructors?

Give an implementation of the Moon in the solar system.