Policy is 7 day rotation, 24h a day. Must be available to respond within 30m.

1. ~$800 US a week. More if there are holidays. Get paid even if no incidents occur.
2. I get phone and Internet reimbursement that normal devs don't get.
3. There's supposed to be a policy where if I get paged between 10pm and 6am, I don't have to show up to work for 11h. It's not strictly followed in my team, but I always try and get my value from it.
4. 7 others, so I'm on-call for 1 week every 2 months.
5. Job is US based, but company is EU owned.

I'm an SRE though, so our on-call is different from on-call for our product devs.

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.

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.

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.

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.

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

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

I don't do it and we have no expectation of it. A good portion of our infrastructure is self healing and spread across multiple zones which has been enough for us for the past 10 years. The parts that aren't can wait until business hours and clients are aware no work is done outside of them so any fixes or changes wait until the following business day.

You would have to more than double my salary to get me onboard with structuring my personal life around "but what if there's an outage", and even then I probably wouldn't do it lol

I'm on a team of 5 and we don't have an on call rotation since developers are not prod ops. But in a sense we are all on call all the time. The NOC has our phone numbers and if we are needed for something urgent we will get a call or a text for things like helping prod ops troubleshoot an issue if they get stuck. My boss has texted me while I was on vacation before. Usually it's a quick question for something obscure. Once it was an escalation from a senior executive. I don't have to respond if I'm on vacation, but if I'm getting a call they really need help with something. It also is a good opportunity to lay a guilt trip on your boss that results in a few reward points. Never had to actually log into anything though.

We also have BCP, business continuity plan, events. I work for a company that provides a lot of critical infrastructure. If the BCP event is really nasty, like a natural disaster, and our team needs 24/7 representation on the bridge, we take turns and will relieve each other. You won't be expected to help out on a BCP event while on vacation.

Besides BCP we usually have to be available for certain production changes. Like a few months ago I had a DNS and load balancer change done. I wasn't doing the work, but the team making the change wanted me available between 3 and 5 am to validate the change.

If I were paid hourly things would be more formal. I would get overtime(1.5 x hourly rate) + comp time. Since I'm salaried I just sleep in the next day. Our schedules are really flexible. We basically need to be mostly available for meetings for around 4 hours a weekday from late morning to late afternoon, and complete our projects on time. It was like this in the before times. Back then I would go into the office around 11 am for our daily standup. Get lunch with some team mates. Do some afternoon meetings then go home, and do my more focused work at home after dinner time. Most of my team mates did something similar.

Rest of the compensation is your typical American senior software engineer salary with a 10% to 20% bonus, 7 weeks pto, health insurance, life insurance, short term and long term disability insurance, 401k with 6% match, pension, retirement health insurance, pet health insurance, can use the corporate travel agent for personal travel. I actually like this perk a lot. You still pay for personal travel but it means a lot of discounts and upgrades. We also get to keep our various travel points.

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.

$150 per week of on-call.

It’s almost never worth it to me (we almost always get at least 1 call during the week, if not 4-5).

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.