That seems like a very long-winded way to say you hate on-call, which is a completely normal thing to do. That said, is on-call effectively mandatory or very popular in the US startup world? Because here, in the European established company world, I can’t really recall seeing a job posting with on-call listed.
In Finland you usually get a static pay just for being on call, meaning you're X minutes away from a company-approved device you can use to fix things if they break.
If there's an actual alert you need to respond to, your pay goes to 2x hourly rate, or 3-4x if it's the weekend and there usually is a minimum amount of billing you do if you have to do any work, usually 30-60 minutes. So if you get an alert and you fix it by pressing the "fix it" button on the dashboard on a Sunday, you just got paid hundreds of euros.
On the other hand you most likely saved the company from losing multiple times that in revenue, so it's worth it to the company.
I have a bunch of friends who were single and/or child free in their 20s and have fully paid apartments/houses because they could be on call at any time because they didn't have any commitments.
I also know a good amount of incidents that were fixed in a pub corner table after a few drinks. I may or may not have contributed to that number. =)
Yes, basically every eng position paying what HN people expect will have the exact sort of described oncall.
I worked on OS frameworks at a FAANG and there was no on-call for anyone on the team.
The users of your flawless frameworks absorbed all on-call load.
I have yet to be on an oncall that is similar to what was described there, and I get paid pretty well. It's very much a function of where you work and what you work on.
Curious how this is the case. Do European companies not provide 24/7 services? Or staff a "follow the sun" model so no one has to answer pages outside of working hours? Do Europeans write better code so they don't need on-call?
I've worked at a few FAANGs in the US, and every single one after 2010 had an on-call rotation.
We totally have on-call, but we're also weaponizing German labor laws to force the company to have their shit together. There are a few interesting parts in there that cause quite the discomfort for employers:
The way contracts are worded, time working on on-call is work-time. Kinda obvious if you write it like that. As such, bad on-call weeks easily cut into the normal duties of the employee. This means team leads have an incentive to reduce time wasted on on-call.
You have mandatory rest-times. If an on-call activity takes an hour or so to fix, the person is suddenly not allowed to work for 10 hours due to these rest-time and maximum work time laws. Suddenly, "some little fixing at night" means the person isn't allowed to work the whole morning.
With a few rules like that, pages become really painful to the company. When a bad application kept pinging on-call every night for a few days, the entire normal work ground to a halt with people being unavailable, other team members dropping project work from sprints to pick up daily business slack. Some product managers got really pissed off and things in that product improved - I'm kinda curious what happened behind closed doors there. .
It's actually 11h of mandatory downtime "between shifts"; this does indeed provide for theoretical opportunity to get good sleep for people with a short enough commute.
Nothing like that in Canada or, I suspect, the USA. You'd be expected to work the morning after.
I think it's mostly down to three factors:
1. Uncompensated oncall is legally tricky in many EU companies, so a lot of midsize companies look at the cost of paying for oncall, or sometimes just the time of administering paying for oncall, and decide they can do without. High frequency oncall is also often restricted (e.g. more than 1 week in 6 is not legal here)
2. A lot of the smaller companies are europeans selling to europeans, and are much more used to a business culture of availability during office hours. Especially there's a bigger share of like b2b back office stuff in europe compared to like, restaurant POS systems.
3. Larger companies do seem more into follow the sun. A lot of the big tech in europe are subsidiaries of US companies, so if they're in Europe it means they've already opened one remote location, and therefore are more likely to have another (California, Europe, India is a super common arrangement)
Never had on call in 25 years with American startups. Surprised that faangs have on call but offer no support or limited that may take days to get a response from a customer perspective.
Had some level of "on-call" in the sense that "there's a bug with your new/recent code and customer needs a fix" or "the demo isn't working and we present tomorrow" or "checkin deadline is in 2 weeks and my code isn't ready" pressure in 20+ years in silicon valley working at a startup and 2 medium size companies. The startup had a bit more since I knew lots of sysadmin stuff so I could help at times when our main IT guy wasn't available - but he was quite good and didn't let me have root access anyway, so it's not like I could have fixed it on those rare occasions.
Mind you, I interviewed for a Yahoo Mail job that would have included wearing a pager (back in '05). And I know it's pretty common - I've been fortunate to not have that be an issue. Hoping for another ~5 years at the current job until I can retire.
I've been on-call (sometimes on a rotation, sometimes always) for the past 10+ years. So, yes. It's common.
on-call is ubiquitous in the US tech industry. I've never had a job without it.