Earlier quoted context omitted.
I know it's pushing it, but couldn't one go w/ 1 team of 5 (probably 6 for minimal downtime/buffer?) in NA to cover 24/7?
Making people operate against circadian rhythm is a hard sell. Google advocates against that in SRE book.
Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
21–30 of 40 posts
Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#22Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#23Earlier quoted context omitted.
That sounds perfectly reasonable. Rules of thumb: If a business has to operate 24/7 worldwide (and maybe even have office in multiple locations), it's gonna need over 100 employees. There is no sane way around that. You don't want to be in a business with less than that many, trust me ;)
WhatsApp was operating with 650m MAUs, 24/7, and was purchased for $19 billion. How many employees did it have? 55.
Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#24Earlier quoted context omitted.
That sounds perfectly reasonable. Rules of thumb: If a business has to operate 24/7 worldwide (and maybe even have office in multiple locations), it's gonna need over 100 employees. There is no sane way around that. You don't want to be in a business with less than that many, trust me ;)
WhatsApp was operating with 650m MAUs, 24/7, and was purchased for $19 billion. How many employees did it have? 55.
Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#25Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#26Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#27Earlier quoted context omitted.
It's not even layoffs. Just making use of "Altersteilzeit" (early part-time retirement) and then not filling the retired jobs.
'zeit' must roughly translate into 'time' in German, based on context. Is that correct?
Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#28Earlier quoted context omitted.
That sounds perfectly reasonable. Rules of thumb: If a business has to operate 24/7 worldwide (and maybe even have office in multiple locations), it's gonna need over 100 employees. There is no sane way around that. You don't want to be in a business with less than that many, trust me ;)
If you need 1 engineer available 24/7, you need 3 teams of 3, one each in APAC, AMER and EMEA, at minimum . You can't sustain running with less, otherwise people can't ever take vacations or get sick... if you need 2 you need at least 12 and so on.
You need one team of three for 24/7 NOC coverage, even for a worldwide customer base. Preferably four or more but three will do for a while.
Tickets are automatically generated from alerts for anything from unusual web server logs to disks filling up to network bandwidth spikes to slow SQL queries, etc. The NOC staffer attempts to resolve problems on their own, and identifies and calls the first point of contact for specific issues as necessary, following the appropriate escalation procedure.
As people get woken up in the middle of the night for their shit breaking, after a few weeks, suddenly regular problems either go away or standard procedures for fixes are documented. In a few months a staff of three can handle 90% or more of the tickets that are automatically generated.
We were doing this over 10 years ago with about 2000 servers getting traffic from 2,000 to 150,000 hits per second on Perl web apps. Honestly, nobody does anything efficiently anymore.
Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#29Earlier quoted context omitted.
If you need 1 engineer available 24/7, you need 3 teams of 3, one each in APAC, AMER and EMEA, at minimum . You can't sustain running with less, otherwise people can't ever take vacations or get sick... if you need 2 you need at least 12 and so on.
Apparently you have never worked in a NOC? You need one team of three for 24/7 NOC coverage, even for a worldwide customer base. Preferably four or more but three will do for a while. Tickets are automatically generated from alerts for anything from unusual web server logs to disks filling up to network bandwidth spikes to slow SQL queries, etc. The NOC staffer attempts to resolve problems on their own, and identifie…
Oh, you are talking about people who just phone other people, well you need to include the "other people" in your number.
Re: Who’s Hiring? Who’s Firing? Checking in on Tech Jobs
#30Earlier quoted context omitted.
If you need 1 engineer available 24/7, you need 3 teams of 3, one each in APAC, AMER and EMEA, at minimum . You can't sustain running with less, otherwise people can't ever take vacations or get sick... if you need 2 you need at least 12 and so on.
Apparently you have never worked in a NOC? You need one team of three for 24/7 NOC coverage, even for a worldwide customer base. Preferably four or more but three will do for a while. Tickets are automatically generated from alerts for anything from unusual web server logs to disks filling up to network bandwidth spikes to slow SQL queries, etc. The NOC staffer attempts to resolve problems on their own, and identifie…