Rubrik SDE-2 System Coding Interview Experience and Concurrency Question
Interview Experience
Hi all, I interviewd for Rubrik recently for SDE-2 role. My first round was System coding in this post will share the question and the solve which i gave. Interviewer was not supportive even my soluti
Full Details
Hi all, I interviewd for Rubrik recently for SDE-2 role. My first round was System coding in this post will share the question and the solve which i gave. Interviewer was not supportive even my solution was correct (accroding to AI tools from which i cross-checked) feeback was
Rejected which i think was not fair evaluation. Interviwer seemed arrogant and i think needed only his solution.
Three kinds of threads share access to a singly-linked list: searchers, inserters and deleters. - Searchers merely examine the list; hence they can execute concurrently with each other. - Inserters add new items to the end of the list; insertions must be mutually ex-clusive to preclude two inserters from inserting new items at about the same time. However, one insert can proceed in parallel with any number of searches. - Finally, deleters remove items from any-where in the list. At most one deleter process can access the list at a time, and deletion must also be mutually exclusive with searches and insertions.
public class Test1 { public Semaphore deleteSemaphore = new Semaphore(2); public Semaphore insertSemaphore = new Semaphore(1); public Integer readCount = 0; public ReentrantLock lock = new ReentrantLock(); public void search(){ lock.lock(); if(readCount == 0){ deleteSemaphore.acquire(1); } readCount ++; lock.unlock(); // read happening lock.lock(); readCount --; if(readCount == 0 ){ deleteSemaphore.release(1); } lock.unlock(); } public void insert(){ deleteSemaphore.acquire(1); insertSemaphore.acquire(1); //insert happening deleteSemaphore.release(1); insertSemaphore.release(1); } public void delete(){ deleteSemaphore.acquire(2); //delete happening deleteSemaphore.release(2); } }
Like the post if it helped you. Will share my resources to prepare for system coding round which i referred in another seperate post, after 50 likes on this.
About This Question
This is a candidate experience report from a rubrik interview for a swe role during the coding round reported in 2026.
It covers the following topics: Os, Concurrency, Linked List .
Topics
More Rubrik Interview Questions
About Rubrik Interview Reports
This question was reported by a candidate who interviewed at Rubrik. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Rubrik are the higher-signal extractions to take from this report.
For broader preparation context, the Rubrik interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Rubrik reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Rubrik Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Rubrik reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.