Cvent Qa Engineer Interview Questions
& Process

The interview process was a continuous 7-hour marathon from morning to evening, and I wasn't even given food until the very end. The schedule of who I was supposed to meet was quite unclear, and it turned out I ended up talking to 7 different people throughout the day. The interviews involved a round where I had to devise a test strategy and create test cases for a given web page, plus a short 10-minute aptitude test. The rest of the time was spent discussing my past experiences. It was pretty evident that about half of the interviewers were not prepared and didn't really know what questions to ask me. When I did have questions, they could only answer one or two before saying it was time for the next interviewer. Honestly, the whole interview experience was pretty bad. They didn't get back to me for two weeks, so I ended up accepting an offer with another company. If you're considering interviewing with this company, be prepared for a really rough time.

It all kicked off with a quick 10-15 minute chat about the job and if I had other options and how Cvent compared. That call ended with a heads-up about a personality and aptitude test, with more info coming in an email. The email had study resources and a link to take the test within a specific timeframe before another call. I took the test without any feedback, which was a bit nerve-wracking since these tests can be tough. Then, I had another call to go over the job details and tech stack. They also briefly talked about the test, saying there was room for improvement and that it was practice for a live, webcam-based test. A date was set for the live test, and I got more tips and another email with study stuff. On the day of the live test, I logged in, chatted briefly with the recruiter, and then took the test with their camera and mic off. Afterwards, we scheduled a call with a manager for later. The manager call was where the real technical questions started, focusing on API's, HTTP verbs, and tools like Jira, Git, Postman, or ReadyAPI. After that call, the recruiter called to set up an on-site interview, which was supposed to be 2-3 hours within a 5-hour window. I prepped by practicing with Postman and ReadyAPI, testing APIs and documenting test cases. At the on-site, I got a schedule with 5 meetings. I briefly discussed Mac computers and the role but didn't get to show my project. The next meeting was intense, with two interviewers who explained the product and then grilled me on my resume with technical questions about Java, Linux, and JavaScript, which I wasn't fully prepped for. They also asked about SQL, Git, sprints, agile, and Jira. The following meeting was with my potential manager and a colleague via webcam on a TV, focusing more on QA terms, methods, QE software, APIs, and more SQL. The final meeting was informal with the office manager. A few days after the on-site, the recruiter called with an offer but needed to discuss salary. A week later, the salary was presented, which was very competitive, and I accepted. The benefits are great, though hours can be long with some restrictions, and there's an expected annual bonus. The whole process was intense, more so than other interviews, but the compensation makes it worth it, and they value learning and knowledge over degrees.

There was an aptitude round, it had 50 questions in 40 minutes. It included reasoning (non-verbal, verbal), quant, and English. A lot of questions were like "which statement is implicit I or II or both". I tried to keep my mind focused and solved around 40 questions, I think almost 90% were correct. I cleared this first round. The second round was technical aptitude, with questions on SOAP, OSI model, AJAX, and HTTP. I didn't clear this one. Those who passed this round were called to their office 2 days later.