DevRev Field / Application Engineer Interview Questions
& Process

I had an initial call with the recruiter, then two technical interviews, and finally a call with the hiring manager. The recruiter was really good at keeping me updated. The technical interviews were pretty much the same: solve a problem with an engineer and answer some follow-ups. The hiring manager interview was where things went south. He seemed annoyed from the start and asked what problems I was given in the technical rounds, like he doubted I could solve them. It was obvious he didn't rate my experience. When I asked about feedback, he pointed to an earlier question he didn't like my answer to. I tried to add more context, but he just put his head down and scribbled, clearly not wanting to hear it. It put me off so much I withdrew my application. I couldn't see myself working for that kind of leadership. Otherwise, everyone else was great.

The interview process at DevRev was pretty smooth and efficient. It had four rounds in total: two technical rounds, a cultural round, and a founder's round. They were great with scheduling and communication, and I got results within a week for each round. There was a small issue in one of the technical rounds, but they were fair and gave me a third technical round where I did really well. The cultural round was a nice experience where I learned about their values and how they work. The last round with the founder was very insightful, and I got a deep understanding of their vision and product. All in all, it was a positive and helpful experience, and I'm excited about the chance to join such an innovative company.

The interview process started with an online test that had 5 questions. I managed to solve 3 of them. The questions covered API requests, number calculations without carry, binary addition, and SQL queries involving group by and IPv4 addresses. After that, I had to complete a snap-in assignment using DevRev's API. The documentation for snap-ins wasn't very clear, but I managed to build one that creates an issue and updates its priority. Then, I had a technical interview where I was asked for my introduction, details about my internships and projects. I also had to show the snap-in I built, its output, and a working demo, and then create a ticket using it. A coding question about asteroid collision was posed, and I explained a brute force approach. Unfortunately, time ran out before I could finish it. I later found out I was rejected through the college placement department. It seemed like others had foreign interviewers and didn't face coding questions, which made me feel unlucky.