Live data from Hacker News

Dark side of a Valley software engineer

businessinsider.com

21–30 of 89 posts

Re: Dark side of a Valley software engineer

#21
post #13

Earlier quoted context omitted.

I'm pretty sure it's just USA. I make a good salary in the North East of UK and I was told multiple times by people from US that I'm crazy to work for that kind of money(If you moved to US, you would easily make 3-4x as much!). And sure, maybe it's true. But I enjoy working 37.5h/week, having 25 paid holiday days a year, unlimited paid sick leave and having a job that I actually like doing - plus I don't really have…

Indeed. Your salary is relative. If you're earning 3-4x more but have to pay 3-4x more on all your expenses, are you really richer? Factor in long hours in general, unpaid overtime, crunch times, a poor work/life ratio in general, etc. It seems like the scales are balanced all wrong. That's my perception as another tech worker living in the UK. I'd love to hear an argument as to why that isn't the case.

That's also the reason why I love being on part-time. I only get 70% salary, but I get 12 hours more time each week for my own projects, or just for hanging out in the city before sundown.

Re: Dark side of a Valley software engineer

#22
> A Google site-reliability engineer starts work at 9 a.m., leaves at 7 p.m., and works in the evenings until about 10 p.m. He's on constant alert because he must respond to urgent pages within 5 minutes. "Go home at 7pm with my backpack and fully charged laptop. If I get a page on the road I need to pull over and get on the system in 5 mins to start debugging. An email alert can wait until i get home.

Can anyone please comment on the veracity of this quote? I'm interested in a SRE position and I was researching details a while ago and the only info I found on work hours was someone saying that, given that Google has employees all around the world, you don't really need to do crazy hours or night shifts. However, the comment above indicates 12 hour workdays, which is insane. Is that every day? How does it compare to a Software Engineer position at Google?

Re: Dark side of a Valley software engineer

#23
post #19

Earlier quoted context omitted.

Hehe, perhaps not only theory. I did loads of overtime in London, got a 50% pay rise and allowed to build and manage a team, then sent to the USA with UK holidays but US taxes (lower), free housing and further payrise.

I think generalizing in either direction is a waste of time. Surely where you live won't have that much effect on whether you've decided to work overtime or not. Though I suppose it's more popular to start a business in some locations than in others.

Plural of anecdote!

Re: Dark side of a Valley software engineer

#24
post #22

> A Google site-reliability engineer starts work at 9 a.m., leaves at 7 p.m., and works in the evenings until about 10 p.m. He's on constant alert because he must respond to urgent pages within 5 minutes. "Go home at 7pm with my backpack and fully charged laptop. If I get a page on the road I need to pull over and get on the system in 5 mins to start debugging. An email alert can wait until i get home. Can anyone ple…

https://www.quora.com/What-is-a-normal-working-day-for-a-sof...

Re: Dark side of a Valley software engineer

#25
post #13

Earlier quoted context omitted.

I'm pretty sure it's just USA. I make a good salary in the North East of UK and I was told multiple times by people from US that I'm crazy to work for that kind of money(If you moved to US, you would easily make 3-4x as much!). And sure, maybe it's true. But I enjoy working 37.5h/week, having 25 paid holiday days a year, unlimited paid sick leave and having a job that I actually like doing - plus I don't really have…

Indeed. Your salary is relative. If you're earning 3-4x more but have to pay 3-4x more on all your expenses, are you really richer? Factor in long hours in general, unpaid overtime, crunch times, a poor work/life ratio in general, etc. It seems like the scales are balanced all wrong. That's my perception as another tech worker living in the UK. I'd love to hear an argument as to why that isn't the case.

Assuming you had money left over to save, yes, you would be. You would be banking 3-4x as much money, if income and expenses remained proportional

Re: Dark side of a Valley software engineer

#26
> 7 a.m. Wake up. 8 a.m. Refuse several job offers from Google, Facebook, Oracle, HP and other tech giants. 9 a.m. Write some code that wipes 100 jobs by making people less useful. Noon Free food. 1-3 p.m. Wipe even more jobs. 5 p.m. Meet with investors that are dying to invest in anything that you touch. 7 p.m. Dinner at the Ritz-Carlton. 10 p.m. - Comment on some company blog. Post goes viral and the company becomes an overnight success.

I laughed out loud when reading this one, then I got silent as I realised how accurate this is compared to my current situation, and I don't even live in Silicon Valley...

Re: Dark side of a Valley software engineer

#27
post #24
post #22

> A Google site-reliability engineer starts work at 9 a.m., leaves at 7 p.m., and works in the evenings until about 10 p.m. He's on constant alert because he must respond to urgent pages within 5 minutes. "Go home at 7pm with my backpack and fully charged laptop. If I get a page on the road I need to pull over and get on the system in 5 mins to start debugging. An email alert can wait until i get home. Can anyone ple…

https://www.quora.com/What-is-a-normal-working-day-for-a-sof...

The important bit from that page is:

"I am on-call about 10 days per quarter, usually 3 shifts of 3-4 days each. I am paid extra for my on-call (after-hours) work, but not at my full hourly salary because I only work when there are problems after hours (e.g. on weekends or late at night.)".

Note that depending on the exact team, Software Engineers at Google may also be part of an on-call rotation.

Re: Dark side of a Valley software engineer

#28
post #19

Earlier quoted context omitted.

Hehe, perhaps not only theory. I did loads of overtime in London, got a 50% pay rise and allowed to build and manage a team, then sent to the USA with UK holidays but US taxes (lower), free housing and further payrise.

I think generalizing in either direction is a waste of time. Surely where you live won't have that much effect on whether you've decided to work overtime or not. Though I suppose it's more popular to start a business in some locations than in others.

In some countries there are many more rules about working time.

For example, in the EU it's not permitted to work more than 48 hours per week on average. As far as I know, that includes "on call" time.

http://ec.europa.eu/social/main.jsp?catId=706&langId=en&intP...

Re: Dark side of a Valley software engineer

#29
post #24

Earlier quoted context omitted.

https://www.quora.com/What-is-a-normal-working-day-for-a-sof...

The important bit from that page is: "I am on-call about 10 days per quarter, usually 3 shifts of 3-4 days each. I am paid extra for my on-call (after-hours) work, but not at my full hourly salary because I only work when there are problems after hours (e.g. on weekends or late at night.)". Note that depending on the exact team, Software Engineers at Google may also be part of an on-call rotation.

Yes, indeed, turns out BI just cherry-picked the worst part.

Re: Dark side of a Valley software engineer

#30

>>If your manager is not a software engineer himself you will have even more stress. Someone should do something about this. Certain other professions, such as the law, protect workers from incompetent management, in many jurisdictions. It might also attract more people to the profession if you knew your boss had done something similar.

On the other hand, not all managers with a tech background have good people skills to manage engineers.

On top of this, if they think "he's slow, I could do this in 5 minutes", burning out becomes a lot easier.
Post reply on HN