4 ms·
I've done a fair bit of on-call during my career, but I wouldn't do it anymore (at least not for any dollar amount a company would likely pay). I value my time
by kelnos 3y ago
I've done a fair bit of on-call during my career, but I wouldn't do it anymore (at least not for any dollar amount a company would likely pay). I value my time outside work -- and my sleep -- too much.
The standard in SV seems to be that on-call is required and uncompensated (some companies will dishonestly try to suggest that your salary is higher than it would be otherwise). This is gross, and we shouldn't stand for it. There are exceptions of course, but even companies I've heard of that compensate for on-call seem to fall far short of what should be expected and required.
On-call should be compensated at a base per-hour rate (outside of 9am-5pm), with an elevated rate for time spent handling an incident if the pager does go off, with a minimum payout of 1 hour of time. It should be opt-in. If not enough people want to do it to get you the coverage you want, raise the rates until your employees feel that the time is worth the money.
It's pretty messed up that OP here is throwing shade at an employee who is balking at this, wanting to put them on a PIP, plus a thinly-veiled suggestion that they're lying about having asked about on-call requirements during their interview process. Bottom line is that they're drastically changing the terms of employment without offering extra compensation, and while in many jurisdictions that's legal, it's nonetheless unethical and disgusting.
- knallfrosch 3y agoOn-call X% (0<X<100), and if you're called: The full 100% and then all the applicable bonuses for night shift and weekend etc.
- morelisp 3y agoIt needs to be be 150% minimum, otherwise they're just paying the same for >40h.
- cj 3y agoI agree if on call is being triggered regularly. I strongly disagree if events that would trigger on call happen rarely (e.g. once per year). Many companies have stable infrastructure but just need the extremely occasional coverage for things that rarely, if ever, happen. I’ve seen people overreact when on call has been introduced, probably from negative experiences at prior jobs. As long as the on call events happen once in a blue moon, I don’t see why anyone would have a major problem with it.
- kelnos 3y agoThat doesn't matter at all to the base rate. Bottom line is that you don't know when that once-in-a-blue-moon page is going to happen, so you still have to curtail your leisure activities in order to be ready. Want to go see a movie? Want to go for a long drive? Want to go on a hike? Want to take your kids (who are young enough to need constant supervision) out somewhere? Want to go anywhere where you don't have cell service? Nope, can't do it. If the company wants me to change how I would otherwise spend my leisure time, they need to pay me for it. So sure, a company fitting your description would only rarely pay out the elevated rate for someone actively handling an incident, but since an employee still has to do the exact same things when not handling an incident (regardless of how often incidents arise), the base rate needs to be there.
- scarecrowbob 3y agoWell, consider that "once in a blue moon" might actually be worse given that a) it is not predictable and b) likely to be less compensated. Like, it doesn't matter if something almost never happens because I'd be "on call" regardless- that ---is--- what it means to be on call. I did that for many years and it didn't matter so much when my kids were little and I didn't want to, like, go to a rave off the grid or perform music over a weekend or go climbing in BFE Utah. But I quit a job that I'd had for almost 10 years because of that fact of the work. After a while it's a really bullshit thing to do to folks. It doesn't matter if I never get called- I still have to be available and that really is something people need to be compensated for.
- nwallin 3y agoThe problem with being on-call isn't that you're working, the problem with being on-call is that you aren't not working. You can't be on-call and go to a place you're not allowed to have your cell phone on. You can't be on-call and drink alcohol. (or other substances of various legalities) You can't be on-call and go camping in a wilderness location that may not have cell coverage. Depending on the circumstances, you may need to lug your work laptop around in your backpack.
- lambdasquirrel 3y agoI see two solutions to the conundrum. At one company where I previously worked, they required that employees receive 2x the time off, if you had to fix or work on anything during off-hours. Another company I’ve been at is pretty strict about not shipping things until they’re ready (but, that company doesn’t hire juniors in engineering). Pick your poison. The fact is that no engineer wants to get paged. But we have to be responsible for our work and our mistakes. That said, I think it’s well understood, the dynamic of pushing rushed work. To which end, you have to construct a system where e.g. product is incentivized to align with engineering on some minimum level of reliability.
- kelnos 3y agoSure, and "constructing that system" should mean paying your employees for non-work-hours work. And even if I never get paged, if I need to be within 15 minutes of a computer with an internet connection at all times, that is going to drastically limit what I can do with my free time. I should be compensated for that. One company I worked at didn't have a formal policy of giving people time off if they got paged, but most/all managers would allow for it. That's nice, I guess, but to me still doesn't cover it. Even if the pager never goes off, the employee has made their off-hours worse (that is, not really off-hours anymore) in order to give the company value. Not compensating them for that is unethical. Just to specifically address one bit: > But we have to be responsible for our work and our mistakes. Absolutely agree. But if you want me to be responsible for my work outside of regular work hours, I expect to be compensated for my time. Also consider that I'm being asked to be responsible for my teammates' work as well; while I do have some influence over the quality of their work, it's far from sufficient to guarantee their work is equivalent in quality to mine (and vice versa).
- karmakaze 3y agoThis is an excellent point. I do recall that did on occasion alter my plans, inappropriately bring my laptop to functions, or limit my alcohol consumption for the evening just-in-case. Fortunately we were given generous on-call compensation even when not paged.
- 3y ago
- andrewaylett 3y agoI much prefer the incentives around time off in lieu for working out of hours, rather than elevated pay. We are paid a base rate just for being on call, it's less than our normal rate and the same for anyone in the company who goes on-call. It's payment for making ourselves available, not for doing any work. If I'm up in the night, I'll want a lie in the next morning.
- kelnos 3y agoGlad you get paid a base rate! A company I worked at (informally, as there was no specific policy) gave people the day off if they got paged overnight and had to do work. That's certainly something. The problem with it being informal is that many employees didn't realize it'd be ok for them to take off the next day, so they didn't. And managers often wouldn't pro-actively offer it. But the question to me is: if I have to wake up at 2am and work for 4 hours, is that "equivalent" to having the next day off? Maybe? But also: maybe not.
- anotherhue 3y agoI find the 'in lieu' method breaks down when one day is not equivalent to another. A Sunday with family that I lose isn't something a Monday on my own can replace. Then again the employer could just let the employee decide which one they want.
- andrewaylett 3y agoThat might be a problem in theory, but it's not been a problem in practice for me. I've been on an on-call rota with my current employer for seven years or so, and it's never happened that I've lost even a significant fraction of a weekend. Stuff tends to break while folk are working and making changes, and I've lost evenings to serious outages. Issues out of hours tend to be solved by a roll-back, or a mitigation (like draining a region) that lets us leave the fix until regular working hours. Probably the most severely interrupted non-working day was when I needed to take an hour between the main couse and pudding one Christmas day, when I was second line on-call and the person who was formally on-call (who doesn't celebrate) needed a second pair of eyes. While the most severely-interrupted working day was probably the one that included this outage: https://medium.com/@SkyscannerEng/how-a-couple-of-characters-brought-down-our-site-356ccaf1fbc3 https://medium.com/@SkyscannerEng/how-a-couple-of-characters.... I'm quite proud of the response to that, especially that we quite carefully and deliberately stopped after one region was back up, running in a degraded state overnight in order to make sure we didn't burn out our teams by trying to do too much out of hours.
- downrightmike 3y agoAKA "How can I squeeze employees even harder rather than paying someone to do the work?"
- jjav 3y agoTo me the most important factor to tolerate on-call duty is that I must have 100% authority to fix the things that would ever make me be paged. Under such an arrangement, I control my destiny (not 100%, but close enough). If I can make the code so robust and so easy to diagnose that I'm very likely to never ever be paged, I'm ok being on call. But if there is some psychopath product manager making engineering decisions above engineering, forcing to increase tech debt constantly, guaranteeing constant outages and thus constant on-call pages then a big fat no. I won't be on call.