Druva Interview Experience for Software Engineer
Interview Experience
They conducted 3 roundsCoding roundTechnical InterviewTechno HrRound 1 :There were 3 easy-medium Coding questions and 10 MCQs to solve within 70 min.A question is similar ...
Full Details
They conducted 3 rounds Coding round Technical Interview Techno Hr
Round 1 There were 3 easy-medium Coding questions and 10 MCQs to solve within 70 min. A question is similar to Capitalize the first letter of a sentence. with variations. Next permutation of given number digit. ( Similar to next permutations ) Given a string having words separated by spaces. Print the words with a frequency of character more than 1 then print the word.
Input: “Aabc abcd abdd”
Output :”Aabc abdd” There were 10 MCQs to solve topics including Cs fundamentals from CNS ( DDOS, Man in middle attack, SQL Injection ) Linux ( Difference between > and >> ,Linux chmod command) DBMS ( index) OS ( cache) Around 500 students appeared for the first round, and 14 students were shortlisted for the
next round. The evaluation criteria focus on the correctness of responses and the timeliness of submissions.
Round 2 Technical Interview The interview primarily centered around fundamental concepts, serving as a gauge of your understanding of the subject matter. The process proceeded seamlessly, with the interviewer providing assistance whenever necessary. In instances where you encountered challenges, the interviewer thoughtfully offered hints to guide you toward a solution. Questions asked were : Deadlock vs Livelock. Join 2 tables based on some condition. The interviewer was expecting multiple approaches. Table join. Subqueries. Set operations in SQL. Left outer join diagrammatically using Venn diagram. Table joins. Cross join vs inner join. Implementation of the stack. Discussion regarding stack operation and time complexity. Implementation of min stack. Priority queues time complexity and operations such as Heapify. Rearrange characters in a String such that no two adjacent characters are the same. The interviewer asked if I had any questions to ask. Asking inquiries can demonstrate your interest in the company, which is a good idea. I asked about the following: How Freshmen Fit In: I was curious as to how fresh graduates like myself adapt to the way the business operates. Obtaining Projects I enquired as to how they determine which tasks each employee completes and how they ensure that it matches their qualifications and preferences. What the Business does additionally, I was interested in learning more about the services the business offers to its customers. By asking these questions, I demonstrated not just my enthusiasm for the business but also got valuable knowledge. After Round 2, 5 students were selected.
Round 3 Techno HR The first question was how would you differentiate yourself from others in the office. Describe yourself in one word. Then we moved to the project section. I had 2 internships and did a couple of projects. Questions were asked from that domain. Peer-to-peer communication. WebRtc what is it that we establish and how does the connection is established between peers? Given 3 cities assume it to be Delhi, New York, and Boston and we are sending data from Delhi to New York and from Boston to New York which will reach first and what will happen if the bandwidth is increased or decreased. Discussion around Bandwidth, delay, and latency. TCP vs UDP Connections. When to use TCP and when to use UDP. UDP use cases and why UDP is used for real-time video conferences. UDP in real life. (example I gave was WIFI ) Coming to other projects which was a movie booking website He asked whether the website is hosted or not. (advice: Hosted website is a plus point). How I implemented the functionality of seat booking by the customers. If collisions occur whenever 2 or more people are booking a movie, such that they have selected overlapping seats and the server receives the request at the same instant, how will you resolve it? Who will be getting the seat? Java is an interpreted or compiled language. What is JVM ( I wasn't comfortable in Java, so he didn't ask further questions from Java). Why node Js? Is node js interpreted language or compiled language? How many programs does node js run at one time? Event looping in node js. What is thread, process, and program? How is thread different from the process? What would happen if thousands of requests come to your server at the same time which one will be executed first (given that the arrival time is the same). How will the data remain consistent? Deadlock on the server side. What is JWT? Why is it used for? How you implemented authorization using JWT? Activities that I do that I haven't written in my resume. After this interview, I asked if I had any questions. I asked a few questions that were : About company work culture. Junior-senior relationship. Why use cloud service? Why can't we have a data center? Every question that I asked. I got a detailed answer to my doubts. Out of the 5 selected 2 cleared the interview and I got selected. Tips for the interview : Keep the interview more engaging and do not just consider it a question-answer type thing. Even if you do not know the answer, don’t say I don’t know, instead try one or two times and ask for hints. Even if you didn’t catch the answer, do ask the interviewer for the answer. They just want to check you're never giving up attitude. Before rushing towards telling the solution or anything first understand the question. Always start by telling the brute force approach and then explain the demerits of the approach. It can be time complexity or other than give some optimized solution if present. If there is a more optimized approach, wait till the interviewer asks.
About This Question
This is a candidate experience report from a druva interview for a backend role (new grad level) during the recruiter round reported in 2025.
It covers the following topics: Heap, Strings, Sql, Stack Queue, Networking, Os, Backtracking, Stack .
Difficulty rating: Easy
Topics
More Druva Interview Questions
About Druva Interview Reports
This question was reported by a candidate who interviewed at Druva. 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 Druva are the higher-signal extractions to take from this report.
For broader preparation context, the Druva 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 Druva reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Druva 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 Druva 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.