Yes, this is pretty common.
Because, ask yourself - how else are customers supposed to get critical software problems fixed in a timely manner?
You have a limited number of options as a business to service your customers:
- Have a large organization that has 3 continents worth of shifts, so it's always working hours somewhere (except for weekends, and holidays, and such)
- Have staff available after hours to some extent
- Don't help customers after hours.
Some businesses can get away with #3. SaaS businesses and competitive businesses can't. You can try to have "first level support" on the weekends but only escalate to engineers during their work day, but that ends up being a decision made if the business doesn't demand it to be successful.
Some businesses can afford to do #1 via running shifts or "follow-the-sun" staffing - but there's always the problem of issues that go beyond the ability of whoever's at work at that time and needing a specialist. Trying to have a distributed team that's actually qualified to work all levels of issues is nearly impossible, so even if you do #1 you may need (albeit less) #2.
So often your business ends up needing to do #2. There's infinite schemes here - often fronting things with automatic support, and "support engineers" that are not full developers/operations engineers that are a lower cost option, and so on, but it is common to have either a formal or informal after hours "on-call" rotation for software developers to handle critical problems. This can be paid "just as part of your salary" (common in the US) or "paid as a separate hourly thing" (a lot of Europe). In some companies it's a choice, in others it's not, it's a condition of employment in that role.
Based on the business need, the staffing, and how crappy the software is, I've seen oncall activity be anything from "once in a long while" to "you are on call all the time, just you, and absolutely having to handle issues every night." This is like any other facet of a job - how much does that bother you, how much money is it worth to you, how employable are you otherwise? When I was younger and had been unemployed for a year due to the recession, I took a tech job with lots of oncall and was happy to have it. Now I'm older and well off and try to avoid it more.
Local laws and norms may try to prevent off-hours/extra hours work, which is fine, but also means there's fewer software jobs in those places. I was working at a multinational and we had our US team and our EU team and the EU team didn't want to work oncall for the SaaS product we were running (even though we offered pay for it and stuff). Fair enough... But then that office started asking "hey why aren't we hiring vacated positions here? Is this office growing or what?" And the real answer was "Look, we need engineers to do the job we need done, and we're going to hire in places where that will happen." US engineers were more expensive than the EU engineers but we were willing to pay more to meet our business need. Welcome to the global economy.
So there are jobs that don't require it, but there are also many jobs that do, so you'll have more job opportunities and make more money if you do it.