Pros
Unlimited vacation is nice but only useful if you plan your life 3+ months at a time. There are some good people but there should be in a company of this size.
Cons
Code base is a mess. System architecture is a mess. Not much uniformity in environments. How do you feel about massive monolithic classes with 30k+ lines of code and multiple methods with thousands of lines each? Data storage footprint is insane. Related data is stored (and modified *facepalm*) between elastic AND sql. Devs shouldn't have to wonder which of the multiple copies of data is the right one to use. Caching is a joke. They have Redis but don't fall for it. In memory cache management across multiple service instances where the developer has the choice to pull from the cache OR from the database makes for really difficult data access and ya know, data integrity. Every problem seems to be solved by adding more logic or scripting instead of considering that maybe the path they're going down should be re-evaluated. Architecture team is incredibly difficult to deal with. They don't lead and inspire. They don't even set relevant standards (hence the messy code). They do think pretty highly of themselves and are known for being difficult to communicate with. Claims to be SaFE Agile but in reality is more like 4 waterfall cycles a year. Super high level estimates done by one person are treated like the word of god. When team estimates come in higher, teams have to justify their numbers and can get talked into lower numbers seemingly because product has already set their expectations based on the high level estimates. Deploying to QA requires a person to do manual things, usually for multiple hours or more. Its 2018, time to get on the continuous delivery bandwagon. The benefits are very documented at this point. They embrace new technology but then use the tech is unintended or misguided ways. You have a nuget serer, use it to resolve your build dependencies! It's not just a packager for chocolaty! "We're moving away from SQL" is often heard from architecture and the management team. Huge red flag here. Sure, there's plenty of use cases for NoSQL databases but that doesn't mean the use cases for a relational database go away. If your SQL database is too slow perhaps it's the way it was implemented. "Don't use foreign keys" is the guidance given (although not by everyone, making the mess even more difficult to deal with).