On-Call Rotations

Amazing. Any oncall type of work? What if things go down at 3am?

When you get a new job, check if you need to be OnCall if yes then ask for 1 day off after every session of being OnCall to recover, even if no event happened, the psychological burdon.

On-call is not the norm, nor to be expected. I've worked over a dozen jobs easily in this industry and not a single one has had an on-call requirement for any amount of time, let alone throughout the night. This will not be the case as much for ops people, but even then it's possible to find jobs that don't have an on-call requirement. Your mistake is thinking this is expected and putting up with it. Sleep is my most precious asset and to be on call 24/7, even once a month, w

I really hate on-call, sadly in any serious distributed systems used by many customers/running large scale online services on-call is table stakes :|It's not like SWEs are paid by hour. If you are on call for a week every 2-3 months (for example), you could just consider the extra 2 work weeks (assuming 8 hour days for a normal week) of part-time work to be part of your paycheck.Staffing competent people 24x7 is completely impractical in a sufficiently complex system... what you

On-call requires you to more or less not plan anything other than being available for work. Sure most of the time nothing goes wrong--but that isn't the constraint, here. The whole point is that something might go wrong and that the person on call must respond within a given window of time (5-15 minutes, generally). That effectively makes even mundane things like going to the grocery store a potential trade-off in favor of work. I definitely consider every hour of the d

Sounds like your issue is with bad managers and bad companies rather than on-call. There are companies out there that cover what you asked for.

I've been part of an on call rotation at my current job and previous job. Both had the same rules because I and other engineers insisted on it.* You are only on-call for systems you can directly change.* The person who is on call has full flexibility to work on anything that improves the life of the on-call person for that time.* Anything that wakes people up in the middle of the night gets prioritized above new feature work.* There is a pager set of monitors, and a message only

There is at least one big company out there, where every dev is part of what they call the "on call rotation" -- where being "on call" typically means being on pager duty -- without any special compensation for that. The only exemption is if you're working on a project that isn't yet in production. They tell you about it during their recruitment process and they communicate it very clearly: take it or leave it, there are no special cases. It sucks, but a lot of peop

What's expected? As an owner of a software company that requires on-call staff (I'm basically 100% on call all the time): If they did not mention it during the interview, nothing is expected of you on-call. If they bring that up, renegotiate your contract.- How often are folks on-call? How frequently do issues occur at your org?I worked in IT that had a rotation. We'd have 6-8 techs and just rotate weekly. However, issues were infrequent: maybe 1 every 2 weeks. Minor things.

I’m not on call, but when doing interviews I explicitly ask about the on-call setup (if any). The usual setup (for backend engineers) is:- 1 week in-call every 5 to 6 weeks (depending on how many engineers are available for on call)- if you get paged, you need to acknowledge within 10-15 min. Sometimes it’s nothing and you can go back to sleep, but sometimes you may need your laptop to fix things. The point is: you don’t know before hand- it’s paid. In my opinion the money is not worth