Rubrik Interview Questions
& Process

Applied via a recruiter, the whole thing took about three weeks. Interviewed at Rubrik and it was a terrible experience. Got feedback for my second-round technical interview and it was negative. I want to share my experience. My second-round interview was scheduled on Thursday, 11th November, from 3:00 PM to 3:45 PM with Shahroz Beig. The interviewer seemed rushed. He asked me to write a trigger with no scenario or context. When I asked for more details, he told me to come up with a scenario myself and write the code. I asked follow-up questions about whether he wanted me to use a specific framework, but he wouldn't say. He seemed distracted, like he was on another call, and mentioned another meeting. The interview ended in 25 minutes while I was still coding, without a proper closing. Overall, my second-round experience was really disappointing and I don't think the evaluation was fair. The HR team later contacted me, apologized, and said they couldn't proceed because I have a six-month notice period. My profile was rejected due to these interview issues.

Had a screening with the recruiter where they asked about my experience and some technical questions. Then there was a technical interview panel and a managerial round. Standard questions testing behavioral and technical skills, including networking, past experience, and Linux troubleshooting. The interview went well but then they ghosted me. This happened because the recruiters left the company. A month later, another recruiter reached out and asked me the same questions the first recruiter did. Very unprofessional and a waste of time.

The interview process had 5 rounds in total, with 2 screening rounds initially, followed by 3 onsite interviews. The onsite interviews included a multithreading round focused on designing an atomic stack using a linked list node, and a coding round where I was asked to create a random number generator for a given range (x,y) using an array and a custom shuffle function. Another onsite round involved BST implementation with inorder traversal, alongside memory management, systems concepts, and an easy LeetCode problem about overlapping intervals. There was also a behavioral interview that was mostly resume and background-focused, without specific questions. Unfortunately, I was rejected, possibly due to weaker technical performance in the final rounds, although the HR and team were pleasant to interact with. The hiring bar seems quite high.

First, a recruiter coordinator will call you to get your expectations and notice period details. Then, you'll have an interview with the Manager, whose body language suggests they're done with the organization. This interview won't be about onboarding you, but rather questioning why you'd even want to join. After that, there's a sourcing round. The expectation here is to use keywords that the hiring manager has in mind, not necessarily what the job description says. Essentially, someone working internally who knows their JD and the actual search isn't supposed to match would be the right fit for this role.