I received a call for an interview after applying through my university career fair.

There were two rounds:

• The first was behavioral.
• The second was technical.

The recruiter shared the material to read for the behavioral round, so it was pretty clear how to approach the interview. The technical round was not very difficult and went smoothly.

The entire process was quite fast; I received an offer within a week after the interview.

Behavioral: Situations:

• When you could not collaborate much with the team.
• When you found a solution, and it was not the actual solution.
• When you were an inspiration to others in or out of the team.
• When you took a risk and what were the implications.
• When you had to rework everything you had done before because of any mistake or error.
• Impact of a particular thing you had done.
• When you completely failed and everything you did was incorrect.

Technical:

• Stack and Queue, Singly Linked List, and Doubly Linked List.
• Exception Types.
• Android App Lifecycle.
• Favorite Design Pattern.
• Design Pattern for a Vending Machine.
• finalize, final, finally.
• Garbage collection in Java.
• Basic MongoDB.
• AJAX vs. SOAP.
• Node.js vs. Java (if Node.js is mentioned on resume).
• Definitions: Stack, Array, Linked List, Queues.
• Abstract vs. Interface.
• Priority Queue: Number of queues required to implement a priority queue.

Coding - Implement any one:

• Linked List using DS.
• Reversing a Linked List.
• Fibonacci.
• String Reverse.
• Bubble Sort.
• Priority Queue.