Cvent Interview Experience | Set 1 (On-Campus for SDE)
Question Details
Cvent visited our campus. The whole process took 1 day. There are 5 levels to be cleared for getting into cvent. First Level Its a shorlisting of candidates on CGPA basis...
Full Details
Cvent visited our campus. The whole process took 1 day. There are 5 levels to be cleared for getting into cvent. First Level Its a shorlisting of candidates on CGPA basis. For us this criteria is 7 out of 10. Second Level Its a Online MCQ based round. There are 30 questions to be solved in 45 minutes based on (Apti + CS Fundamentals + Code Snippets). There are very few questions which were hard. Most of them belongs to the easy and average category. They shortlisted 25 around candidates for the next level. Third Level It is a online coding round on 'Codility' platform. There is one coding task to be solved in 60 minutes. 'Correctness' of the code was major concern for them not 'Time Complexity'. Code needs to be tested for 'ALL' edge cases. STATEMENT: Complete definition of a function which returns true or false and takes array as an input, If it is possible to sort the array in atmost one swap return true. They selected 11 for the F2F interviews. Fourth Level (F2F Interview I) This round sounds HR cum Technical round to me. It was a 1 hour 30 minutes long interview with average difficulty level. 1)My Interviewer kicks of the interview asking about my internship experience as an ice breaking session. Then he asked me about my projects and technology I worked upon. He seems to be satisfied and happy. 2) Complete story after we enter certain URL on a browser to the point we recieve a HTTP response. (Cache checking+DNS name resolving+Proxy server check+IP routing of request to server and then response back to user.) There were many cross questioning like- -Disscuss both the cases when the result is there in browser cache and if it is not. Same for proxy server. -if all browser have same cache or different. -why do there is a need of DNS name resolving to IP. -Where DNS resides? -some things about ISP and local campus and home networks. -How routing works. 3) He then asked all the front end and back end work to be done at developer level, if you were to develop the gmail.com Login page to the page where we see mails. (I responded with front end validation,cryptography and authentication/authorisation process) 4) He then given me a puzzle suppose you have a cube of side n units made up of 1 unit cubes. How many 1 unit cubes are there whose (3,2,1,no) faces are visible. I need to code for te same as well. 5) He then jumped to DBMS and given me as situation of Employee and Department and asked me to form a real time relation between them. He also asked me about anomalies that can arise in this case. (I proposed am ER Diagram with proper relationship and Anomalies). 6) Why Cvent? What do i know about the company? At the end i asked him few questions about work culture and his own work life balance at cvent. He was very friendly and helpful. Overall the interviewer seems to be happy and satisfied. 4 candidates were shortlisted for the next interview. Fifth Level (F2F Interview II) This round was more into technical as cmpared to previous one. It was a complete 1 hour interactive session + testing of my coding and problem solving skills. He first introduces himself to me and then asked for my introduction in the same manner. He also asked about my previous interview experience. 1) First question is to write a code to reverse a line without reversing its words. For eg: "GEEKS FOR GEEKS PLATFORM !!"--> "!! PLATFORM GEEKS FOR GEEKS". I proposed an O(n)
solution and he seems to be satisfied. He then proposed another solution from his side and ask me to compare both on my own parameters.(I used space and time complexity) https://www.geeksforgeeks.org/dsa/reverse-words-in-a-given-string/ 2) He then asked me to find all intersections between two unsorted arrays. I proposed brute force first O(n^2) and then optimized it to O(NlogN). 3) He asked me a puzzle. Suppose A & B are running on a track with S as a source and D as destination. spped of A, B (Sa<Sb) and distance between D and S is given. If both started from S. B has unusual behaviour that he first runs from S to D and then runs back towards S until he meets A on the way. When he meet A he runs back to D, and keep doing so until A reaches D. I need to calculate the distance traveled by B in this scenario when A reaches D. (I already knew the answer so i asked him for some another question) 4) He then asked me to solve a puzzle of three Jars filled with Red and blue colored balls with 'wrongly' Labelled as RED, BLUE, RED+BLUE. I need to correct the labels with minimum number of picks. The interviewer that i faced this time was also very helpful and interactive. They finally selected 2 students and wind up the whole process. I am glad and would like to thank GeeksforGeeks which proves to best study material for me to achieve success through the interviews.
About This Question
This is a reported interview question from a cvent interview for a frontend role (intern level) during the oa round reported in 2025.
It covers the following topics: Networking, Sql, Arrays, Strings .
Difficulty rating: Easy
Topics
More Cvent Interview Questions
About Cvent Interview Reports
This question was reported by a candidate who interviewed at Cvent. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Cvent are the higher-signal extractions to take from this report.
For broader preparation context, the Cvent interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Cvent reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Cvent Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Cvent reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.