Most people working like this are making things in factories or performing other relatively menial work such as first-line technical support (where most of the job is following scripts), but it is not entirely uncommon for higher paid roles. One example I can mention is in chemical processing (an industry some of my family have worked in): the plants tend to run 24/7 and they have to have safety & repair engineers and so forth on site at all times no matter how automated the processes are otherwise (a good, experienced, safety/emergency engineer can command a pretty impressive salary as they are expected to know a lot of stuff in quite some detail, perform well under stressful circumstances, potentially work in very dangerous conditions, and on top of that take responsibility for the safety of others and sometimes even responsibility for the actions of others).
Exchange 2010 I think added online automated mailbox moves, which obviated my job. So I've experienced software eating my job more than once.
BPOS was backed by Exchange 2007, I'm pretty sure, which required manual mailbox moves - you had to offline the mailbox to move its files, and we were basically manually rebalancing the mailboxes for thousands of users as each server's local storage became full.
Obviously it's very disruptive to offline a mailbox - the user can't interact with it at all, their client usually has a copy of some of their mail, but they can't check for mail, send new mail, save anything, or search for old mail. And all incoming mail is usually queued. So we had to do this during a region's nighttime. This made trouble for our customers who worked in i.e. the USA branch of an European company; they would have to deal with EMEA outage hours, which were something like 2pm to 10pm PST.
We were a 24/7 operation with a 15-minute SLA for emergencies, and we covered the after-hours alerts for several other groups as well. We provided worldwide support for the service. Us mailbox movers worked alongside the emergency oncall break/fix engineers.