| I'm probably piling on, but wanted to echo a lot of what's been said. On-call responsibilities are supposed to be a two way street between an employee and an employer. Employers expect employees to be on-call and handle production incidents quickly. That's good for the product. The two way side of it is that employees must have the autonomy and time to fix the root causes of what's paging them to reduce toil. This is the root of "you build it, you own it". "Own" means having autonomy. That kind of engineering work does come at the expense of feature delivery. However, it's also good for the product. Regarding getting paid more for going on-call, from your description, the issue doesn't sound like it's a financial one. If you received $X00 per week more, would that be an acceptable tradeoff for the constant anxiety of your phone paging you at any time or waking up at least once per night? (source: am ex-PagerDuty and founded a company to help drive software ownership, so I've thought a lot about this) |