As with almost all software companies 5 years or older - maintenance of legacy stacks, especially after M&A into the bigger firm. Typical problems of a large corporation after going public: re-orgs, middle manager switch-ups all over the place, build this, tear that down, leadership ghosting... it feels like an attempt at generating something amazing from controlled chaos, but in my experience, the outputs from this process are not gratifying to the engineers on the ground who feel push & pulled to deliver the actual results. Biggest con: on-call requirements on a pretty high rotation. I was 24/7 every five weeks, sometimes supporting software I never worked on and had little knowledge of how to fix if something major broke, and they want it fixed NOW. Second biggest con: compensation calculation for remote workers based on Minneapolis cost of living, which is significantly lower than some of the regions they hire remote workers out of (including mine on the West coast). It seems most other major firms adjust their pay rate based on the states they are hiring in, and they need to figure that out or just stop hiring from those locations.
