Druva Interview Questions
& Process

Druva came to our campus for the SDE role. The first round was an online assessment with core fundamentals and 2 coding questions. Around 113 students made it to the next round, which was an in-person technical interview the very next day at their office. I was asked to introduce myself and then briefly about my projects from my resume. They tested my CS core subjects knowledge with application-based questions on CNS, OS, OOP, DBMS. I also had to write pseudocode for about 6 DSA questions covering sliding window, linked list, basic trees, and arrays, which I think I answered correctly. Despite that, I wasn't selected for the HR round, and only 2 people got selected overall.

It was moderate difficulty, questions were about Systems, Algorithms and pretty decent DSA. OS and Architecture focused questions in beginning and then they moved to Cloud and Machine Learning. Later on they asked about location preference and all

I had an interview with a senior engineer. It began with introductions and some fundamental JavaScript questions covering topics like data types, hoisting, closures, promises, and the event loop, all of which I answered. Next, I was given an array manipulation problem in JavaScript. I managed to solve half of it within the 10-minute time limit before the interviewer moved on. Following that, the interview shifted to React. I answered general React questions well. Then, I was asked to write a `useState` polyfill, which I did, though the interviewer seemed to expect a slightly different implementation. This also had a 10-minute time limit. For the final 10 minutes, the task was to set up a new React project and code a counter component with start, pause, and reset features. I got most of the logic down, but due to the time constraint, I made a small error, and the code didn't function correctly. The interviewer offered no hints and remained silent. Only after I finished and pasted the code into a Google Doc did he point out the single-line mistake. It was quite awkward, and honestly, I feel like tech interviewers should remember that code pairing sessions aren't tests.

I applied for the job through the career page. The whole process took about 3 weeks. A recruiter called me to say my profile was shortlisted and that I seemed like a good fit for the role. Then, I went through 3 technical rounds, and I felt I did okay in each. Each round lasted about an hour and included questions about the role and DSA. The interview experience was pretty good, helping me learn more about the job and the company. Then, out of nowhere, I got an automated email saying my profile wasn't shortlisted, with no explanation. When I followed up with HR, she just said I could try again in the future. I'm leaving this negative review not because I was rejected, but because they didn't provide any feedback on why, and it felt like a waste of my time if they already thought I wasn't the right match, regardless of how I performed.