Cvent Software Engineer Interview Questions
& Process

My interview experience at Cvent's Bangalore office was quite disappointing, despite Cvent Gurgaon generally being a good place to work. The process involved three rounds. Round 1 was an online interview, which was okay. They asked some basic Ruby on Rails coding questions, like checking for anagrams, and a simple SQL question about employees and departments. Nothing too out of the ordinary. Round 2 was an onsite interview, and they insisted I travel to the Bangalore office at my own expense. This round was with an architect. He asked a very basic coding question and then asked me to explain the architecture of a past project. The issue wasn't the question itself, but how it was evaluated. Instead of focusing on how the system scales, traffic handling, data flow, or trade-offs, he just kept judging my previous company's architecture, taking notes, and not really exploring my thought process, decisions, or problem-solving skills. This felt unfair. An interview should really assess how a candidate thinks, designs systems, and approaches scalability and constraints. If they wanted a system design discussion, they should have provided a new problem rather than evaluating past decisions made under different organizational constraints. So, if you live far from Bangalore, I wouldn't suggest making the trip for their interviews, as the onsite experience didn't seem worth it.

The Cvent on-campus interview process included an initial round with aptitude, coding, OOPS, and DBMS questions (easy level). This was followed by a second round with one coding question (medium level). Round 3 was an interview round focused on coding questions, general DSA theory, and puzzles. Round 4 was another interview round. Finally, Round 5 was an HR round. After these rounds, we wait for the results.

I went through 2 rounds of a 3-round interview process. This role was for Ruby on Rails, and I had about 2 years of experience. The first round went well, focusing on my introduction and explanations, with the interviewer offering helpful corrections. I felt I led that part of the interview. The second round with a senior Rails developer didn't go as well. They seemed uninterested in my experience and asked about the VS Code file search algorithm, expecting an Elasticsearch-like solution, which I found a bit misguided given the difference between an algorithm and a tool. They also asked some SQL queries.