
Rakuten Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 1,203 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 1,203 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Rakuten.
Intern
The interview process consisted of two rounds. The first round involved fundamental questions covering Data Structures and Algorithms (DSA), Object-Oriented Programming (OOPS), and Operating Systems (OS). The second round focused on discussing my personal interests, my preferred technology stack, and my previous projects. No HR round was conducted. The offered stipend was ₹25,000 per month.
- Basic DSA questions
- Basic OOPS questions
- Basic OS questions
Sales
There were quite a few interview rounds, and I got ready using Mikitani-san’s Five Principles to get a better handle on the company culture. The first round was with the regional manager, then rounds two through four were with Japanese managers at HQ, and the last round was with HR. It took about two months, which was a pretty long time.
- Can you introduce yourself?
- What is your knowledge of the industry?
- What is your understanding of the role?
MLOps Engineer
There were way too many rounds, some questions really weren't related to the role or job description at all. The interview had 4 technical interviews split into 2 sessions. 3 of them were okay: 1) general ML stuff verbally, 2) a deep dive into Kubernetes, and 3) system design. But the last one, 4) low-level Python, was weird (you could ask, but it should be in the JD, and these questions had nothing to do with ML or MLOps).
- What are the differences between a Kubernetes Pod and a Container?
Software Engineer
It was a pretty bad experience overall. I had two interviewers, neither of whom were HR. One was easy to talk to, but the other struggled with English, making it hard for them to communicate, to the point I considered switching to Japanese even though that's supposedly the company's internal language. They didn't understand some of my questions even after I rephrased and gave examples. They mostly asked generic behavioral questions they were clearly reading from a script, like 'What inspires you?', 'What makes you happy?', 'What are your ambitions?', and 'What tech do you want to learn?'. Only one question seemed potentially related to my CV, but it might have been a coincidence. They barely discussed their team or the product. I ended up asking them more questions than they asked me, which might be why I didn't move forward. Then they ghosted me, which is the opposite of how it should be. They didn't even send a rejection, even after I followed up, which makes me question how they treat their employees.
- Can you share an example of how you approached performance optimization in your past role?
- What is it that motivates you in your professional life?
- Describe a situation where you had to overcome a specific challenge at work, using the STAR method.
Rakuten Interview Questions
Quoted word for word from Rakuten interview reports.
“Reverse a linked list, but only the first half, using constant extra space.”
Read reports →“Can you count the letters in a given word using Python?”
Read reports →“What is the difference between HTTP 1.0 and HTTP 1.1?”
Read reports →“What are the causes and consequences of overfitting in machine learning models?”
Read reports →“Could you detect and remove a loop in a linked list?”
Read report →“How would you implement a button with its rendering logic in React?”
Read report →“What would you suspect if your colleague's machine learning model has an unusually low error metric?”
Read report →“Can you explain how to deduplicate a table, providing both a basic and an efficient approach?”
Read report →“What's your approach to finding the second largest element in an array?”
Read report →Formats, difficulty and experience
Across all 1,203 Rakuten interview reports.