3 ms·
This sounds a bit hard to believe. Mind sharing some of the $ figures of this business? Nevertheless, I'm with the parent. This practice is abusive. When yo
by YZF 5y ago
This sounds a bit hard to believe. Mind sharing some of the $ figures of this business?
Nevertheless, I'm with the parent. This practice is abusive. When you're not working, you're not working. Being on call is working. If a company wants you to work longer hours they should make it explicit, pay for it, and comply with the local employment laws. This sort of argument that the business has no merit if they were to hire more people or pay can be applied to many exploitative situations. Most of the companies doing this are drowning in profits.
- p2t2p 5y agoMy company pays for on-call. There is a rotation, you go for a week and they pay you more for that week by several hundred AUDs and it is basically a job requirement. Does the fact that it is discussed during hiring process and that it is paid change you opinion about being oncall?
- YZF 5y agoI think that sounds fair. The concept of being on call is not unique to software engineers. You might be an emergency doctor. You might be a fighter pilot. It's possible that some software engineers need to be on call, because they support some critical infrastructure, and that can be part of their contract. I would say the default assumption for most software engineers should be they are not on call and the company should try to structure itself around that assumption. The problem starts it's just considered the norm that software engineers are expected to work 24/7.