Commvault Systems Interview Experience for SDE
Interview Experience
Interview RoundsRound 1: Online Coding Test (Hosted ongeeekAssess)MCQ: (Around 25 – 30)OSDBMSCNC++Problem List:Longest Palindromic SubstringMin Cost Path | DP-6Jump GameRo...
Full Details
Interview Rounds
Round 1 Online Coding Test (Hosted on geeekAssess)
MCQ: (Around 25 – 30) OS DBMS CN C++ Problem List: Longest Palindromic Substring Min Cost Path | DP-6 Jump Game
Round 2 Project Round (~8hrs coding) We were given access to Remove VM one day before. On the day of the assessment, we were asked to create a File Manager with features like creating, reading, updating, deleting, list files in a directory, batch operations, creating soft/hard links, and managing versions of the files (version control). We were provided with a mentor, Initially, we had to prepare the design and discuss it with the mentor (~30 mins). After he approves the design we can start coding, the mentor takes status every 30 mins and if he finds that you have made no progress, he will politely ask you to leave, don’t worry that’s the case when you’ll be absolutely doing nothing. If you’re stuck you can discuss it with your mentor, they are very helpful.
Round 3 Interview Round (2.5hrs) At Commvault you can expect to get roasted on OS. OS is a must for Commvault, I was asked about concurrency control (not directly they will tell a story and you have to solve the issues in the story), threads, and other topics. Then we discussed DBMS, serialization, performance, transactions, and ACID properties. After DBMS, we moved to the DSA part, where I was given 2 – 3 problems: Binary Tree Maximum Path Sum, Mirror view of the tree, and a medium dp question (I don’t remember). Then we discussed CN, different layers, functions of them, and sockets. At last, we talked about my projects. It was an in-depth analysis of my understanding and I really enjoyed the process. They are very polite and helpful. I was also asked a puzzle before the conversation ended.
Round 4 HR Round The team asked to share our experience and congratulated us.
About This Question
This is a candidate experience report from a commvault interview for a swe role during the recruiter round reported in 2025.
It covers the following topics: Trees, Strings, Dynamic Programming, Binary Tree, Os .
Difficulty rating: Hard
Topics
More Commvault Interview Questions
About Commvault Interview Reports
This question was reported by a candidate who interviewed at Commvault. 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 Commvault are the higher-signal extractions to take from this report.
For broader preparation context, the Commvault 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 Commvault reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Commvault 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 Commvault 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.