Rubrik Test Automation Engineer Interview Questions
& Process

The interview process was pretty drawn out, lasting nearly two months over three rounds. I was ultimately rejected, and the reason given was vague, something about the position no longer being available or budget issues. All the interviewers were really nice and kept the conversations flowing, which was a plus. I felt like I connected well in each interview and did well, so the rejection was quite a letdown. From a hiring perspective, it would be better to have faster elimination rounds to avoid wasting everyone's time, both the company's and the candidate's.

HR reached out and set up a phone call where I had to code on Coderpad. Then, I went to the office for three in-person interviews. I was running a bit late and thought the interviewer might be upset, but they were really nice and welcoming. The HR kept in touch throughout. The last interview was with someone from the US on Hangouts, and we coded on Coderpad again. After that, I had a managerial interview back at the office, and I got an offer the same day because I did well in most interviews.

The recruiter reached out about the MTS-SDET role at Rubrik and was helpful, even giving me a list of CS topics to review. The first stage was a screening via hang out on coderpad, where I had 30 minutes to code a solution. I finished the brute force in 10 minutes but the interviewer wanted a more optimized one. I struggled to find the best solution in the remaining 20 minutes, as it required dynamic programming, which is tough to invent on the spot. Then, I got a design followup question about the same program, but the interviewer's explanation was unclear, so I'm unsure about my response. They also asked for all possible test cases for the problem. Because I couldn't nail the optimized solution, I was rejected. The interviewer also seemed to ignore my approach and efforts. The overall experience was okay, but the process felt too rigid. I think I should have gotten a chance for in-person interviews.