Live data from Hacker News

Ask HN: I joined a FAANG and it is awful

news.ycombinator.com

51–60 of 255 posts

Re: Ask HN: I joined a FAANG and it is awful

#52
post #14

"staffed with below-average IQ people" I'm not sure why your co-workers' IQ is your concern. To come out of the gate with a comment like this sounds like you have a strong disdain for them. Part of your reason for joining the company was the paycheck. I assume the checks aren't bouncing. My advice is the same advice I would give to many people: Learn from your coworkers. Understand the problems that the team and the…

I remember my first day at Goofacelix when all my cowokers were forced to submit IQ tests to me.

Re: Ask HN: I joined a FAANG and it is awful

#54
I've worked at two different FAANG companies, and have a different view than some of the other commenters here. It sounds like you want to grow, learn, and advance, and I don't think you'll be happy kicking back and coasting.

The first piece is that mobility is high between teams at almost every FAANG company. At my first one, I moved 3 months later because the initial team wasn't a great fit for me maintaining a lot of slow moving legacy systems. I moved to a team working on much more greenfield projects with more attention on the products themselves, and I thrived for several years. See what your options are to talk to other teams and move to one that aligns better with what you want to work on.

The other related piece to this is that because mobility is so high, there do tend to be certain teams or areas with higher turnover and lower quality hires in some cases. No one wants to work on hard to maintain and neglected products, most good engineers that start there move on, and so it becomes a self-perpetuating cycle.

There are likely some extremely brilliant people to learn from at the company (even if not in your team), so try to seek out and find them in teams with openings. I agree it's easier to move after a year, but if the fit is really not right you can likely get an exception going to a team with an understanding manager (who you would enjoy working for anyways). Set up some non-formal meetings based on the internal job board and be open with all these experiences and concerns.

Finally, the internal toolset is a real challenge, but I've come to take a slightly less pessimistic view on it. First off, the internal tooling tends to be worse on an individual workflow level, but accepting it has largely been better for me than fighting it (in most but not all cases). It's slower than a modern toolset, but still usually productive once you embrace what it's good at. The flip side is there are usually good reasons it's evolved to where it is today. Some of these reasons have to do with the scale of how many teams are working together, and understanding that will help explain why it is what it is. The other reasons are just that some of these companies have now been around a long time, and shifting to something better would be quite painful organizationally, meaning it's not ideal but the alternative would also be painful for the organization at a whole. You're new to it, so are at the opposite end of that.

Re: Ask HN: I joined a FAANG and it is awful

#55
Is everyone coasting and there is a lot of turnover? This seems to be somewhat conflicting. Is there a lot of turnover because it is so boring people are quiting? I find this unlikely. I used to work in the government and most people are pretty content coasting, especially if there is a faang salary to go with it.

If people are getting pip'ed or fired it seems like it might be difficult to coast.

Re: Ask HN: I joined a FAANG and it is awful

#56
post #14

"staffed with below-average IQ people" I'm not sure why your co-workers' IQ is your concern. To come out of the gate with a comment like this sounds like you have a strong disdain for them. Part of your reason for joining the company was the paycheck. I assume the checks aren't bouncing. My advice is the same advice I would give to many people: Learn from your coworkers. Understand the problems that the team and the…

I had the same visceral reaction to that comment.

I was fortunate enough to work in an environment, where I was the "below-average IQ person," and I am not below-average, but I worked with some fairly smart cookies.

I know that some of my co-workers looked at me with disdain; but I was honored that most did not.

Working with frustrating people has been a very useful part of my career. As a manager, I had to make life-changing decisions for employees, and it was important for me to be empirical in my decision-making.

It appears that working for FAANGs is a "mark of distinction," these days. I know they pay ridiculous salaries. I'm pretty much aware of the working environment, and don't find the prospect enticing.

In NY, I know many, many folks that worked in the finance industry as brokers and traders. They got their licenses, and made a whole boatload of money in a few short years, while absolutely destroying their mental and physical health.

They then left, when they couldn't stand it anymore, and used the money they made to start companies, doing the things they liked doing.

Maybe that could be the approach the OP may want to take.

Re: Ask HN: I joined a FAANG and it is awful

#57
I recall working for a company who programmed POS in Basic... The place was 20 years late (in any domain) and dysfunctionnal. YET, it is still in business today and making money on a regular basis.

As for me I quit, because I could not focus on my role and instead focused on the environment.

Re: Ask HN: I joined a FAANG and it is awful

#58
You don't have to "coast", you only have to learn to leave the stress and problems at work when the day ends. Work to fix things by day, try to find some enjoyment in it, be kind, and leave the troubles at the office when evening comes.

If you can do this and manage to turn the project around you will have achieved far more than knowing the latest toolsets.

Re: Ask HN: I joined a FAANG and it is awful

#59
post #13

Don't try to fix everything. Pick small battles and things and fix them one by one. You're not at a startup where "fix all the things ASAP or we die" is the driving force. Settle in and work on making things better, even if it's just to keep you in play as you investigate other options. A year of improving a team would give you a solid foundation for an internal transfer, for example.

Also try to get alignment within your team. Does everybody on the team agree these things are so broken? If not, try to find out things you all agree are problems and then fix those (be it by sharing information better, or picking better targets).

I have no idea what you mean about "working weekends." It sounds like you just made up a line in your head "1 year" and then made up a story "I'll be such a victim if I have to fix every single thing myself in 1 year, it will require such suffering." Except nobody told you that you have to fix every single thing on your team in 1 year, why don't you fix half of it in 40 hour weeks, and if it's things people agree are problems and you outshine your team so much then I think you'll find it's nice to be appreciated.

This plus the IQ comment, plus the nature of the question (how much deep down did you turn to HN because you thought we'd give you a simple quick fix? how much did you ask this "question" just to vent?) makes me think you might be a challenging person to work with. This could be a great opportunity for you try to attain technical mastery of yourself, your presentation, and your emotions/attitude.

Re: Ask HN: I joined a FAANG and it is awful

#60
"staffed with below-average IQ people"

I don't think anyone is in the position to judge other IQ's especially co-workers. These people passed the same interview loop as you. Just puts them in the same "IQ" bracket as you. Maybe they also feel the same way as you and don't want to put their effort in trying to turn this team around and just want to coast and switch later on. You need to get off your high horse and try to understand the motivations of the team by talking to them individually and bringing stuff up in standups/meetings and suggest ways to improve. Work with your manager. Maybe you can be the one who can turn this team around without burning out yourself. In the end, its just a job and trick is to not take everything personally.

Post reply on HN