Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For me, reaching 50, it is all about boring enterprise consulting.

You still get to jump around technology, althought it might not be as cool, as whatever newer generations are making use of on startups, but on the other hand seniority combined with such stacks is exactly what many companies are looking for.

Naturally social skills also play a big role, as they expect people of our age to also contribute to discussions with all involved key persons, drive architecure and junior devs.

You need to lookout for opportunities where you can bring more than plain coding.

Given their classical interviews and crazy workhours, I doubt Google is really the place to retire.



Google was relatively cozy when I was working there about ten years ago. (But that was as an SRE and in Sydney. I believe the Americans make more of a show of long hours? They always seemed more exhausted in any case.)


Might be, apparently doing less than 60h or not being reachable during the already short holidays is not doing enough, if the memes are to be belived.


I was there through 2016, and I was explicitly told not to work on weekends because it might make others on the team think they would have to do the same.


What about non-SREs? I get SREs need to be always on-call but I'm not sure about other positions.


I really don’t understand that - if you have 20 SREs why would you need to be on call more than 3 weeks a year? If you do get called frequently then you should probably be working shifts anyway.


20 SREs, assuming two different time zones, means ten weeks per year. You need two people in the same continent for the same 12h shift, so that one can drive, take the train home, shower, etc. Within five weeks, you have gone through the entire team.

If your pager response SLO is not that strict and is not impacted by such routines, then you probably can't justify staffing a team of 20, either.


You need 6 people to staff a 24/7 desk on a 6 week rota. That’s not on call, that’s actual work, assuming you don’t need to cover toilet and meal break or handle two fails with equal priority (when I used to work regular nights I’d have a pager when I went to the canteen)

You can do it with 5 but that leaves little room for covering illness and holidays, and you tend to end up paying overtime.

If you are getting frequent call outs out of hours, you need 24/7 coverage at a skill level high enough to reduce the total call outs to just a handful per year.


Only being oncall 3 weeks a year doesn't work: you'll forget everything in between.

It makes more sense to split the work by topic or area or so.

But yes, follow-the-sun shifts make sense.


I think maybe two reasons:

1. Multiple SREs on-call for the same week.

2. On-call chains make senior ones called more often than they hope so.


But where did you get the '20' figure from?

Many companies have specializations, and maybe only 1,2 or 3 people for each one. So at best you might have some vacation coverage.


There's always going into management.. become an SRM today! ;o)


Depends on the team you're working with. I'm not going to call out names. But some teams are nightmare 60hr weeks and other teams are 30hr weeks.


Are you talking about big companies like Accenture, Deloitte, etc? Or something else?


I am talking about Fortune 500 consultancy, those aren't the only ones.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: