Pros
Most people are friendly and most developers/devops are good at their jobs. There isn't a lot of pettiness or rivalry, communication is usually efficient and people work well with each other. Initiative is valued, if you have an idea on how to fix a problem generally you'll be given time, space and resources to do it your way, from proof-of-concept to production. Thinking outside the box especially is very appreciated. Wide responsibilities. Depending on the project, if you're blocked or getting tunnel-vision on an issue, it's usually possible to focus on something else. There is internal motivation to fix the technical mess, several people are dedicated to replacing or fixing outdated components and there is an ongoing effort for modernization.
Cons
Atrocious off-hours policy, mandatory for some projects. Expect to be on call to fix issues every month, each night for one full week plus one weekend, while still working your normal day hours. Despite official policy, I'm not aware of this toil ever being compensated financially and only sometimes with days off. There is also little acknowledgment or appreciation for this work, or barely even records that it is done, but several zoom calls with management if it's not. For example, you can be called several times per night to fix issues, between midnight and 6 AM, and when working the next morning (yes) you might discover there were no records of that work being done - instead there could be a stern warning about the single time you did not respond at 7 AM. Equally terrible days-off compensation policy. If you canceled weekend plans to be on call, got called once at 3AM on a Saturday and fixed it in 10 minutes, despite the significant inconvenience to your life, management will likely count that as actual 10 minutes of off-hours work. If, after a full week of getting called at nights, you add a day off as compensation, you might find that management inexplicably reduced that to a half day off, with no warning, explanation, apology or alternative compensation. Asking for clarification on this policy can lead to termination. There's a clear recent shift towards an attitude of not questioning things. Opinions can be interpreted as disagreement, which is generally not well-received. You may be told in team calls to not discuss orders. Informal curse-bro work environment that sometimes crosses from endearing to deeply unprofessional. People curse and insult things and each other *a lot*. Expect to hear the R-word (sorry, Glassdoor) in work calls. Despite HR being aware of problems with off-hours policy and other issues, they seem unmotivated to fix them. Several HR projects never make it past the "post about it" stage. A salary transparency initiative was announced over a year ago and never materialized. Mental Health Day was celebrated with an article detailing the signs of a toxic work environment, but ironically only on Linkedin, not shared internally with the company workers. There is currently a lot of technical debt, multiple projects internally competing against each other and there are several strange or redundant design decisions. Most issues are caused by internal tools not communicating properly with each other.