It was one of their data science group. Initially, when the interviewer asked a question on LRU cache design, I solved it using DS, as I assumed the interviewer was expecting the underlying data structure of how a cache would work. I explained it using a doubly linked list and hashmap and coded it – running, neat code with all the methods properly explained and taking care of all edge cases.
Guess what? When he asked me where an interface was, I said we could have one, and I would rather make it an abstract class. It would have a few methods different for the eviction policy and a few common methods.
He didn't even ask me the logic of what I did, since he had no ability to understand the DS or even bothered with what I wrote. He was not even there when I was doing the question, and not one review question on my data structure that I used.
Then he gave me a design question where I wrote two service classes, basic data models, customized exception handling, one server all in one, HR. Checked it out on Git and given it to him.
Basically, I felt they were not technical enough to take your interview. If there was a negative button, I would have given them.
LRU cache design (they were not expecting any DS).
Parking Lot
The following metrics were computed from 1 interview experience for the Rakuten Senior Software Engineer Lead role in India.
Rakuten's interview process for their Senior Software Engineer Lead roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Rakuten's Senior Software Engineer Lead interview process in India.