Rakuten logo

Rakuten Devops Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 15 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Rakuten.

Showing 3 of 15
Rakuten logo
Rakuten

DevOps Engineer

Engineering · a year ago

Senior Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Background check Offer
Interview formats
Technical Behavioral Coding System Design

Started with a recruiter call for initial screening. Then there were two tech rounds. The first tech round covered cloud, DevOps, Linux, and automation. The second tech round focused on my previous projects and was a general chat with an experienced person, with some basic questions about my education and career. The manager was present but quiet. The fourth round was with a director from Japan who asked about job changes, managing leaves, Japanese work culture, work pressures, and some networking concepts. HR then called, confirmed selection, and discussed HR aspects, also asking for counter offers. They said an offer would come in 2 hours. Later, HR called again asking me to interview with a different team that had more budget and could offer more than my counter. They assured me that if I didn't clear that round or like the tech stack, I'd still get the offer from the original project. The interview with the new project team was unprofessional, focusing heavily on Linux and core networking, and their current processes, rather than my expertise. It felt like a process to not select me. Afterward, HR avoided giving feedback or further steps, causing a two-week delay. HR was unreachable and kept postponing. Eventually, HR stated the old project manager had no budget and chose someone else, and the new project also closed its position. They wasted my time with lies and false expectations. HR blamed the hiring manager, but ultimately, my time was wasted. The interview process lacked professionalism, and I wouldn't trust Rakuten even with an offer.

Confirmed questions2 questions
  • How do you manage your leaves?
  • Could you explain the complete lifecycle for building and deploying an application?
Rakuten logo
Rakuten

Devops Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 2 rounds
Interview process
Take home Technical screen Onsite Offer
Interview formats
Technical Behavioral

First, there was a code test. Then, there were 2 rounds of interviews. After that, I got an offer letter. The first interview had tech problems, and they weren't too hard. The second interview was about culture fit, which I learned a lot from. The hr person was very good and positive.

Confirmed questions1 question
  • What is the difference between Java and Python?
Rakuten logo
Rakuten

Devops Engineer

Engineering

Mid Average Negative experience No offer 2 rounds
Interview process
Technical screen Phone screen
Interview formats
Technical Behavioral

The first round was a general tech screen, it was pretty chill and they gave me good feedback that same day. I didn't make it through the second round because I was a bit off from what they were looking for. The second round questions were super broad and not very specific. I had to figure out how to structure my answers first, which made it tough to be brief and to the point. Oh, and they also asked for proof of English skills, like a TOEIC score of 860 or higher.

Confirmed questions2 questions
  • What are the methods for monitoring a MySQL database?
  • Describe the process for upgrading an on-premise Kubernetes cluster.

Rakuten Devops Engineer Interview Questions

Quoted word for word from Rakuten interview reports.

How would you explain the kernel option used to prevent SYN flood attacks?

Read reports

Can you explain Kubernetes pods and networking concepts?

Read report

In the second round, which was the worst, two interviewers from the US office, one quite rude, joined for a short time. They asked some basic Kubernetes questions and then posed a strange question: 'How many soccer balls are there in the world?'

Read report

Could you explain the complete lifecycle for building and deploying an application?

Read report

Formats, difficulty and experience

Across all 15 Rakuten interview reports.

Interview formats

Technical 54%
Behavioral 22%
Coding 18%
Other 4%
System Design 2%

Interview difficulty

Easy 6.7%
Average 73.3%
Difficult 20%

Candidate experience

Negative 46.7%
Positive 33.3%
Neutral 20%