Demandbase Software Engineer Interview Questions
& Process

The interview process at Demandbase India Pvt. Ltd. starts with an online aptitude test that checks logical reasoning, quantitative skills, and basic programming knowledge. If you pass this, you'll go to one or more technical interviews where they'll test your knowledge of data structures, algorithms, programming languages like Python, Java, or C++, and anything specific to the job. You might also have to solve coding problems or talk about your past projects. The last round is an HR interview to see if you're a good cultural fit, how well you communicate, and what your motivation is. They'll probably ask about your background, career plans, and what you know about the company.

A recruiter reached out on LinkedIn for a job opening. The interview process had four rounds in total, with three being technical and one being a mix of technical and managerial. The first round, which was supposed to be about DSA and Java, got rescheduled for the next day because the interviewer was busy. On the rescheduled day, the interviewer was late. He asked one DSA question: 'Minimum steps to reach the target by a Knight,' which I solved using BFS and it passed. The remaining time was spent on Java questions like 'volatile,' 'SOLID,' 'String comparison output,' 'serialization,' 'deserialization,' and the 'transient' keyword. I got a call from the recruiter for the second round after the first one went well. The second round, focused on Java, was also rescheduled for the next day. We started by discussing my current project, the tools I've used, and then moved on to Multithreading, LRUCache, and eviction policy, Distributed cache, design patterns, and SOLID. I felt this discussion went well, although when asked about advanced multithreading, I admitted I hadn't worked on it. I thought the interview went very well and was confident about moving forward. After the interview, I asked about Demandbase's tech stack and current operations, suggesting some improvements. I felt these suggestions might have bothered the interviewer, perhaps because people are comfortable in their routines and don't always like hearing about better ways. I was waiting for the recruiter's call with positive feedback, but since it was Friday, I called him to avoid waiting until Monday. He asked for my name and immediately said the feedback was negative. When I asked for details, he mentioned they expected more on multithreading, system design, and design patterns, even though the interviewer was satisfied with the design part. I felt I answered most questions correctly and wasn't sure about the exact reason for rejection, suspecting my suggestions might have played a role. Looking back, there are a few things that could be improved: the multiple last-minute reschedules, the recruiter's lack of timely communication about the negative feedback, the negative feedback despite my feeling of a positive experience, and the absence of specific reasons for rejection, which leaves me unsure about what exactly went wrong.

A recruiter contacted me. They were flexible on the exact title. The recruiter explained the interview process. The whole thing took about two weeks. There were 6 rounds in total. All rounds focused on Java, Scala, and Spark. The Java questions were quite detailed and of good quality. The first round was an introductory call with the hiring manager. Rounds two through six were all technical. One interviewer in the fourth round was arrogant, trying to show off and even mocking me. When I tried to ask about the work at the end, he said he didn't have time. It made me feel like the company culture might not be great.