Software Developer 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 44% positive. To compare, the company-average is 44.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 36 days to get hired, when considering 175 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 Software Developer according to 175 Glassdoor interviews include:
Skills test: 22%
One on one interview: 17%
Phone interview: 16%
Group panel interview: 10%
Background check: 9%
Presentation: 9%
Personality test: 7%
Drug test: 4%
Other: 3%
IQ intelligence test: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 day. I interviewed at Rakuten (Bengaluru) in Sep 2018
Interview
Round one is Aptitude and basic programming followed by face to face interview round ,All the aptitude questions where solvable but programs where not that easy.required high programming skills.whole interview process completed in one afternoon ,offer letter was rolled out immediately .
amazing place to work,provides free foood
Applied online. Initial screening with the hiring manager. Questions from resume. Technologies used. Java basic questions. Salary expectations. About the role and team. Leetcode question - no coding - just mention the approach. System design question.
Interview questions [1]
Question 1
Leetcode question - no coding - just mention the approach. System design question.
Disorganized, no HR reached out to discuss about the administrative details and salary and benefits, the hiring manager reached out directly, scheduled a meeting and asked about HR questions(visa, RTO etc.)
The hiring manager was late for over 5 mins minutes, no apologies, no greetings. Negative experience
The interview covered Python libraries, networking, and my software engineering experience. While questions were basic, they can be tricky for seniors. Review your definitions alongside your past projects to succeed.