1. We get paid $70 per weekday and $105 per weekend. I think it’s $140 for public holidays.
2. Eh, it can be a bit annoying at times. It’s pretty easy to swap with people as needed. I believe we’re allowed to opt out of it too, some of the other devs have. Since we’ve started it we’ve tuned our monitoring scripts that false alarms are pretty rare.
3. Any time spent on incidents is rounded up to 15m. Which can make it feel quite unworth it if you get an alert in the middle of the night. Unsurprisingly since they reduced down from an hour it’s taken at least 16m to investigate any alert.
4. We’ve got a decent number of people on rotation that I’m only on call about three weeks a year.
5. Australia

1. $150 per day, call out to office is $275, and the start billing hours as per normal. (AU)

2. Mostly worth it, call outs are rare, but when it rains it pours, so can completely ruin a weekend.

3. Have to be within 1hr of the office, which implies staying sober.

4. 3 people, 1 week rotations.

5. Aus

I am the lead on a team of 5 and technically we have an on call rotation but it is rarely used. In the last 3 years I have been called after hours a total of 4 times and TBH it was usually due to an AWS outage which resulted in us saying well let’s see how long it takes for them to o restore services and then someone run a safety check to make sure shit is normal.

For that I make $120k, have unlimited PTO, and work from home.

Benefits for on-call?

We’re a team of 7 devs and the on-call schedule is 1 dev per week.

We bill 15% of the hourly rate for being on standby and 150% when responding to an incident. Incidents are fairly infrequent, roughly 1 per month.

The company’s based in the EU.

It’s been all over the map during my career. Currently there is no extra for your on call week as was an expectation of employment, but I am only on call one week out of eleven.

My salary, I guess.

Everybody on my team is required to do on-call once they have enough experience (except for the low budget offshore contractors who I wouldn’t trust to do it anyhow…)

We have 2 people on call at a time, 1 primary and one backup. You do a week on backup, then the next week you’re primary.

There’s no set time limits etc, but if you get sucked into some fire, people are reasonable about letting you take some time off the next day or whatever.

All in all, there are very rarely fires that happen inside or outside of normal working hours. Making the whole team be on call helps incentivize everyone to write more stable code since it’s your own ass on the line.

I get nothing. So after a while I told my bosses I would simply stop doing it, since the work to compensate us was still “in progress”. It helped the rest of the team get a free day per on call week, which I guess is something, but still not enough for me personally.

I told them I wasn’t even sure it was legal in my country (Spain) which I guess they didn’t even discuss with legal, or legal didn’t even blink.

Used to be on $140k with on-call paid at $1050 a week (whether called or not). It was later reduced to $550 a week.

In a new job on-call is unpaid but on $230k (plus RSUs)

My employer is suuuper generous. I get a “shout out” on Slack, and if it’s a big incident my slack profile photo appears on a slide at the company all-hands and the CEO graciously extends his thanks. Sometimes he might even say my name!

I’m on call every 3rd week, no cap on time, usually 3 to 5 people (cross teams). base salary $175k US, no RSUs or 401(k).

I want a new job but not getting many resume bites at the moment.

Would love to see some base salaries posted along with the responses. If you’re getting paid shit base maybe this is how they make up for it?

I’m in SRE. No on call benefits at all. Base salary is 175k USD plus 20% annual bonus.

There are a lot of different flavors of being on call.

I’m on call all the time. That just means I might get a phone call at any time and have to help one of our techs on a site. I don’t have to be near the office for that - it’s the knowledge in my head they want.

I charge regular time for it.

We have a team of 6 and rotate on call regularly. I’m in the US and receive no benefit for on call specifically, but other regions do. My salary more than covers the inconvenience though.

Like many others here, at the company I work for you get nothing.

I do one on-call shift as primary per week and one as secondary. I then also cover a week every six weeks or so.

If shit really hits the fan, them work is pretty cool about taking some time back, but we’re far from micromanaged as it is, so we can just kind of make it work.

I’d say an incidency probably occurs on around half of my primary shifts (and I’ve yet to ever do anything as secondary), and nearly always it was something I could resolve within one hour.

Every dev at the company is on the rota once they’ve got a few month’s experience.

Based in the UK.

My developers are only “on call” in the sense that their code supports responders who save lives.

In that context, I maintain the expectation that I might call any of my developers at any time.

That said, I have made that call once ever in the years since I built this team, and it happened to be during business hours anyway.

Officially, I require my team members to take off time to make up for any overtime worked. (Only officially, I guess, since it has not been tested.)

Our flexible work schedule already sets an expectation that someone too tired to work should let their manager know and sleep in and come in later. That has been tested, for various personal reasons. So that would still apply for a late night or early morning incident.

I’m not able to pay an overtime rate, at this time.

I credit my prioritization of graceful rollback for some of the lack of actual on-call calls. But lots of credit is also due to our fantasticly skilled first line responders.