Real, anonymous reports from people who interviewed for Software Engineer at Druva, newest first and distilled into what to expect across the loop.
I went through a pretty short, demoralizing technical loop. After two online rounds, I finally had a third round in person for a technical discussion. The manager who ran that last session didn’t feel invested in the process at all, and the vibe was basically that the role didn’t really need to be evaluated fairly—like they already assumed they could handle everything themselves.
My process felt structured more than stressful. HR set clear expectations and timelines, and the recruiter side didn’t leave me hanging or waiting around. I still got the sense they were trying to keep things simple, which made the whole experience feel more manageable.
The interview process typically starts with an online test, followed by multiple technical rounds that can include both coding and system design discussions. Candidates often experience a structured flow, but the timeline can vary significantly, with some reporting delays in communication and scheduling.
Candidates can expect a strong emphasis on data structures and algorithms (DSA), with questions covering a wide range of topics including operating systems, networking, and sometimes machine learning concepts. The difficulty of questions tends to escalate throughout the rounds.
In addition to technical evaluations, there are often behavioral or managerial discussions where candidates are asked about their experiences and fit for the team. However, some candidates noted that these rounds can feel abrupt or lack engagement from interviewers.
The level of engagement and professionalism from interviewers can vary, with some candidates reporting positive interactions while others experienced disinterest or an adversarial tone, which negatively impacted their overall impression of the process.
Many candidates expressed frustration with the lack of feedback and closure after interviews, often receiving generic rejection emails without specific reasons for their outcomes. Clear communication throughout the process is a recurring concern.
Candidates should be prepared for a hands-on coding experience that tests their problem-solving skills under time constraints. The coding tasks can range from straightforward algorithm problems to more complex system design challenges.