Dark side of a Valley software engineer
businessinsider.com
businessinsider.com
Now: Wake up at 8 get to work at like 8:45 work till 6 or 7. Sit in air conditioning all day at a computer. Free lunch. Go home, don't worry about anything. No tests to study for, no worrying about paying rent. Holidays off. Weekends off.
Yea development sucks sometimes but it's almost like doing nothing compared to what I was used to. Sometimes when I get frustrated I just have a flashback of my old life.
In part because of this, I find it really difficult to deal with people I work with complaining about pay/bonuses/hours etc, because imo what I do now is way easier and probably less empirically useful (although obviously more valuable - thanks capitalism).
There is a small part of me that misses the buzz of a busy service though.
I get what you're saying and that you likely don't mean any malice, but just in case: It isn't a competition to see who can have the worst working conditions.
That kind of rhetoric is the same that those with capital use to suppress wages/benefits because it's obviously profitable in the long run. It's a manipulation: Many people want to be seen as industrious, and telling someone they're entitled because they want an extra vacation day a year is a powerful manipulation that works much of the time.
Don't be manipulated. The company is almost assuredly making a huge return on your employment. Don't be afraid to assert your right to some of it.
Never go to ask for a bonus/raise because you "deserve" it, but because your skills are valued x in the current job market.
I mean some I know are very intelligent people, and extremely good at what they do, but make like $50k working 60+ hours per week. It's insane.
For those guys (and it was almost all guys) - it was just the only thing they wanted to do in life. This was also kinda the moment I realised it wasn't for me!
I remember a good number of people on high school who thought they didn't fit in, only went because their parents made them go and who had no intention of going to college or university. Their plan was getting a blue collar job or working for a friend's dad or the like. These days their outlook is dim. There was little forethought in what their situation might look 20 years on, given their choices.
"I'm training my off-shore replacement, but at least I'm doing it in air-conditioning!"
In case "mandatory crunch time" becomes the norm, I simply look for another job.
Being able to appreciate that I have that choice is another matter.
The months before, during and after interview season were the worst. I had to add 10 hours a week to study 1-2 months beforehand. Then during the interview season, I had to miss classes to go on 7 hour east to west coast flights, with return flights landing at 3 AM local time. After the interviewing season ended, there were mountains of work from missing classes and neglecting school work.
Now it's 10 AM - 7:30 PM (including meal time, I never eat at my desk) with free breakfast, lunch and dinner with no deadlines to worry about. During the undergrad years, I was studying by memorizing the answers to all permutations of a problem because of stress and multiple deadlines a week, but now I have the time to understand the how's and why's of the questions and answers.
Also the money that can effectively be used buy time is nice. I can afford to pay people to fix my toilet/unclog my sink/build IKEA furniture/etc. and have the money to order grocery delivery/drop-off laundry/take-out/etc.
tl;dr: yes, there are worse jobs than programming, but not many. The ridiculous amounts of stress is one of the reasons Silicon Valley pays so much more than Industry jobs.
> harsh deadlines, huge backlog of tasks, fear to fail
This happens everywhere. Deadlines exist because customers exist. All backlogs grow until they're silly. Companies may have a fear to fail. But if you have multiple engineers and they're afraid of failure, that's on the management.
> If I get a page on the road I need to pull over and get on the system in 5 mins to start debugging.
That's just terrible planning. Why are people on call when they're traveling? Even some basic rule like adjusting working hours +/-1h for different people on call to account for commute would help. And we're talking about google who could just do 8h support in 3+ countries and get rid of on call apart from n-th tier "the world is on fire" specialists.
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.
I did have to bust my ass a bit to get to the point where I had the skillset and the knowledge necessary to do it, but I'm glad I did. That I am at this point is probably some of why I feel freer to criticize the tech industry--I've been on the bottom and I've since largely stepped out, and it's ugly looking in on it.
Imagine you're making $100 per month right now and spending $95 of it. So you're saving $5 per month.
You move to the US and start making $400 per month, but your expenses skyrocket to $380 per month. But you're now saving $20 per month -- four times as much as you were before.
Now imagine those savings numbers were $1k and $4k, and the difference becomes a pretty big deal.
At the same time, I make enough to pay mortgage on a 4-bedroom house, have a car that I really like, and have the latest gadgets I like. Sure, I can't afford a rolex or a ferrari - but that's fine with me. Saving more money while working in the US and worrying about the above is just absolutely not worth it to me, but again, that's just my personal opinion.
Though I suppose it's more popular to start a business in some locations than in others.
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...
That's 11-12 hours per day, which in the EU would limit him to four working days per week.
For someone working normal hours but also on call, if they respond to an incident during the week they're likely to be given e.g. Friday afternoon off in return.
> career perspective
Did you mean prospects, or something else?
I'm sure it makes a difference in some companies, but there are plenty where it doesn't impress anyone.
My sense, too, is that the industry tends to attract workaholics.
Sometimes it grows out of the company as it scales up. Other times it gets institutionalized. The Googles of the world are in a weird spot because they made it part of their culture but the financial and industry upside of working for them mean people apply even if they aren't the kind of folks who can work 60h week for 10 years. Who can say no to that kind of pay cheque?
I think you don't know in advance how long you can stand this before you burn out.
This is, sadly, in line with the mentality of the country's workforce, that believes that you're only doing your job (good or not) if you're leaving after hours...the result is basically people that are too worn out and/or uncooperative by the time they're 40 or less...
It doesn't happen everywhere.
I work for Pivotal. In my first month I took a train from NYC to Philadelphia to take a weekend course I was interested in. I left the office at 6pm sharp, when we close. At 7pm the train pulled out of the station. I was bored, so I opened my laptop and logged into my work email.
I bounced a few emails back and forth with client devs, who will still in their office. Then at 8pm I closed my laptop and continued merrily on my way.
On the following Monday I was told, in no uncertain terms, to never work after hours again.
The latest I've worked in the office is 6.30pm. Because I thought I'd broken our public cloud. By 6.15pm I had multiple people wandering up and asking why I was still working.
We just now introduced pager duty for teams with operational dependencies. And the policy is: if you have a reason not to answer, then don't.
I am constantly amazed at what people will put up with. Really amazed.
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?
"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.
When allocated 100% to cash (vs. vacation) oncall pay amounts to more than an extra full paycheck every quarter.
If you don't notice an extra $10,000/year post-tax then please, send some of your moneybags to someone who appreciates the value of a dollar. Like me.
For me it's (off the top of my head) about 10%. Definitely noticeable.
Just thought this would be worth mentioning.
https://www.quora.com/What-is-a-normal-working-day-for-a-sof...
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...
This also happens outside of Silicon Valley but perhaps not to such an extreme extent.
The current system is far from a meritocracy because a lot of unlucky people fall through the cracks.
Given how hard I've worked, I've probably fallen through a lot of small cracks (but thankfully no major horror stories as described above).
I work 4 days per week rather than the typical 5 and refuse to do out of hours jobs, using the additional day to have fun with open source, exercise and just generally keep on top of life. I make well over double the annual average household income for the UK at 30 hours a week. I'd take that over ladder climbing as aggressively as possible any day. We really do have it pretty good.
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.
The job does not care that you won't be able to get interested in their stuff for unknown amount of months. It must be done, and now.
Reading these stories - do people actually get paid more for doing more over there?
Here it's a fixed monthly salary, regardless of how much you do (as long as the deadlines are met).
To be honest this is stupid this has hit the front-page because there are so many shit jobs out in the world. And you can't complain for working at one of the biggest tech companies.
First, getting such a job is a ton of work and then doing it isn't easy either.
I mean, how much people even have the education to got into IT and then score a job at Google for example?
For larger companies it's more transactional in nature: they have a job and a budget, and you have your own interests. The agreement you come to is more of a coldly calculated negotiation.
http://webcache.googleusercontent.com/search?q=cache:http://...
Oh well...
It may be fair to say that the pay ceiling is higher for the best-paid lawyers than it is for the best-paid engineers. However, engineers can reach the same pay or much higher by taking on a management role -- CTO, technical co-founder, small business owner, etc. -- at which point, IMO, they typically cease to be engineer.
Investment banking & hedge funds are another matter, and the compensation can be ridiculous.
From Glassdoor:
- Google corporate counsel ($188k salary, $215k with bonus)
- Amazon corporate counsel ($180k salary, $250k with bonus)
- Microsoft attorney ($164k salary, $224k with bonus)