@nq
Engineers at USAA have an extremely cushy job with “work life balance”
Is this supposed to be some sort of "gotcha"? Engineers also work nights and weekends, release code at 10pm or midnight, have on call shifts where they get woken up at 3am and have to jump online at a moment's notice, have their holidays interrupted, etc.
Work-life balance is a pendulum. Sometimes it swings in the direction of life, other times it swings in the direction of work. I've had on call shifts where I literally worked 24 hours straight because most of my team was OOO and I was the only person who was familiar enough with my team's application to support the major incident call.
And I'm not even complaining about that. Some weeks are cushy. Other weeks are straight out of he-l. It just comes with the territory. RTEs and Scrum Masters aren't the ones who get called at 3am when there's an outage, engineers are.
I don't necessarily agree with the OP that RTEs, product owners/managers, or Scrum Masters need to go, because some of them are amazing and truly do keep the train moving so to speak. Many of them deal with the business/leadership politics so the engineers can actually get work done. But USAA would cease to function if there were no engineers to fix production when it goes down, build/implement new apps, handle security incidents, you name it. The same can't be said for Agile-specific roles.