Pros
Great and approachable management for the most part. Reggie and rest of executives and directors are great and passionate. This may depend on the group and location you work with, but my experience is that managers are very open, transparent and approachable. Good benefits and pay, at least in the tech side of things. Cvent is by far the leader in the space, so pretty secure company to work for. Interesting products and potential for future growth. They're a selling machine. Great culture and friendly people.
Cons
As the company has grown significantly over the past 3 years, it has doubled in size practically, increasingly "the process" is becoming more important than building great products to serve customers. Everything revolves around "metrics" and about making sprints and deliverables look good to upper management and creating proper tickets and following flows and alike. You spend so much time in planning meetings and just doing process related activities, yet you're expected to still meet your commitments and perform. There is only one hard problem in computer science... Timesheets! The timesheet application we use is terrible. Technical decisions seem to be made by a handful of people at the top and the approach is very top down. Some of the people use appeal to (their own) authority to validate technical decisions rather than give logical reasons why things are done a certain way. A lot of technical attitude and approach is very much "old school enterprise-y". You'll see old style Java and .NET everywhere. The company does not really enable teams to dictate their own approaches or provide them with the tools and power to research different technologies. There is not a lot of room for exploration outside of the core R&D team which seems very narrow minded. Without going into too much details, similarly some of the the technical architecture, organization and and some of the internal tooling is old and the approach and process taken is slow, which has actual productivity and developer experience implications. Some of the tools we use internally have reached or are approaching EOL, yet we still haven't migrated to newer versions. A lot of time and resources are spend building things in-house that are not part of the core business and when significantly better and relatively cheap solutions are available from 3rd parties that have already solved the problem properly.