You won't be excited to go to work when you were woken up for the 3rd time this week at a page at 4:30 in the AM because your db replication took a dump again,

You won't be excited to go to work when you were woken up for the 3rd time this week at a page at 4:30 in the AM because your db replication took a dump again, or one of the ten other single points of failure in your architecture dies for the 5th time this month. I did oncall work for large pharma for 7 years, then also for AWS. It is terrible. I can guarantee you everyone there for the most part hates oncall. Everyone has to plan their lives around it, pre-plan trying to swap weeks out which overlaps family time and basically being tied to your pager and a computer / internet location for a week at a time is the worst thing in the world. The type of job posting above sounds like you will be doing all of the crap work just keeping the lights on and never have any time to sit down and convince people how to reasonably re-architect all of the crap you are up all night working on...because you have no time to do anything but fight fires. Being up all night and shifting your work schedule to 11AM - 7PM for the week just because you know you will be up in the wee hours of the morning every time you are on call is something I never want to go back to. What's that you say? I'm the only person on the oncall rotation? Well unless off hours pages are few and far between, don't expect me to be picking up trouble tickets every night or weekend because I am actually going to be out drinking at the bar, or doing other things. If your oncall load is this high, you better be hiring additional peers because there is no way I'm going to be expected to be tied to my computer every day of the year.