Rubrik | Senior Engineering Manager | March 2026 | Rejected

rubrik logo
rubrik
· Senior Engineering Manager
April 14, 2026 · 1 reads

Summary

I interviewed for a Senior Engineering Manager role at Rubrik, completed three interview rounds focusing on system design and past projects, and was ultimately rejected.

Full Experience

1st round (System Design) - Design a config store that store service config values for A/B testing. System should support 50K/s reads and 5K writes/day. The values are boolean (feature enabled/disabled) and should also support percentage based rollout of features or customerid based rollout.

Gave a solution based on dynamodb, redis cache, bloom filters and a scale set of service hosts. Interviewer was satisfied with solution and the discussion of tradeoffs and non functional requirements.

2nd round (System Design) - You have at your disposal a master node and some spare capacity on a set of (unreliable, crash prone) nodes. Design a system to count the most frequent set of english words across all github repos. You are not allowed to use any managed services though you can install software (e.g. an embeddable db) on the nodes.

Could have done much better in this round, I gave a solution based on min-heap + count-min sketch. There were many follow ups which I bungled to some extent, still the verdict was positive.

3rd round (Past projects) - Problem here is to describe your past project in detail, recruiter will prep you for this and you are supposed to describe something having distributed systems, algorithmic complexity not just CRUD/integration challenges.

I described a production component with a strong distributed systems aspect. Interviewer however could not understand the context and was only listening to some keywords and pattern matching them to other systems. e.g. when I said round robin scheduling he said that's a problem based on the fact that it has issues in other setups (like load balancing http). However, it was apt for our use case. Overall, I felt mixed about my performance in this round. The interviewer did not feel all that knowledgeable to be conducting this round. Advise for this round is to avoid conventional lexicon (like round-robin or at-least once delivery) that interviewer can pattern match to pick apart your project.

Got a rejection email after 2 weeks. Poor experience overall. 3rd round was unmethodical and Recruiter ghosted for 2 weeks before sending a rejection.

Interview Questions (2)

1.

Config Store for Feature Flags

System Design

Design a configuration store that holds service config values for A/B testing. The system must support 50,000 reads per second and 5,000 writes per day. Values are boolean (feature enabled/disabled) and should also support percentage‑based rollout of features or customer‑ID‑based rollout.

2.

Frequent Word Counter across GitHub Repositories

System Design

Given a master node and a pool of unreliable, crash‑prone worker nodes (no managed services allowed, but you may install software such as an embeddable DB), design a system that counts the most frequent English words across all GitHub repositories.

📣 Found this helpful? Please share it with friends who are preparing for interviews!

Discussion (0)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

No comments yet

Be the first to share your thoughts and start the discussion!