Druva Staff Software Engineer Interview Questions
& Process

So the first part was a chat with the hiring manager. We talked about stuff from my resume and what the job actually involves. They also gave me the lowdown on the tech stack they're using.

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.

So first there was this online MCQ and Programming Round. After that, I was called for a face-to-face interview at the SB Road office in Pune. I'm also prepping for other companies, so I feel pretty solid on Data Structures, Algorithms, and Designing (both High-Level and Low-Level). I had explicitly told the HR that I'm currently using Python and I'm not really up to speed with C. The HR assured me it would be a DS and designing round, and that the interviewers would focus on my logic and approach. However, during the interview, I was asked C questions. I managed to answer most of them, except for the last one, which was algorithm-based. I thought I did well, but then the HR told me I didn't clear the round. I have no idea why! I've asked for feedback and I'm still waiting, but based on what other candidates have said, I'm not expecting much. My observations are: 1. They seem to have a really cool interview process, but in reality, they seem to want candidates who've just memorized everything. They expect everyone to start writing solutions on paper immediately without thinking. 2. The interviewer doesn't seem to consider solutions that aren't exactly what they have in mind. You'll be marked wrong even if you suggest a different, potentially better, approach. 2. Discussing the problem with the interviewer is apparently not a good thing; you lose points for it. (I suspect this might be why I got rejected.)