3 ms·
This data is presented in a really frustrating way. First, I suspect (but I'm not certain) most companies do it as X% of salary. So I have no idea if I'm looki
by morelisp 4y ago
This data is presented in a really frustrating way.
First, I suspect (but I'm not certain) most companies do it as X% of salary. So I have no idea if I'm looking at truly different on-call policies or rather salary spreads.
Second, there's no associated estimation of how much work "being on-call" is. For us, a small team with SWEs doing voluntary on-call, any out-of-hours page is immediately top priority for work the next day. The person on-call also gets the final say over risky deployments after lunch / on Friday. I know that's not universally true, and we've worked with companies that consider a page a week or even more normal (still without a separate SRE/OpsEng team). If any of us was getting paged once a week, we'd refuse.
- ipsi 4y agoWell, Google is explicitly listed (about halfway down) as paying a percentage, and they're the only ones that are. In my (very limited) experience, it's generally been a flat rate regardless of salary, so I'd go the other way and believe that the majority do, indeed, do that. Your second point is definitely a major concern, though - the author talks about it (calling out Amazon and Twilio as particularly bad), but doesn't provide any sort of hard data on what the workload is like, possibly because it varies heavily even between teams or groups within the same company.
- morelisp 4y agoI know the rate for three other German companies are are percentages. I think time and a half for “activation” is relatively common. I’m less sure about inactive time.