[encoderer]

Former SV engineering manager and engineering director here:

Have you had a conversation with your skip-level manager? If so, then you are probably right that it's not valued up the chain and you should leave because that is a total shit show that is not the norm.

If you haven't, reach out for time on their calendar, and write down your data points on on-call wake-up rates, total of alarms over time, and let the data make the point that this is not sustainable.

The Director should have some options. How big is the rotation? Is the manager in the rotation themselves? When you're on call are you also expected to contribute story points to the sprint? Why are you not able to solve underlying engineering issues that are causing the SLO violations?

If you came to me, I would be shocked, and immediately make a plan with the engineering manager. Any time a person is woken-up by an alarm it's an incident. There needs to be a response to every incident. There needs to be some serious bar-raising and you can't do it yourself. You need an ally in your management chain and if you don't have one, you're better off transferring teams or companies.

[hinkley]

At some point, OP and their coworkers should be refusing to work on any new code that isn’t at least superficially in the service of reducing these preemption events. If coworkers aren’t concerned about that, it’s probably best to move on.

[saargrin]

any manager who disregards potential churn and/or mass walkouts is probably too obtuse to be talked sense to