cross-posted from: https://programming.dev/post/2933587

  1. How much extra do you get paid for being on an call rotation?
  2. Is the salary/benefits the same for inconvenience of being on call and working on an incident?
  3. What other rules do you have? Eg. max time working on an incident, rota for highly unsociable hours?
  4. How many people are on the same schedule with you?
  5. Where are you based, EU/US/UK/Canada?
17 points
*

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.

permalink
report
reply
6 points

In Germany you must be able to have an 11h break between shifts by law.

permalink
report
parent
reply
3 points

Same in France

permalink
report
parent
reply
15 points
  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

permalink
report
reply
14 points
*
  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
permalink
report
reply
12 points

$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).

permalink
report
reply
6 points

I worked at a place like that and I ended up saying no to on-call. It depends on your leverage, of course. I was able to tell them “I’m here to fix your mess, not to roll in it.”

permalink
report
parent
reply
6 points

Dang, that’s a big difference from the top post.

permalink
report
parent
reply
5 points
*

Seems like you have some organizational and technical debt in the company that would be worth addressing before agreeing to be on-call

permalink
report
parent
reply
9 points

Benefits for on-call?

permalink
report
reply
5 points

Same boat here haha

permalink
report
parent
reply

Programming

!programming@programming.dev

Create post

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



Community stats

  • 3.2K

    Monthly active users

  • 1.8K

    Posts

  • 30K

    Comments