3 ms·
Somewhere in the OK to mediocre range. On the plus side a 40 hour work week was typical. On the minus side being on call may be a major hassle and increase your
by InclinedPlane 10y ago
Somewhere in the OK to mediocre range. On the plus side a 40 hour work week was typical. On the minus side being on call may be a major hassle and increase your work hours significantly and affect your ability to make plans on weekends or evenings depending on your team make up and the stability of your code base, etc. Also on the minus side: you don't get a lot of vacation time, there are periods of "crunch" when you'll be expected to work a bit more, and those periods can often be during traditional holiday times (thanksgiving, christmas, etc.)
- CaptSpify 10y ago> being on call may be a major hassle and increase your work hours significantly and affect your ability to make plans on weekends or evenings Could you clarify? that's kind of what I expect when being on-call anywhere
- InclinedPlane 10y agoKeep in mind that you're on salary, so no matter how much you work while on-call you still get paid the same. How often you're on-call depends on how big your team is, if you get unlucky and have a tiny team for a while (say, because everyone else quit) you might end up on-call quite a lot. Also, depending on the code base and what your team is doing at present there might be long periods of time (months) where when you're on call it's very intensive, with frequent periods of getting up at 2am to fix problems, working a lot more hours, etc. Most importantly, unlike a typical Ops/DevOps job where being on-call is "your job" you are still expected to deliver on your "real" development job in addition to being on-call.