Research Scientist applicants have rated the interview process at Rakuten with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 17% positive. To compare, the company-average is 44.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Research Scientist roles take an average of 26 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at Rakuten overall takes an average of 35 days.
Common stages of the interview process at Rakuten as a Research Scientist according to 6 Glassdoor interviews include:
Background check: 36%
Group panel interview: 18%
Phone interview: 18%
Drug test: 9%
Other: 9%
Presentation: 9%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 6 days. I interviewed at Rakuten (Bengaluru) in Apr 2019
Interview
I have gone through 3 interviews. Starting with a simple coding test. Second round was good conducted by a junior person over telephone. Third round was with a director who has no clue what to ask. He is a Phd holder with limited knowledge in Data Science and good with bluffing and asks silly questions. Totally waste of time to attend. Instead you can spend time watching FC Barcelona replay football match
The process took 2 months. I interviewed at Rakuten
Interview
I had a first screening interview after ~3 weeks, and waited 4 weeks to pass the technical interview which has 2 sessions (each session 1h with a staff member). The way to schedule the interview was particularly not smooth and impractical. I had to exchange by emails to fix the dates and get confirmed.
Interview questions [1]
Question 1
- Implement cross entropy without using defined function in torch
- Implement a data loader of large JSON text database in pytorch
- Questions about: difference between SFO and RL(HF), what consumes more of GPUs during the training of LLMs, and many other questions about parallel training
The interviewers seemed not too knowledgeable about their questions and likely asked an LLM to generate them. The answer that we discussed was divergent and did not convince me. Both interviewers were very unfriendly and not collaborative during the interview.
Long interview process, everything is automated by AI, so no HR to communicate with.
First round with hiring manager - technical discussions, and design choices.
Second round - coding in python loss function, linked list, sampling function, very algorithm related. Bootstraping techniques
Final round - discussion with hiring manager and director
Upon arriving for my interview, I was informed that HR had forgotten to include the interviewer in the meeting invite. They attributed this to a new HR system implemented six months earlier. While the issue was acknowledged, it impacted the overall experience.