1. Codelity - 4 questions, 2 hours duration
2. Telephone Screening - 1 hour
3. Onsite Interview - 4-5 hours:
   • Behavioral
   • Quality Assurance
   • OOPS concepts
   • Algorithms
   • Unspecified focus

1. Codelity:

   • 4 questions on Angular, SQL, .NET, and Java. They were moderate; one could do them with minimum preparation.

2. Telephonic Screening:

   • They focused on your Codelity round and your approaches.
   • They asked 2-3 coding questions. The level of these questions depended on the interviewer. For me, I felt 2 of them were easy, and the other took some time, but I could do it.

3. Onsite Interview:

   • Behavioral: Stay cool and answer how you usually handle situations efficiently within your team.
   • Quality Assurance: They focused on your approach to coding to minimize bugs and how efficiently you could code within the deadline.
   • OOPS: Basic Java questions on OOPS concepts. They presented a problem and assessed your approach to achieving it, mostly via whiteboarding. If you are good at OOPS concepts, you are fine.

4. Algorithms:

   • The interviewer asked about Graphs and graph traversing algorithms.
   • He asked me to write pseudocode for a few of them. I missed handling a few edge cases, but he sounded okay.

5. Managerial Round:

   • This is where I think I got screwed up. Another manager joined the interviewer. They didn't let the original interviewer ask any questions and took all the time asking basic questions, which I answered well and was appreciated for.

Got a response from HR stating I am good in algorithms but not in databases and data structures. None of the interview panels asked me any questions regarding databases. I solved my algorithm questions using data structures (Arrays, Queues, Stacks). I don't know how they concluded that I am good in algorithms but not in data structures and databases.