I applied to Rubrik about six months before finally hearing back from a recruiter. While I appreciated the outreach, the initial screening call felt perfunctory, as if the recruiter was simply going through the motions rather than genuinely interested in my experience or fit for the role. The conversation came across as detached and mechanical, leaving the impression that this was more about checking a box than actually engaging with a potential candidate.

The technical screening went well, and I was invited to an onsite interview at their Palo Alto headquarters. It’s worth noting that Rubrik does not cover travel expenses (gas, lodging, etc.) for onsite interviews, which means candidates must pay out of pocket. This is something I wish had been communicated more clearly upfront. I spent nearly $300 on this trip to Palo Alto.

During the onsite, I met with four engineers. Most of them were professional and respectful, but one interviewer’s tone and approach felt condescending and unnecessarily cold. It stood out as unprofessional, especially given the company’s reputation.

After the interviews, I waited nearly three weeks with no updates. Eventually, I reached out to the recruiter directly via phone after my follow-up email was not replied to. Only then was I informed that the position had already been filled.

Overall, the process left me disappointed. For a company as established and respected as Rubrik, I expected more transparency, support, communication, and basic respect for candidates’ time and effort. I hope they take steps to improve the candidate experience moving forward. A simple courtesy email is enough.

Questions involved low-level design, concurrency, and memory management. Examples:

• Implement an atomic queue with a custom lock.
• Implement an asynchronous notification scheduler.
• Implement a function to replicate large binaries with limited memory.