> Imo, having "on call" rotations is a clear red flag and bad software practice that has somehow made it in the mainstream. I thought so too until I gigged for

> Imo, having "on call" rotations is a clear red flag and bad software practice that has somehow made it in the mainstream. I thought so too until I gigged for a SaaS company that absolutely needed it. No, it was not moon-shot rocket control software, but it was a money printer with literally thousands of clients around the globe paying six figures for the service. The on-call SWE duty was not onerous: about 2 hour shifts every 2 months, and your job was to attempt to handle it and then escalate it to staff if you couldn't. There were so many CI tests on the way to production that nothing ever happened, until it did, and then you needed to make sure that money printer go brrr.