Job is Great, Hours are Extremely Alarming - Systems Engineer Epic Employee Review

There are fewer cons, but their severity both outweighs and prevents you from enjoying the pros. Nearing my 1 year mark, it has become clear that the cons are not temporary or anything new. 1. 50-60 hours a week is typical and expected (~10 hours per week day and work ~30% of weekends) 2. High turnover 3. Understaffed 1. The hours are absurd when you take a step back and look at them. Team Leads mostly sympathize, but don't seem to have the power to make any change. If for some reason I did not have to work additional shifts for maintenance windows and upgrades, I would be closer to 45 hours per week. The fact that this work is in addition to normal hours leads to some horrifying statistics: I have worked more weekend days than vacation days, sick days, and holidays combined. This means that I have worked more full days than someone who only works weekdays but never has time off. I typically work 10-11 hours on each weekday since getting to a full customer load, and yes I have voiced my concern/displeasure to my TL. It becomes painfully obvious how bad the hours are when you go to and from work in the dark even during summer. Note that salaried employees only get paid for 40 hours a week, so nearly a third of what I do is free work. 2. The hours are pretty standard on my team except for higher level management (TL's TL). As a result it is no surprise that more than half of my team has left the company or moved to a different role in the last year. The job doesn't allow you to have any sort of life outside work- social, family, or otherwise. The portion of my team that left was overwhelmingly higher tenure employees, which can move to new jobs without looking like quitters. 3. As a result of the massive turnover, teams are perpetually understaffed (to various degrees with my experience likely as an extreme), which leads right back to con #1.