Microsoft SDE Intern Interview Experience
💼 LTIMindtree Interview Experience (On-Campus) | Fresher | 2026
Salesforce SMTS | Interview Experience | Rejected
JPMC | SDE2 (Associate) - Java Backend - Interview Experience + Compensation
Microsoft - SDE2 - Coding Round
G5 Interview Experience at Rubrik (2025)
Summary
I recently attended G5 Interviews at Rubrik, which included an online coding test, two algorithmic coding rounds (one focused on concurrency), and a hiring manager discussion. I found the questions unique and successfully navigated the rounds.
Full Experience
I recently attended G5 Interviews at Rubrik. Hope it helps.
Experience: Over 1 year of experience at a well-known product-based MNC (not part of FANGG).
There were a total of 5 rounds:
- Online Coding Test
- Algo Coding
- System Coding 1
- System Coding 2
- Hiring Manager (HM)
Mode of Application: recruiter reached out on linkedin
Online Coding Test
Language used - C++
Online Coding test was pretty simple with 1 DSA qs (Easy-Medium BS) and some MCQ related to multithreading and OS
Algo Coding
Language used - C++
If you can solve LC-715, then you can solve that qs easily. I don't remember exact qs, but it was something to do with range modification and range updates. I solved it using Seg tree. There is no language restriction. Interviewer was fully supportive and cooperative.
System Coding 1
Language used - JAVA
This was the best interview round I have ever experienced so far. This round test your multithreading and concurrency area. They provided one coding platform link which has compatibility to run multithreaded code.
I cannot disclose exact Qs due to NDA, but if you know how bookMyShow ticket booking system works, you can arrive to this solution easily.
I took 10min extra for this round as I messed up my code somewhere and because of that, couple of threads were getting executed at a same time. Interviewer was co-operative and told me that a single line of your code change can fix your whole logic. I took 10min more and was able to debug code by myself. The interviewer seemed highly experienced in multithreading and was very particular about my choice of concurrency constructs such as CyclicBarrier, Semaphore, etc....
I got positive feedback from both the rounds and after 4-5 days HR schedule 2 more rounds. System Coding 2 and HM round.
System Coding 2
Language used - C++
This was pretty straight forward round for me. It was a medium to hard LC type problem (not available online). I solved it using multiset, basic interval merge logic combined with line sweep.
I don't remember exact problem but it was greedy problem and require some constructive logic building. Interviewer was pretty supportive. I solved the problem without any hints and my round was finished before 5min of scheduled time.
Hiring Manager (HM)
This was a deep down grill on work experience and also how we handle responsibility. There was also few discussions on projects, but mostly discussion was on experience as well as behavioral qs. This was a decent round.
The best part of whole interview process which I liked the most is - all qs are framed by rubrik internal team itself (this is what I feel). I have solve more than 3000+ qs on various platforms but haven't seen exact same qs (may be they do exist but I have not encountered them).
They not only test your coding ability but also test multithreading and concurrency area, and how well verse you are with handling exceptions.
Please comment if I have missed anything to add.
Cheers!!!
Interview Questions (3)
The round tested multithreading and concurrency. The question was a system coding problem, similar to designing a ticket booking system like BookMyShow, focusing on handling concurrent operations.
This was a medium to hard LeetCode type problem, a greedy problem requiring constructive logic building. I solved it using multiset, basic interval merge logic combined with line sweep.
Preparation Tips
I have solved more than 3000+ questions on various platforms, but noted that Rubrik's questions seemed internally framed and unique, not directly encountered before.