Open In App

Delhivery Interview Experience for SDE-1

Last Updated : 27 Feb, 2023
Improve
Improve
Like Article
Like
Save
Share
Report

About Delhivery 

Delhivery Private Limited is one the largest and most profitable logistics companies in India. It primarily focuses on digital commerce. It was established in May 2011. Its first two centers were in Delhi and Gurgaon. From there onwards, it grew to become a multi-million dollar company and now servers 12000 pin codes in 1200 cities. It handles over 10 million orders per month and employs about 15000 professionals.

Shortlisting

I applied via referral. My resume was shortlisted by Delhivery and I got a call from their HR. She told me that there would be 3 rounds of interviews, 2 technical and 1 HR.

All the rounds were conducted remotely.

Round 1 : (Online Technical Interview)

Since there were no coding rounds before this as is usually the case with SDE-1 roles, the technical interview went on for more than 2 hours. The interviewer was super friendly and he asked me about my background, and my current company and then we had a detailed discussion on my projects. He asked me about the challenges that I had faced during developing these projects and how I overcame them. Also, he asked a bit about my current project. This continued for half an hour and then he jumped straight onto coding questions. This was done on the Codepair platform. I was asked a total of 5 questions on Data Structures & Algorithms (one by one) over the next 2 hours, and I was asked to code out a proper solution covering all the edge cases. I could use any language of my choice to solve these problems. (Please note I am not going to divulge the exact questions as I am not allowed to).

First up was an easy String problem which I was able to solve within 10 mins. Next, he gave me a problem on Array which was a medium-level problem. It took me some time to figure out the optimal solution. I discussed the approach first and then coded it on the platform once the interviewer was okay with it. There was a follow-up question to this, which turned the problem into a hard-level problem.

It was a dynamic programming problem and I solved it optimally with full working code. The interviewer was satisfied and moved on with the next problem. This time, he gave me a medium-level yet famous problem on trees and I came up with the solution pretty fast. There was another follow-up question to this problem which was also a medium-hard problem.

I coded both solutions and then he asked me if I had any questions for him. I asked him about the company, my role if selected, and the tech stack they use. The interviewer answered all my questions very meticulously. By the end of the interview, I was exhausted, but at the same time feeling pretty satisfied to be able to solve all the problems as they were of quite a good standard.

Round 2: (Technical + Behavioural Interview)

Later in the day, HR called me up to inform me that my feedback from the first round was positive and that they would like to schedule another round of interviews on that same day. The interviewer was a senior engineer of Delhivery and he asked me a few questions on low-level design and then asked me to figure out an optimal solution for one module which turned into an algorithmic question. This was pretty similar to my Juspay Technical Interview Experience. In between, I was asked a lot of behavioral questions like — How I would act in a given situation, etc. which is pretty similar to Amazon behavioral questions. Next, I was asked a puzzle which I found a little tough initially but was able to crack eventually. In the end, the interviewer explained to me the kind of work Delhivery does and what to expect from them.

Round 3: HR

After a few days, I got a call from HR informing me that I am selected for the role and would like to roll out an offer to me after having some formal discussions.

The overall experience was pretty nice and the questions were of a pretty good standard. If you are reading this, and have an interview with them in some day’s time, my tip would be to ensure handling all the edge cases before you submit your code to the interviewer and practice more algorithmic problems.

Hope it helps.


Like Article
Suggest improvement
Share your thoughts in the comments

Similar Reads