DevOps

1698 readers

2 users here now

DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.

Rules:

Posts must be relevant to DevOps
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be promotional content.

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

[email protected]

What benefits do you get for being on-call? (programming.dev)

submitted 1 year ago by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] Skyzyx 5 points 1 year ago* (last edited 1 year ago)

Based in the US.
Salary employee (overtime doesn't apply).
We embrace "shift-left" methodology, which means that we own our stack, soup-to-nuts.
It makes zero sense for us to build an application, then toss it over the fence to another team that knows nothing about it.
We partner with specialist teams for any skill that we don't have on the team. While many of us have Dev and also Ops skills, we partner (for example) with our SRE team on certain matters. We still own the work, but we "sub-contract" it out to our SRE team.
We devs are on-call, and the SRE team that supports us is also on-call. Both teams get paged for any production incident. Our team is ultimately on-the-hook, but SREs are there to have our backs.
It empowers/enforces us to make sure that we don't ship crap. And if we do, we get paged.
We think about SLIs, SLOs, error budgets, and work to identify trouble spots in the application.

Based on the way you wrote your questions, I sense that your situation is completely different from mine. But we work hard to eliminate silos, eliminate fence-tossing, and partner together with experts to ensure that what we ship is of a high quality so that we don't get paged in the middle of the night. The better we do our daytime jobs, the more we can sleep in the nighttime.