Lol. When I was a student, I worked all sorts of shitty jobs. Here's how it looks when I compare overtime hours I worked in different places.
1. Factory work: no overtime ever. It's against the safety regulation. When the bell rings, you must go home or punitive measures will be taken against you.
3. Working as a waiter / room service: you fight for overtime because you get paid extra. Especially if you do overtime on holidays. It's hard, but is totally worth it.
2. Other shift-based work, s.a. night guards, cleaning, cab dispatcher. It usually happens if the next shift is tardy / stuck in traffic etc. It's annoying, but doesn't happen a lot.
3. Bakery. Holly hell! You have to show up at work at like five in the morning and you get two breaks during the day when you can sit down. Your day ends up around five in the afternoon, unless it's a holiday when everyone wants extra donuts / cakes / pastry, then you go home at eight in the afternoon. No pay can possibly justify this, but you work for pennies.
4. Newspaper. Every now and then you need to sit in the office an wait for the important game to finish so that you can publish the score the day after. Meh. It's fine. You spend time sipping tea and chatting to the other person staying with you.
5. As a programmer: you switch your status in Slack to WFH. Also, the amount of overtime work I ever put in as a programmer was negligible. I know people in game development work their butt off and do a lot of overtime. But that's unique to that field. The rest of the programming world just doesn't see overtime at all. Well, maybe NOC, but they aren't really programmers.
----
6. I'm not a doctor, but my wife is. Doctors work the most overtime of all professions I know. They don't even really have that as a concept as, for example, if you are a surgeon, you just keep going until the surgery is done. If it takes days, then it takes days.
Do you mean "IT" as in the people who deal with technical issues / supplies that the company is facing (they might be working in shifts). Another way to use "IT" is to refer to the whole group of people who operate computers on a more than user level, but mostly including people who'd self-identify as programmers.
If you mean the former, then yeah, these people might work in shift, but usually don't (they might work in shifts only if the organization they support needs 24 hour technical support, or NOC, as I've already mentioned), which most organization don't need. This technical support interpretation of IT is very rarely programming anything (exceptions are SREs or PEs in large companies where there's so much complexity in their in-house infrastructure that they need tech support to program).
In the later case, there's no need for most of IT to work in shifts. Definitely not at night. Same way how there's no need for accountants to work in shifts (and definitely not at night).
Lol. When I was a student, I worked all sorts of shitty jobs. Here's how it looks when I compare overtime hours I worked in different places.
1. Factory work: no overtime ever. It's against the safety regulation. When the bell rings, you must go home or punitive measures will be taken against you.
3. Working as a waiter / room service: you fight for overtime because you get paid extra. Especially if you do overtime on holidays. It's hard, but is totally worth it.
2. Other shift-based work, s.a. night guards, cleaning, cab dispatcher. It usually happens if the next shift is tardy / stuck in traffic etc. It's annoying, but doesn't happen a lot.
3. Bakery. Holly hell! You have to show up at work at like five in the morning and you get two breaks during the day when you can sit down. Your day ends up around five in the afternoon, unless it's a holiday when everyone wants extra donuts / cakes / pastry, then you go home at eight in the afternoon. No pay can possibly justify this, but you work for pennies.
4. Newspaper. Every now and then you need to sit in the office an wait for the important game to finish so that you can publish the score the day after. Meh. It's fine. You spend time sipping tea and chatting to the other person staying with you.
5. As a programmer: you switch your status in Slack to WFH. Also, the amount of overtime work I ever put in as a programmer was negligible. I know people in game development work their butt off and do a lot of overtime. But that's unique to that field. The rest of the programming world just doesn't see overtime at all. Well, maybe NOC, but they aren't really programmers.
----
6. I'm not a doctor, but my wife is. Doctors work the most overtime of all professions I know. They don't even really have that as a concept as, for example, if you are a surgeon, you just keep going until the surgery is done. If it takes days, then it takes days.