Why not? Requiring off-hour access is admitting project management failure. That’s what on-call is for, and on-call engineers and management should rotate and be paid for on-call duty. For them, it’s working hours. When I’m on call for a client, I bill _for being available_, so basically for keeping the phone on.
You are completely right.
Management lack of competence is pushed down and transforms in extra working hours for everyone else. In this kind of company, people are always putting down fires instead of working strategically. That causes more fires and more extra work at any time of the day.
The way I usually approach these discussions is “ok, you can have the feature built this weekend, this means people need to work their weekend, that costs 50% extra and means that the people working extra hours will be unavailable some time in the future.” Same thing with 24/7 support. It just costs money. Staff needs to be available. 90% of the people decide that Monday will be good enough.
The hard fact is that someone needs to pay for 24/7. It’s either the client, the employer or the employee. It’s just that a lot of employees don’t realize that they’re getting shortchanged here with talk about engagement and promise of better projects and I’m trying my best that this doesn’t happen in my company on my watch.
24-hour is harder, but when you have clients across different time zones, it is also a norm. Again, with big films scattering themselves across the globe, it is expected that someone in authority picks up 24/7 because your 3am is sometimes the client's 10am.
You can charge more for this, but the client doesn't want to hear complaints. You will be judged on service rendered for a given price. The firm down the street, the one who can provide people on a sunday without overtime, will win the next contract.
There's no 'on call' for the kind of projects that parent is talking about. There's a small handful of guys who get shit done and maybe a second ring development team around them.
For some people, the truly exciting work is the work where none of this stuff has been proceduralized. It's not feasible to train or do knowledge transfer between two shifts for these projects.
I know folks that sit on packed bags, ready to fly to Alaska and hike another 50 miles to fix failing cell infrastructure, but even they have a notion of “i’m on duty now and I’m off duty.” And on top, they get paid a shitload of money for being available just in case.
You make a deal with your #1s that they will get the fun projects, the paid vacations when the current crisis is over, the completely flexible hours and full autonomy. Anything they want within reason, as long as shit gets done.
It's not for everyone, but I can see where GP is coming from.
Flex hours is a thing that helps, but even there must be an agreement that when you’re off, you’re off. Companies can be stuck in perceived crisis mode for years at a time.
I had the employer pay for some of my vacations during downtime, I progressed along my career path much faster than normal employees, I was paid more than normal employees. It was a good gig.
And even startups need to get out of “we’ll wing it and cover with our lives for our management failures” mode as early as possible because it’s clearly not sustainable.
You don't have to pay for the vacation, if the crisis never ends.
This is true, but this is really question about compensation, not work time. Executives are basically always on call but they get executive pay.
If you are not well compensated for doing the work that can't be replaced, you are being exploited.