I'd personally appreciate if you explained the intention behind asking these questions.
Is this for your personal market-awareness? Or is it part of a survey (community or corporate?)
this post was submitted on 13 Sep 2023
18 points (90.9% liked)
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
- 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.
I was the only data scientist for a while and was on-call every day all the time. No benefits
I don't get anything for being on call, neither I receive anything for working on an accident. Sometimes I am allowed to have extra free time next work day. At the same time, we don't have many accidents and I mostly ignore calls unless it is convenient for me to look up whats going on. There are 2 people, me and my manager.
U.S Remote
$3 an hour, not allowed to move out of phone network
1hr overtime pay if I get a call
Not allowed to get plastered, but not limited on drinking
Only me
Australia
It is a good deal on general days of the year
Ooof, i was reading that thinking you were in a different country to me.
I am on $150 per day, must be within 1hr of office. Call out to office is a $275 flagfall, and then i start billing hours as per normal.
I am also Aus. Maybe you should ask for more?
Mine was just phone work, IT support, and it was public service, so the rates were set
Anyway it was full pay (at penalty rates) whenever I got a call
- I get 15/hr just for being on-call. This is on top of my normal salary. Whether I receive a call or not.
- See above
- We have a maximum engagement time of 12 hours, then rotate with your backup on-call resource to keep folks fresh.
- A primary and a backup are rotated out of a team of about 10 or so. There is always 2 levels of escalations available.
- U.S. - Remote
Based in Israel, don't get anything. This is standard as our contacts usually specify that a third of our salary is legally considered compensation for overtime.
There's no defined schedule, it's mostly "whoever is available will take care of the incident, and if multiple people are available then they should join too". It will obviously not go smoothly if you're never available. This is terrible, I wonder if there are any other places that behave like this.
It should be noted that this isn't weird considered the working hours are quite bad compared to the OECD, not terrible though.
It's not worth being on-call.