3 ms·
It's disingenuous (or misinformed) to talk about on-call engineers being annoyed that they're always being woken up by alerts. That's the job. A lot of compani
by peterwwillis 9y ago
It's disingenuous (or misinformed) to talk about on-call engineers being annoyed that they're always being woken up by alerts. That's the job.
A lot of companies mis-manage their ops department and flood the on-call staff with after hours alerts because someone is not fixing the underlying issues. This situation is not unique to Uber. (One alternative is to have a 24/7 NOC staff to deal with recurring alerts (and resolving them using a NOC playbook) and escalate to engineers as necessary, which they may have already been doing)
Reporting on these specific issues in this way makes me wonder what other examples in this article might be commonplace in many industries. There's no easy way to know if Uber is a truly horrible place to work, or if they just dug up every inflammatory remark they could find, and confirmation bias is feeding what we want to be true. Although the executives (like the CTO) definitely aren't afraid to sound like dicks.
- bkor 9y agoOn call doesn't mean you're working. It means you might get a call. The people I know whom were on call weren't paid at 100% but more in the 10-30% range (on top of their normal salary). They might get a call and were paid accordingly. If they'd get too many calls that had an obvious effect on their performance. I completely disagree with your statement that being "on call" means that it is their job to "always being woken up by alerts". If you get so many alerts the company should have someone _working_ (roster, etc), not have people on call!
- peterwwillis 9y agoWe are not in disagreement... you essentially re-stated my comment. But your experience of on-call may be different from mine. (I'm assuming you have also been on-call for a multi-million-dollar 24/7 production service?)