Waking up a developer should be done as escalation.
If resolving an alert requires to "turn it off and on again" you don't need a developer for that.
Stress and lack of sleep reduces cognitive performance (what you pay for when hire a developer) and kills employee morale.
If you have 2 similar job offers for similar companies, one requires you to be on-call, the other one doesn't... which one would you pick?
If you are having a very bad on-call week and a recruiter reaches to you, you will be more likely to talk to them, or will be more likely to ask for a raise or just quit.
The "skin in the game" argument sucks. Developers are not solely responsible for software quality. Deadlines are often not set by developers.
If resolving an alert requires to "turn it off and on again" you don't need a developer for that.
Stress and lack of sleep reduces cognitive performance (what you pay for when hire a developer) and kills employee morale.
If you have 2 similar job offers for similar companies, one requires you to be on-call, the other one doesn't... which one would you pick?
If you are having a very bad on-call week and a recruiter reaches to you, you will be more likely to talk to them, or will be more likely to ask for a raise or just quit.
The "skin in the game" argument sucks. Developers are not solely responsible for software quality. Deadlines are often not set by developers.