The interview process was very smooth. The recruiters followed up and tried to match your requirements as much as they could.

The process involved two telephonic interviews:

• First, with a junior developer.
• Second, with a developer of the same level.

The telephonic interviews were mostly LeetCode Easy/Medium, focusing on arrays. They also checked the breadth of your knowledge, such as Java collections classes (ArrayList vs. Vector), Hashtables, Java multithreading, and how you handled memory leaks and garbage collection in Java.

The onsite interview consisted of four rounds taken by principal engineers: a manager round, system design, coding, and a data structures and algorithms round.

The interview questions were pretty unclear and were not too difficult or easy. They just wanted you to answer what they had in mind, which made the process quite unclear.

The DS/Algo round was similar to LeetCode or Cracking the Coding Interview. For system design, you need to know basics like consistent hashing, CAP theorem, caching, microservices, and distributed system concepts.

The manager asked too many behavioral questions for which you should have good answers ready (e.g., weakness, accomplishment, tough decision, team conflict). He also asked some technical questions but expected answers in a non-technical way. For solving the string "a+b*c", he expected some weird state machine explanation.

The recruiter got back to you with the result within two working days.

Java multithreading/concurrency, garbage collection, Java collections concepts, hashtables, CAP theorem, consistent hashing.

• Find the max contiguous sum in an array with positive and negative integers.
• Merge two sorted arrays with duplicates.
• Implement consistent hashing using maps.
• Get the 25% of N repeating integers in a sorted array.
• Design a common chat window where all users can chat simultaneously (REST API, etc.).