Mental health impacts of a big tech job
oilyraincloud.com
oilyraincloud.com
To give another data point, I've worked at a different Big Tech company since 2012, on two different teams, and haven't experienced anything like this. There's no pressure to work after hours, on weekends, or vacations. Just today I was debugging a release blocker with a coworker, and it got to be 4:30, which was when they had planned to end their day. It wouldn't even have occurred to me to suggest they stay late: we can pick it up on Monday and the release can slip.
I'm sure there are people at my company who have experiences closer to the author's: what I'm trying to say is that Big Tech is a big place, and if you find yourself somewhere with bad culture don't take that to mean there aren't other places you would like.
Tell that to an H1B holder.
You're not wrong to point out that we can't generalize from a single data point, but you're wrong to bring your positive experience as if there is an equivalence between the two. They don't have the same weighing; we are not trying to have a 50:50 split between bad and good experiences. Even a single workplace-driven mental health incident is too many. And unlike other workplace related injuries, mental health injuries are elusive to tracking.
One hard metric would be the percentage of FAANG employees that are lost to suicide each year. It would be morbid but telling if some companies have an overrepresentation (I have my doubts but won't voice it here).
I don't think this is how statistics work. Both are one piece of data. In order to make meaningful conclusions, we need more data. It seems to me that all of a sudden we have a mental health epidemic and I am peppered by mental health stories left and right in the media including HN. I'd love to know more if what changed, some hard data, happiness surveys even if they have flaws, it is better than arguing like this.
I'll throw one more anedote - I've worked in large tech company and my experience was it was just super chill. No issues with a team of 24 engineers. Everyone left at 4pm everyday and at 2pm on Friday. In fact, people were frustratingly lazy.
I’m not saying this is the best metric but they would find that sort of treatment to be highly ineffective. Lifetime prevalence of depression and the depression at any given time are different things; it would be like trying to weed out all future cases of flu based on symptoms at hire time. Either way it wouldn’t make a dent on flu caused by the work environment itself.
It's a simple solution, but a bad one. The alternative is to overwhelm people with complete availability and encouragement of help, and while helping them, convince them that it's not in their best interest to own guns (ideally to agree to give up their right to own guns.) Actually effective change is expensive, so will not be done.
That being said, tracking tech suicides doesn't have to track the companies they work for in order to indicate if there's something wrong with the culture. Theoretically, identification of companies would certainly help to figure out what that wrong thing is, though the metric would immediately be gamed in the way you describe and exacerbate the situation.
> So someone with 20+ years of experience with subject matter expertise (not me) is a 'developing' Principal engineer.
If one of your major complaints about work is that some other employees only make $300k while some arbitrary table made by the company says they should be making $400k-$500k, then perhaps you're in a pretty good position overall?
In other words - it's a huge organization, of course it's not far from perfect. But, pretty much nothing in life is.
Golden handcuffs are a living hell.
1. https://www.reddit.com/r/apple/comments/kpgs1x/my_experience...
I suspect it's the same at all of the FAANGs, frankly. (Setting aside companies you may not wish to work for because of general company policy/work reasons)
I think it's important to realize that it is not limited to this industry; It's something that's actually also happening outside of bounds where people even might be used to this kind of remote work standards and practices, and it might be considered one even shittier to deal with when it comes to being new to this.
I also had a very similiar experience at my previous employer which was also a valley based company which IPOed.
I have multiple colleagues who are in the same boat, both current and former, and while I realize this data is anecdotal, from my perspective, work culture in the valley is just plain broken.
People are not robots, they need time to rest and adjust.
I'm writing my final proposal as one final swing at the bat and the title is "XYZ or Bust" where either I get buy-in or I'm leaving. I've never felt better in my entire career.
This is made possible because I'm old enough with enough assets that I can quit and retire, so now it is time to leverage the positives.
From reading this, it is clear the team he is on is toxic. The key to not being on-call all the time is not answering the call unless you in rotation. It's hard to do for sure.
It's not just the brazenness of the act, it's the fact you made your defiance into art that I really respect.
I will not do this PSC.
There is a future that I foresee.
No longer shall I bend the knee
to this process called PSC. Oh oh oh oh oh
Now I can bring you in
Warm or cold
I'll get paid either way
(Oh oh oh oh)
It might not buy me happiness
But it might just ease my pain
(Oh oh oh oh)
'Cause it's hard to live
This life alone
But it's all I've ever knownAs a former manager at said company, I would absolutely hate you for making my PSC hell-period even more hellish, as I would still be on the hook for delivering your packet under incredibly unrealistic timelines. Won't somebody think of the managers! ;)
You can't do that! Hey, come back here! You're not allowed to do that! Can you hear me? Get back over here, don't walk away. Don't keep walking away. Stop!
So, I think in management's eyes, very very very few people are irreplaceable.
And yet, from where I sit, it's not obvious that managers (at multiple companies) show that they care that much. I think the exception was when I was at a startup, but I think that was due to combination of two reasons: The amazing manager, and the fact replacing a specialist on our team was even harder.
Disclaimer: My views are my own.
Look at any failed multi-decade war waged by any unbeatable superpower past or present to see the highest levels of military and civilian command employ these exact same methods to build careers so successful that they'll be immortalized in statues for centuries after their deaths :)
But what's also been true for a very long time is that, outside of some of the older larger companies, Silicon Valley has normed job tenures for a lot of people that would seem ludicrously short most other places and would, in fact, possibly make those people unhireable.
This is the life changing part.
“Well, I wouldn’t say I’ve been missing it, Bob.”
i don't even care to write anything. They aren't going to fire me - there is so much manure to shovel that somebody got to do it and after 30 years i do it very reliably (and i don't care whether i'm doing it here or at some other place, whereis our department has huge challenges hiring people in US). And i'm not promotable anyway.
>The key to not being on-call all the time is not answering the call unless you in rotation.
additional trick - to not go into rotation too, at least until it is really core nature of the business that you was aware about when coming onboard.
>enough assets that I can quit and retire
unfortunately not there yet. Yet it doesn't really matter much as long as there is a demand for tech labor.
(Not retired yet, I knew I was quitting a week or two later. Amazingly my boss was surprised when I gave my notice …).
Can't recommend this enough. I've nearly always opted-out of performance review dance. Just don't do it. In most companies I get pushback to do it but then they give up and it doesn't matter at all. Still get my promotions.
This really has nothing to do with Big Tech and is a nearly universal characteristic of any job that requires mental effort instead of physical. Yeah, if you're getting paid to move boxes all day, the boxes don't follow you home. If you get paid to think all day, the thoughts do. Nothing much you can do about that other than learn to deal with it.
My friends who are scientists think about their research in their free time, and worry about upcoming conference deadlines, etc. My friends who are lawyers think about their cases and upcoming filing deadlines. My friends on the business and sales side think about clients and deals and marketing. That's just how it goes. Be glad someone is willing to pay you for it and that your brain doesn't wear out from thinking the way your back wears out from carrying boxes.
This person just sounds like they have trouble setting boundaries and some general anxiety issues. I am a SWE at a FANG company right now, in a reasonably important and high-profile area, and the work-life balance is way better than any other job I've had at smaller companies both in and out of "tech".
https://epicflightacademy.com/wp-content/uploads/2020/04/maj...
https://epicflightacademy.com/wp-content/uploads/2020/04/car...
It's way higher than what I expected.
> your brain doesn't wear out from thinking the way your back wears out from carrying boxes.
this is not obvious at all.
I worked in one of the ads teams at Google. I quit a few weeks ago, with reasons similar to the ones described in the article. I was giving just way too much of my life away for that work...
I was in Corp and now I'm in Cloud. I haven't interacted with anyone in ads so I am not familiar with the experience. Do you think your peers had a similar experience as you?
I’m thinking in terms of Wall Street banks, where for example traders might have very stressful jobs but receive huge bonuses that far outstrip what the more relaxed back office roles get.
That's what I thought! Amazon sure, Apple maybe.. but Google seems like a pretty chill place to work. There's a reason it's like one of the hardest to get into, right? :D
I'm trying to say that you being promoted twice and not being an excellent engineer doesn't mean it's easy. You may have other traits that allow you to excel in that environment. The level distribution by itself says that being promoted twice in 3-4 years, with a significant bump in pay each time, isn't the norm.
Depending on your luck if your manager is someone without kids, or has grown up kids, they might be totally OK working more hours than you, and as a result, the culture can totally become what the author is describing.
Mix the whole interviewing process of Leetcoding with this, and it becomes a sad worklife, and even if you want to escape that, switching careers can only happen if you put in extra hours.
Life is too short to make this sacrifice.
My strategy has been to create good relationships with people in companies and then if they want to hire me, tell them clearly I don't work overtime and I don't do Leetcode. Has worked well for me so far. Relationship building and networking is still the best way even in this industry.
The present company I am working at, I didn't even have to do a coding test. Just a chat.
A marathon runner can't have the pace of a 100m sprinter but software engineers are expected to maintain sprint pace for perpetuity.
And give detailed status reports Every.Single.Day. So there's no possibility of a breather, ever.
This is not at all what it used to be like pre-agile. There was time to think deeply about solutions. It was ok to slack off a day (or three) and make it up later when you got into The Zone.
https://github.com/rayfrankenstein/AITOW/blob/master/README....
The second is that productivity in a creative occupation just doesn't work that way. We're not factory workers assembling widgets on a conveyor belt. Einstein didn't give fucking daily updates on his theory of relativity. No, we're not Einstein, but daily updates ensure that we're not thinking meaningful deep thoughts, instead giving in to short-sighted thinking like a starving beggar looking for their next meal.
>What I found was that the decent salary and excellent benefits came at a much greater cost.
I know you can get in with a big paycheck work your ass for 10 years and get out with lot of money in your bank. Maybe it my early 20s. Now I'm 35+ I don;t have the motivation to be a Google or Apple Software Engineer. I work in small firm and on interesting problems, and I'm OK with it.
> If it was after 6PM and I heard a notification on my phone, the hair on the back of my neck would stand up. Often times it was someone from work asking a seemingly innocent question.
This happens to me at my current job. But I don't have similar reaction to it. I'm more like "Oh, someone is working late..." And I respond to their queries. I believe performance and getting your task done faster has to do something? I know Amazon PIP thing is scary place to end with. No idea just read it on HN.
A lot of my friends work at FAANG and finance in SWE roles too and their wlb is pretty good as well, with most working under 40 hours a week--some well under.
And we're all 1-2 years out of college. I really don't get the whole 22 year olds wanting to work a lot thing. Doesn't seem to hold true in my friend group (~10-20 samples).
You really wanna ask yourself if you wanna go thru the promo circus. What I get after a potential promo at Amazon 1.5 years from now is gonna be less than what I can get if I Leetcode hard and interview with some financial firms and unicorns so that's the route I'm planning on going. Knowing this, I don't even really need to meet expectations or try to go beyond them.
Point being: if you're willing to spend a couple hours a week keeping your interview skills sharp, you can afford to just meet expectations or even perform slightly under and stop worrying about promo and just jump ship when you get a better offer. If you go into every job with this mentality, you won't become attached to your job.
Downside: If you're oncall, you might have to stay up for 18 hours straight of something big goes wrong, and you won't get paid any overtime.
I work at a FAANG, and it's probably a team-by-team thing, but that is absolutely not normal in my experience. That's a particularly shitty circumstance, and it's a bummer your management didn't stick up for you.
* The one exception was when I was on a team where we had a rotating pager duty for our stuff in production, and I would periodically be on duty. As I recall we got paid extra for those time blocks.
If you’re being hired for a team specifically (at another company, say), ask for a “follow-up” meeting with future team mates after offer as a condition for accept. You have a lot of power at that point.
The source of all your misery may have been your inept manager. Your manager's job is to insulate you from these situations when it escalates. Your job is to build a good enough relationship with your manager that they go to bat for you in ambiguous situations. If you can't build this relationship, leave the team immediately and find something else. Direct managers make or break your experience.
The stress of dealing with an organization with the wrong culture, and you having to clean up the messes made, with no agency for meaningful change due to leadership is something most folks with some years in this industry have experienced regardless of the size of the company.
At a tech giant the salary removes even more agency. Near a vest date? Most likely not leaving until after. It's an awful feeling to show up for work, having enough professional pride that you continue to perform, but knowing you want to be anywhere but there.
If you use EAP, you give up your right to privacy (in practice if not in law) and damage any chances you have for finding legal recourse.
“If a potential client called me and said: ‘I’m being harassed at work, I feel really stressed and anxious. Do you think I should use my company’s E.A.P.?’” Ms. Mizrahi said, “I would advise them against it.” [0]
[0] https://www.nytimes.com/2021/07/28/us/google-workplace-compl... https://archive.is/VKXEU
* Things could be worse * Everywhere it's the same * Someone's good time management is someone else's bad time management * The worst behaved wins - be the rhinoceros you wish to see in the world * It doesn't matter what you do, it matter what your bosses boss thinks you do * It is very likely that hiring and headcount is the only thing your boss cares about * We should stop giving RSU grants for people below <insert level> * Everyone can write code, I could easily write a million lines of code if I wanted to * It doesn't matter if you do not get a promotion, you aren't going to take this money with you when you reach heaven < some story about judas and jesus that i did not understand > * If you embarrass me in a meeting, remember that you aren't going to be present when your promotion packet comes up for review * We follow the best development practices - but we also have 3 dozen AWS accounts and manually generated security credentials we message each other in slack * etc etc etc
The least troublesome part was delivering - the hardest was accepting that US work culture confuses leverage for intelligence
So you have a software engineer at Apple ruining his mental and physical health to chase a deadline. Only to have someone at Foxconn in China destroy their eyesight slightly sooner gluing digitizers to iPhone screens. Then we can all buy the resulting product for a commercial holiday starring an imaginary jolly fat man.
But is the new iPhone really all that different than the last? It has a marginally better camera and downloads stuff faster, but if it came out a year later nobody would be particularly upset.
I am certain that I am not the only one disillusioned with tech, and indeed consumerism as a whole. The implications of this will be interesting to see once more people work up the courage to say this out loud.
If you don't, just read Steve Job's biography. Most of the work situations Isaacson described in Apple's earlier days are horrifying, albeit presented in a heroic, nostalgic light.
FWIW, I have heard these types of stories before too, and they are definitely NOT unique to Apple.
I know it's easier said than done and one may feel trapped and overwhelmed in a bad situation, but it's just a job at the end of the day.
Is it really that common? Does it mainly happen at global corps that run essential internet infrastructure?
Being on-call happens at scale because machines are not to be trusted, and the limits of our skulls meet their match when machines vastly outnumber people. When I worked at Amazon S3, we had rotations where people had physical pagers. On-call was a duty, and everyone shared a rotation.
Honestly, I thought it was an awesome responsibility that there I was at 2 AM and some stupid shit happened in dublin and I got to fix it. (Or at least try to fix it as my first on-call shift was rough)
I think Amazon is one of the few companies that get this right with their cultures because you can own efforts that people use. It's not going to be something discarded after a year unless a massive rewrite is planed. The massive rewrites can be super fun (but hard) as well because you have to do it in-flight.
The reason Amazon gets this right is that you can get a bit of the stake on the outcome, and this is awesome. For instance, I designed how Amazon S3 does URL rewrites on the website endpoint. It's a small feature, but I lead the effort from start to finish. For all practical purposes, that feature is most likely going to last until the end of time. However, its that relationship between myself as an engineer with the customer that makes it worth it (at least emotionally).
It read like something in the military, but when there's no legal implications to telling someone his request is unreasonable... then I think it's self-inflicted.
Sometimes the juice is worth the squeeze and sometimes it is not.
Be aware of your work-life balance or lack thereof, the impact on your health and relationships, how work affects your non-work goals, etc. and make the choice you need to make:
1) Try to set boundaries or manage up.
2) Leave for a role that is a better fit.
3) Sometimes it's worth the grind if you are learning enough or being paid enough to stick it out for a bit.
This, right here, is where OP lost. It takes some discipline from management to admit there are only three options:
- There is a formal oncall rotation of people properly equipped to solve all problems.
- Everyone is oncall all the time.
- Whatever you make can only be expected to work in core office hours AND your users understand this is not production level.
In my seven years in Google I've only been in the first and third category. Nobody ever suggested I should do overtime. But I know there are teams in the middle category and people there eventually end up miserable just like OP.
My biggest gripe is that despite knowing that we don't really know what we are doing, that there are lots of unknowns, that something like this is being done for the first time in team the management often expects deadlines set in stone. All the "agile"ity goes out of the window.
Or worse, like in Uber's case, the CEO will announce something on a whim and you have to scramble to get it done because of no fault of your own.
If I'm on call, I'm 100% on call. If something important is late (not endemically but as a one off), I'm fine with working late or on the weekend. Even if someone "unfairly" drags me into their on-call issue I will stay up late and help them.
But once I check out, I check out. I refuse to install work stuff on my phone, and have most notifications off by default... on a rare occasion that someone from work texts me in off hours and off call, I would "miss" the notification unless they describe the problem, and it's actually somewhat urgent. If something is on fire (again, it's very rare and not endemic in the teams I worked in), sure, I'll be there if I'm near a computer. Otherwise I might as well be out in the mountains ;)
The other types exist, but they're typically in non-profits (like, the real kind, not the one where a small team is lining their pockets) and overwork themselves because they believe in the mission.
But if you make 4-10 times the national average, and you start out in your first year making more than most people will at the peak of their career, that's the biggest incentive. You absolutely can semi-retire after five years of doing that and dramatically scale down the amount of work you do because you'll have more savings than most people will have at the end of their career.
WTF? Why is a company like Apple using one off machines for release builds? That should all be on a VM and a server with a management interface. I made that mistake once and won't make it again.
It can take some time to adjust to feeling like you are always at work but IMO it also feels like I'm never at work. I work 40+ hours and respond to things off hours but I don't have to deal with the hour or so of wasted time and typical office annoyances.
I guess when you have a bespoke OS that can't really be virtualized and needs to run on your own (non-server grade) hardware, you need to do stuff like this. I imagine the 'build server' is actually just a Mac Mini.
It is worth focusing on the ways in which you are lucky, and it puts some of the stress in perspective. We are living in challenging times - environmental, economic, and societal change. Everyone is experiencing this stress in different ways.
But before that the power to disconnect from work, to not have slack on your personal phone, and to simply say “no” and set boundaries. You could get fired, true, but thats their loss. You’re lucky in tech that you’ll almost certainly land on your feet.
I think if we can name names to shame the bad teams it really helps the industry improve conditions and expectations. And if you really are on a good team you should get the word out so it's easier for you to hire.
I'd help if I could but I'm just a student.
I've seen that trick pulled many times over my career and I've learnt to just shrug and let it roll.
Unless you can explain to me why it is so absolutely critical that it needs to go today in a form I can understand then I'm not going remotely above and beyond to make it work out that way.
Stressing out my entire team to make an arbitrary deadline imposed from outside for invisible reasons is the definition of me not doing my job as a leader.
It takes experience and practice to learn to manage upwards but it's an intensely useful skill.
Start not with explaining what you can't/won't do but instead with what you can/will do - most people are reasonable most of the time and if they are unreasonable anyway then whatever you do will not be right/enough.
If you firmly say "no" or "I can't" people will be a lot more accommodating than you think. Easier said than done in the actual situation but it seems almost always true.
> If you find yourself in this type of situation, please do what’s best for you and get help if you are feeling stuck or overwhelmed.
Get help the !@#$% where? There isn't a magic American "help" fairy who bails people out of trouble.
These issues are complex, and therapists/counselors/psychologists suck up time and don't really address root causes.
I honestly didn’t realize any of this until the last 1-2 years. When you’re raised in a fairly stable and supportive family environment, the level of dysfunction in other people’s home lives is completely outside of your reality.
- Financial constraints
- A harasser
- A medical problem
- Etc.
a therapist/counselor can't help you very much. Whenever I've had issues I needed help with, there were real issues behind it. A therapist/counselor won't be able to do much, if anything.
If you're making a $350k salary in a hell-job while having $100k in financial obligations, the solution is simple enough.
If you're making a $350k salary in a hell-job to pay for your kid's medical problem and meet mortgage, talking to a therapist or "just quitting" won't do much.
* in an abusive job
* are going to be deported if you quit
* have kids you want to keep in school
... anxiety is a natural biological response, and there isn't a magical therapy trick that will help you get rid of it. Perhaps that time and money is better spent on managing immigration or job issues than on therapy.
And if you're in a new country with no savings and no contacts, continuing with the same example, there might not be friends or family whom you can turn to for help.
Unfortunately, there isn't a magical get-help fairy which helps with external problems. Sometimes, your life just gets f-ed up, and there's nothing you can do about it.
> Furthermore, when issues really started to occur where someone was unable to do any work until you completed a task, it was often threatened that things would need to be escalated to upper management. It was never put this way directly, but to me when people would say this it could be interpreted as “we are going to tell your director about your poor performance.” Because of that, individual contributors (i.e. non-management) would often do everything possible just to get the job done and avoid that escalation. This meant late nights, weekends, skipping lunch, or whatever it takes. Pulling in upper management was bad and should be avoided at all cost. While that wasn’t a written rule, I certainly observed it a lot during my time there.
Seems about right.
My theory is I'd end up paying very little taxes compared to working myself mad trying to hit 200k a year.
You can even try to set non “fulltime” hours eg 20-30hrs/week but not all clients will go for that.
Also file your taxes as an s-Corp and start a solo 401k. You can contribute much more than a regular salaried employee could
It doesn't need to be a full 6 months every single year , some years might be a bit longer , etc.
A very continental take that's much easier to have when others in the organization share the same views. If the culture of the organization is you work late, you care a lot, you're constantly available otherwise you're not a team player and are at risk of being let go, it is unreasonable to say "just don't do it. stop caring". Both psychologically and financially unreasonable.